SSO Integration with Microsoft Entra ID

Marketplace Integration Help
1

Hi there,

May I have a quick question on whether Auth0 supports integration with Microsoft Entra ID? I saw that we have an option to integrate with Azure Directory RMS SSO on the Auth0 Dashboard’s SSO page. Are they the same (assuming that Microsoft Entra ID just changed the name to Azure Directory)? If not, how can I implement SSO for Microsoft Entra ID?

Thank you in advance,

Hung Vo

2

Hi @hwng

Welcome to the Auth0 Community!

You are asking whether Auth0 supports Microsoft Entra ID, whether the Azure RMS SSO option on the SSO page is the same thing, and how to set up Entra ID single sign-on if it is not.

[Solution] Microsoft Entra ID is the current name for Azure Active Directory, and Auth0 supports it through the Microsoft Azure AD enterprise connection. The Azure RMS SSO option on the SSO page is a different Microsoft service for Rights Management, so it is not the integration you need for Entra ID sign-in. Set up the enterprise connection instead.

  1. Register an application in the Microsoft Entra admin center. Under Supported account types, choose the option that matches your audience: a single directory for your own users, or any organizational directory for customers from other Entra tenants.
  2. Add the Auth0 callback URL as a Web platform redirect URI: https://YOUR_AUTH0_DOMAIN/login/callback.
  3. Create a client secret for the application, then copy the Application (client) ID and the secret value.
  4. Open the Auth0 Dashboard and go to Authentication → Enterprise → Microsoft Azure AD, then enter the client ID and client secret.
  5. Set the Microsoft endpoint to the common endpoint if you want users from any Entra tenant to sign in. Restrict it to your own tenant if you only need your own users.
  6. Enable the connection for your Auth0 application. If you want users to reach the Entra ID login without typing a domain, add the email domains to Home Realm Discovery.
  7. Test with the Try button in the connection settings, then sign in through your application.

For multi-tenant customer setups, the community recommends a single enterprise connection that uses the common endpoint, combined with Home Realm Discovery domains for each customer tenant.

You can read more about it in our documentation for Connecting Your App to Microsoft Azure Active Directory.

Please follow up if you need further assistance after completing the connection test.

Thanks!
Dawid

1 Like
3

Thank you, I will check that out and let you know if I have any further question.

Best,

Hung

4

Integrating that with Microsoft Azure Active Directory (Entra ID) worked! There are quite a few configurations with common endpoint that I might need to play around to actually get multiple tenant (customers) to use the app through a single button on signing in with microsoft.

Furthermore, dumb question if you can tell the difference between what you recommended and this option in dashboard → Application → SSO Integration. Looks like they are both using SSO in principle, is that correct?

image
image1158×783 56 KB

5

Hi there, can you clarify if there is any difference in using SSO integration that way as mentioned above.

Moreover, can you point out for me how we can have users linking different identities, as I am currently having database connection by default, and Azure AD connection right now for SSO for the future use? Hence, the same account can be linked if the user decides to login with the other method of connection as long as they are using the same email.

Currently, one Azure AD connection will have a specific button at the login page, how can I utilize one button for multiple Azure AD connections (if I have more)?

Hope you can help me answer these questions well.