This guide walks you through setting up single sign-on (SSO) using SAML 2.0, with Microsoft Entra ID as the identity provider (IdP). Unleash supports a variety of identity providers and protocols; visit our reference documentation to explore other options.
To follow along, you’ll need:
To create a new enterprise application in Microsoft Entra, do the following:
To configure SSO for the new application, do the following:
https://<region>.app.unleash-hosted.com/<your_unleash_instance_name>.<your_unleash_url>/auth/saml/callback.To configure attributes and claims for the new application, do the following:
user.mail.To populate the first and last names of users in Unleash, configure two additional claims with attributes user.givenname and user.surname with no namespace.

Save the following information from the single sign-on settings of your application:
To save the SAML certificate, go to the single sign-on settings of your application. In SAML Certificates > Federation Metadata XML, click Download. Open the file and copy the contents between the X509Certificate tag.

To find your login URL, go to the single sign-on settings of your application. In the Set up <your-application-name> section, copy and save Login URL. For example: https://login.microsoftonline.com/<your_identifier>/saml2.
To find your Microsoft Entra identifier, go to the single sign-on settings of your application. In the Set up <your-application-name> section, copy and save Microsoft Entra Identifier. For example: https://sts.windows.net/<your_identifier>
To finalize the configuration, do the following:

To test that things are working as expected, log out of Unleash and verify that the login screen gives you the option to sign in with SAML 2.0. You can also test the integration in Microsoft Entra in the single sign-on settings of your application.
Optionally, you can sync groups from Microsoft Entra ID to Unleash to map them to groups in Unleash.
To create the group in Microsoft Entra, do the following:
Microsoft Entra limits the number of groups emitted in a SAML response to 150, including nested groups. If you have users who are present in more than 150 groups, add a filter in the advanced section of group claims to ensure the response only includes the groups you want to send to Unleash.
To enable group syncing in Unleash, do the following: