Tutorial: Register an app with Azure Active Directory

  • Article
  • 2 minutes to read

This tutorial describes how to register an application with Azure Active Directory, which enables a user with Ability Apps user business relationship to connect to their Microsoft Dataverse environment from external client applications using OAuth authentication.

Important

Power Apps also provides you with Server-to-Server (S2S) hallmark option to connect to Dataverse surroundings from external applications and services using the special application user account. S2S hallmark is the mutual way that apps registered on Microsoft AppSource employ to access the data of their subscribers. More information: Build web applications using Server-to-Server (S2S) hallmark.

App registration in Azure Active Directory is typically done by ISVs who desire to develop external client applications to read and write information in Dataverse. Registering an app in Azure Active Directory provides you with Application ID and Redirect URI values that ISVs can use in their customer application's authentication code. When stop users use the ISV'south application for the first time to connect to their Dataverse environment by providing their Dataverse credentials, a consent class is presented to the finish user. Afterwards consenting to use their Dataverse account with the ISV's application, terminate users can connect to Dataverse environment from external application. The consent form is not displayed over again to other users afterward the first user who has already consented to use the ISV's app. Apps registered in Azure Agile Directory are multi-tenant, which implies that other Dataverse users from other tenant can connect to their environment using the ISV's app.

App registration can besides be done by an application developer or individual user who is building a client awarding to connect to and read/write data in Dataverse. Use the Application ID and Redirect URI values from your registered app in your client application's authentication code to be able to connect to Dataverse environment from your client application, and perform the required operations. Note that if the app is registered in the same tenant as your Dataverse environment, you won't be presented with a consent form when connecting from your client application to your Dataverse environs.

Prerequisites

  • An Azure subscription for application registration. A trial account will too piece of work.

Create an application registration

  1. Sign in to the Azure portal using an business relationship with administrator permission. You must use an account in the same Microsoft 365 subscription (tenant) as you intend to annals the app with. Yous tin also access the Azure portal through the Microsoft 365 Admin center by expanding the Admin centers item in the left navigation pane, and selecting Azure Active Directory.

    Note

    If y'all don't have an Azure tenant (account) or you do have one but your Microsoft 365 subscription with Dataverse is not bachelor in your Azure subscription, post-obit the instructions in the topic Ready up Azure Active Directory access for your Programmer Site to acquaintance the two accounts.

    If you don't take an account, you tin sign up for one by using a credit bill of fare. However, the account is free for application registration and your credit carte du jour won't be charged if you only follow the procedures called out in this topic to register i or more than apps. More information: Agile Directory Pricing Details

  2. In the Azure portal, select Azure Active Directory in the left pane and select App registrations and click on New registration.

    Azure App Registration.

  3. In the Annals an awarding page, enter your application'southward registration information:

    • In the Proper name section, enter a meaningful application name that will be displayed to the users.

    • Select Accounts in any organizational directory choice from Supported account types section.

    • Set the Redirect URI.

    • Click on Register to create the application.

      New App registration page.

  4. On the app Overview page, hover over Application (client) ID value, and select the Copy to clipboard icon to re-create the value equally you'll demand to specify this in your application's authentication code or app.config file where advisable.

    Copy application ID.

  5. Select Manifest tab, in the manifest editor, set up the allowPublicClient* property to true and click on Salvage.

    App registration Manifest.

  6. Select API permissions tab, click on Add a permission.

    Add app permission.

  7. Search for and cull Dataverse under the APIs my organization uses tab. If "Dataverse" is not establish, and then search for "Common Data Service".

    Select API.

    Tip

    If y'all are presented with more than one Common Data Service item in the search list, cull whatever one of them. In the adjacent stride the service proper name and URL will exist shown. At that betoken you tin can go back to the API search and choose a unlike Dataverse list item if needed.

  8. Click on Delegated permissions and check the options and click on Add permissions.

    Delegate Permissions.

    Note

    A future revision of the form in footstep #8 will replace the Dynamics CRM logo and icon with Dataverse.

This completes the registration of your application in Azure Active Directory.

Additional configuration options

If your awarding volition be a Single Page Awarding (SPA) that depends on CORS you must configure the app registration to back up the implicit flow. More information: Tutorial: Registering and configuring a SPA application with adal.js

If your application will back up server-to-server connections, see Use Multi-Tenant Server-to-server hallmark

See besides

Awarding registration in Azure Active Directory
Authenticate Users with Dataverse Web Services