# Microsoft Entra ID

> Connect a SAML enterprise application in Microsoft Entra ID, formerly Azure AD.

Source: https://diakrin.com/docs/sso/microsoft-entra

Microsoft Entra ID was previously called Azure Active Directory. Use an **enterprise application** with SAML single sign-on. You need application-management permissions in your tenant.

## Create the application

1. In Microsoft Entra admin center, open **Enterprise applications → New application → Create your own application**.
2. Name it **Diakrin** and choose to integrate an application you do not find in the gallery.
3. Open **Single sign-on → SAML** and edit **Basic SAML Configuration** using your [setup packet](/docs/sso#get-your-setup-packet).
4. Review **Attributes & Claims**. Supply the work email and a stable NameID; a UPN is suitable only when it is the intended work-email identifier.
5. Assign pilot users or groups under **Users and groups** and apply your company’s Conditional Access policy.

## Map the fields

| Entra field | Value |
| --- | --- |
| Identifier (Entity ID) | Diakrin SP Entity ID |
| Reply URL (Assertion Consumer Service URL) | Diakrin ACS URL |
| Sign on URL | Diakrin console sign-in URL |
| Unique User Identifier (Name ID) | Work email in EmailAddress format, or agreed Persistent identifier |
| Additional claim `email` | Your directory’s work-email value |

## Activate and test

From **SAML Certificates**, copy **App Federation Metadata Url** or download the federation metadata XML. Return it with approved domains and certificate expiry to your Diakrin onboarding contact. After activation, follow [Test and roll out SSO](/docs/sso/testing).

If an assigned user still cannot log in, review the enterprise application’s sign-in logs and Conditional Access result. Do not relax tenant-wide policy to resolve one application’s setup.

Official reference: [Enable SAML single sign-on for an enterprise application](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/add-application-portal-setup-sso).
