Skip to main content
This guide shows you how to register your own app with Microsoft Entra ID to obtain your OAuth credentials (client ID & secret). These are required to let your users grant your app access to their Microsoft Dataverse environment.
1

Create a Microsoft account and Azure account

If you don’t already have them, sign up for a Microsoft account and an Azure account.
2

Register an application in Microsoft Entra ID

  1. Sign in to the Microsoft Entra admin center as at least an Application Developer.
  2. If you have access to multiple tenants, use the Settings icon in the top menu to switch to the tenant that hosts your Dataverse environment.
  3. From the search bar, search for App registrations and select it, then choose New registration.
  4. Enter a meaningful name for your application, for example “Nango Integration”, and click Register.
3

Note your application (client) ID

After registration, you’ll be taken to the application’s Overview page. Record the Application (client) ID.
4

Add a redirect URI

  1. In the left sidebar, select Authentication.
  2. Under Platform configurations, select Add a platform, then select Web.
  3. Enter https://api.nango.dev/oauth/callback as the Redirect URI, then click Configure.
5

Add API permissions

  1. In the left sidebar, select API permissions, then click Add a permission.
  2. Select APIs my organization uses, and search for Dynamics CRM.
  3. Under Delegated permissions, check user_impersonation (“Access Dynamics 365 as organization users”).
  4. Click Add permissions, then click Grant admin consent if you have permission to do so.
6

Create a client secret

  1. In the left sidebar, select Certificates & secrets.
  2. Under Client secrets, click New client secret.
  3. Enter a description and an expiration period, then click Add.
  4. Important: Copy the secret value immediately — you won’t be able to see it again after you leave this page.
7

Next

Follow the Quickstart.

​
API gotchas

  • The delegated user_impersonation scope requires a signed-in Dataverse user — the connection authorizes as whichever user logs in during the OAuth flow, with that user’s own security-role permissions.
For more details, see Use OAuth authentication with Microsoft Dataverse.