Authentication Application Credentials

Description

Application-only access is broader and more powerful than delegated access (User Credentials), so you should only use app-only access where needed. Use it when: 1. The application needs to run in an automated way, without user input (for example, a daily script that checks emails from certain contacts and sends automated responses). 2. The application needs to access resources belonging to multiple different users (for example, a backup or data loss prevention app might need to retrieve messages from many different chat channels, each with different participants). 3. You find yourself tempted to store credentials locally and allow the app to sign in 'as' the user or admin. [API reference]

Instructions

Follow these simple steps below to create Microsoft Entra ID application with application access permissions.

1. Navigate to the Azure Portal and log in using your credentials.
2. Access Microsoft Entra ID.

3. Register a new application by going to App registrations and clicking on New registration button:

   
   INFO: Find more information on how to register an application in Graph API reference.

4. When configuration window opens, configure these fields:

   • Supported account type
     • e.g. select Accounts in this organizational directory only if you need access to data in your organization only.
   • Redirect URI:
     • Set the type to Public client/native (mobile & desktop).
     • Leave the URL field empty.
   

5. After registering the app, copy the Application (client) ID for later:

   

6. Then copy OAuth authorization endpoint (v2) & OAuth token endpoint (v2) URLs:

   

7. Continue and create Client secret:

   

8. Then copy the Client secret for later steps:

   

9. Continue by adding permissions for the app by going to the API permissions section, and clicking on Add a permission:

   

10. Select Microsoft Graph:

    

11. Then choose Application permissions option:

    

12. Continue by adding these Mail (Outlook) application permissions (for example Mail.Read, Mail.ReadWrite, or Mail.Send depending on your needs):

    

13. If you want the Default User Id drop down to list organization users (calls GET /users), repeat Add a permission and also add the User.Read.All application permission. Add Group.Read.All if you need group lookups. Search for User under Application permissions, select User.Read.All, then click Add permissions.

14. Finish by clicking Add permissions button:

    

15. Now it's time to Grant admin consent for your application:

    

16. Confirm all the permissions are granted (Mail scopes plus User.Read.All when using the user drop down):

    

17. Now go to SSIS package or ODBC data source and use the copied values in Application Credentials authentication configuration:

    • In the Token URL field paste the OAuth token endpoint (v2) URL value you copied in the previous step.
    • In the Client ID field paste the Application (client) ID value you copied in the previous step.
    • In the Client Secret field paste the Client secret value you copied in the previous step.
    • Choose Default User Id from the drop down menu (requires User.Read.All application permission and admin consent), or type a user id or email manually.
18. Click Test Connection to confirm the connection is working.
19. That's it! Now you can use the connector.

Parameters