> ## Documentation Index
> Fetch the complete documentation index at: https://nango.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How to register your own Microsoft Dataverse OAuth app

> Register an OAuth app with Microsoft Entra ID and connect it to Nango

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.

<Steps>
  <Step id="create-accounts" title="Create a Microsoft account and Azure account">
    If you don't already have them, sign up for a [Microsoft account](https://account.microsoft.com/account) and an [Azure account](https://azure.microsoft.com/free).
  </Step>

  <Step id="register-application" title="Register an application in Microsoft Entra ID">
    1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) 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**.
  </Step>

  <Step id="note-client-id" title="Note your application (client) ID">
    After registration, you'll be taken to the application's Overview page. Record the **Application (client) ID**.
  </Step>

  <Step id="add-redirect-uri" title="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**.
  </Step>

  <Step id="add-api-permissions" title="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.
  </Step>

  <Step id="create-client-secret" title="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.
  </Step>

  <Step id="next-steps" title="Next">
    Follow the [*Quickstart*](/docs/getting-started/quickstart).
  </Step>
</Steps>

## 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](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/authenticate-oauth).

***