Connect Your App to Microsoft Azure Active Directory

You can integrate with Microsoft Azure Active Directory (AD) if you want to let users:

• From within your company use your application from an Azure AD controlled by you or your organization.

• From other companies' Azure ADs use your application. (We recommend that you configure external directories as different connections.)

To connect your application to Azure AD, you must:

1. Register your app with Azure AD

2. Create an enterprise connection in Auth0

3. Enable the enterprise connection for your Auth0 Application

4. Test the connection

To register your app with Azure AD, see Microsoft's Quickstart: Register an application with the Microsoft identity platform.

During registration, configure the following settings:

During this process, Microsoft generates an Application (client) ID for your application; you can find this on the app's Overview screen. Make note of this value.

To create a client secret, see Microsoft's Quickstart: Configure a client application to access web APIs - Add Credentials to your web application.

Once generated, make note of this value.

To add permissions, see Microsoft's Quickstart: Configure a client application to access web APIs - Add permissions to access web APIs.

While configuring permissions, consider the following:

If you want to enable extended attributes (such as Extended Profile or Security Groups), then you will need to configure the following permissions for the Microsoft Graph API.

Create and configure an Azure AD Enterprise Connection in Auth0. Make sure you have the Application (client) ID and the Client secret generated when you set up your app in the Microsoft Azure portal.

1. Navigate to Auth0 Dashboard > Authentication > Enterprise, locate Microsoft Azure AD, and select its +.

   

2. Enter details for your connection, and select Create:

   Field	Description
   Connection name	Logical identifier for your connection; it must be unique for your tenant. Once set, this name can't be changed.
   Microsoft Azure AD Domain	Your Azure AD domain name. You can find this on your Azure AD directory's overview page in the Microsoft Azure portal.
   Client ID	Unique identifier for your registered Azure AD application. Enter the saved value of the Application (client) ID for the app you just registered in Azure AD.
   Client Secret	String used to gain access to your registered Azure AD application. Enter the saved value of the Client secret for the app you just registered in Azure AD.
   User ID Attribute Type	Attribute in the ID token that will be mapped to the user_id property in Auth0. The options correspond to the two supported ID types described in Microsoft's documentation: ID token claims reference - Microsoft identity platform.
   Use common endpoint	(Optional) When enabled, your application will dynamically accept users from new directories. Typically enabled if you selected a multi-tenant option for supported account types for the application you just registered in Azure AD. Auth0 redirects users to Azure's common login endpoint and Azure performs Home Realm Discovery based on the domain of the user's email address.
   Identity API	API used by Auth0 to interact with Azure AD endpoints. Learn about the differences in behavior in Microsoft's Why update to Microsoft identity platform (v2.0) doc.
   Attributes	Basic attributes for the signed-in user that your app can access. Indicates how much information you want stored in the Auth0 User Profile.
   Extended Attributes (optional)	Extended attributes for the signed-in user that your app can access.
   Auth0 APIs (optional)	When selected, indicates that we require the ability to make calls to the Azure AD API, which allows us to search for users in the Azure AD Graph even if they never logged in to Auth0.
   Email Verification	Choose how Auth0 sets the email_verified field in the user profile. To learn more, see Email Verification for Azure AD and ADFS.

   

3. In the Provisioning view, you can configure how user profiles get created and updated in Auth0.

   Field	Description
   Sync user profile attributes at each login	When enabled, Auth0 automatically syncs user profile data with each user login, thereby ensuring that changes made in the connection source are automatically updated in Auth0.
   Sync user profiles using SCIM	When enabled, Auth0 allows user profile data to be synced using SCIM. For more information, see Configure Inbound SCIM.

4. In the Login Experience view, you can configure how users log in with this connection.

   Field	Description
   Home Realm Discovery	Compares a user's email domain with the provided identity provider domains. For more information, read Configure Identifier First Authentication
   Display connection button	This option displays the following choices to customize your application's connection button.
   Button display name (Optional)	Text used to customize the login button for Universal Login. When set the button reads: "Continue with {Button display name}".
   Button logo URL (Optional)	URL of image used to customize the login button for Universal Login. When set, the Universal Login login button displays the image as a 20px by 20px square.

   Optional fields are available with Universal Login only. Customers using Classic Login will not see the Add button, Button display name, or Button logo URL.

5. If you have appropriate Azure AD administrative permissions to give consent to the application so users can log in, then click Continue. You will be asked to log in to your Azure AD account and give consent. Otherwise, provide the given URL to your administrator so that they can give consent.

To use your new Azure AD enterprise connection, you must first enable the connection for your Auth0 Applications.

Now you're ready to test your connection.

Here are some troubleshooting tips:

I registered my application with Azure AD, but when I go back to my Azure Active Directory App registrations, I can't see my application.

You may have accidentally registered your app in the wrong Azure AD directory (or not have created an Azure AD directory at all before registering your app). It's likely easiest to re-register your app in Azure AD. Make sure you are in the correct directory when you register the app. If you need to create an Azure AD directory, follow Microsoft's Quickstart: Create a new tenant in Azure Active Directory - Create a new tenant for your organization.

I receive the following error message: "Access cannot be granted to this service because the service listing is not properly configured by the publisher".

To resolve this, try changing the Supported account types for your registered Azure AD app. Make sure you have chosen an appropriate multitenant option in the Azure AD app's Authentication settings. Multitenant options include the following: Accounts in any organizational directory (Any Azure AD directory - Multitenant).

When users try to log in, we receive the following error message: "invalid_request; failed to obtain access token".

The most likely reason for this error is an invalid or expired Azure AD Client secret. To resolve this, generate a new Client secret for your app in Azure AD, then update the Client Secret in the enterprise connection configured with Auth0.

Signing keys are used by the identity provider to sign the authentication token it issues, and by the consumer application (Auth0 in this case) to validate the authenticity of the generated token.

For security purposes, Azure AD’s signing key rolls on a periodic basis. If this happens, you do not need to take any action. Auth0 will use the new key automatically.

If you're using a custom domain, the application consent prompt for Azure AD login may label your domain as "unverified". To remove the unverified label:

1. Verify the domain for the Auth0 application: Add your custom domain name using the Azure Active Directory portal.

2. Assign the verified domain to the Auth0 application: How to: Configure an application's publisher domain.

• Integrate with Auth0 using one of our libraries

• Integrate with Auth0 using our Authentication API

• Read more about the authentication flow

• Pass additional parameters to the Identity Provider

• Re-prompt users for permissions