# Microsoft Entra ID SAML single sign-on

<!-- Generated by scripts/generate.ts. Do not edit. -->

Create an enterprise application in Microsoft Entra ID, configure SAML with the values from this setup, assign your users and share the app's federation metadata with us.

:::caution[Verification]
Not yet verified on a real Microsoft Entra ID tenant. It was written from the public Microsoft Entra ID documentation, so labels in the admin console may differ slightly.
:::

The values in braces, such as `{sp_entity_id}`, are specific to your connection. The setup link from the application you are connecting shows them with a copy button. The same steps appear there.

## Steps

<ol class="idp-steps">

<li class="idp-step">

<a id="create-app"></a>

### Create an enterprise application

Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator. Browse to Entra ID > Enterprise apps, select New application > Create your own application, name it, choose "Integrate any other application you don't find in the gallery" and select Add.

</li>

<li class="idp-step">

<a id="open-sso"></a>

### Open the SAML settings

In the app's Manage section, select Single sign-on, then select SAML.

</li>

<li class="idp-step">

<a id="identifier"></a>

### Enter the identifier

In Basic SAML Configuration, select Edit. In Identifier (Entity ID), paste `{sp_entity_id}`.

<div class="setup-values">

Paste into Microsoft Entra ID:

- SP entity ID: `{sp_entity_id}`

</div>

Fixes: [`saml_audience_mismatch`](/errors/saml_audience_mismatch/)

</li>

<li class="idp-step">

<a id="reply-url"></a>

### Enter the reply URL

In Reply URL (Assertion Consumer Service URL), paste `{acs_url}`, then select Save.

<div class="setup-values">

Paste into Microsoft Entra ID:

- ACS URL: `{acs_url}`

</div>

Fixes: [`saml_destination_mismatch`](/errors/saml_destination_mismatch/), [`saml_response_malformed`](/errors/saml_response_malformed/)

</li>

<li class="idp-step">

<a id="claims"></a>

### Check the claims

In Attributes and Claims, make sure the email address, given name and surname claims are sent and the unique user identifier (name ID) is the user's email address or another stable value.

Fixes: [`saml_email_missing`](/errors/saml_email_missing/), [`saml_nameid_missing`](/errors/saml_nameid_missing/)

:::caution[Labels not confirmed in step 5]
The SAML page read on 2026-10-11 does not name the Attributes and Claims labels.
:::

</li>

<li class="idp-step">

<a id="signing"></a>

### Check the signing settings

In SAML Certificates, make sure the assertion is signed with SHA-256.

Fixes: [`saml_signature_missing`](/errors/saml_signature_missing/), [`saml_signature_algorithm_weak`](/errors/saml_signature_algorithm_weak/)

:::caution[Labels not confirmed in step 6]
The SAML page read on 2026-10-11 does not name the signing option and algorithm labels.
:::

</li>

<li class="idp-step">

<a id="assign"></a>

### Assign people to the app

In the app's Users and groups, assign the people or groups who should sign in with single sign-on.

Fixes: [`saml_idp_status_error`](/errors/saml_idp_status_error/)

</li>

<li class="idp-step">

<a id="metadata"></a>

### Share the federation metadata

In SAML Certificates, copy the app's federation metadata URL (or download the federation metadata XML) and add it to this setup. Do this again whenever the signing certificate changes.

Fixes: [`saml_signature_invalid`](/errors/saml_signature_invalid/), [`saml_issuer_mismatch`](/errors/saml_issuer_mismatch/)

:::caution[Labels not confirmed in step 8]
The SAML page read on 2026-10-11 names Certificate (Raw) but not the federation metadata download.
:::

</li>

<li class="idp-step">

<a id="test"></a>

### Test the connection

Run a test sign-in in this setup, signing in as a user you assigned to the app.

</li>

</ol>

<a id="standby"></a>

## Optional: add the standby reply URL

If our main network ever has an outage, sign-ins can continue through a standby address, but only if Entra ID accepts it. If you uploaded our metadata file, the standby URL is already a second reply URL; check that it is listed. Otherwise, in Basic SAML Configuration, add `{standby_acs_url}` as a second Reply URL, keep `{acs_url}` as the default and select Save. Then confirm in this setup that you added it.

<div class="setup-values">

Paste into Microsoft Entra ID:

- Standby ACS URL: `{standby_acs_url}`
- ACS URL: `{acs_url}`

</div>

This step is optional. See [standby route behavior](/trust/standby/) for what the standby address does during an outage.

## Sources

- [Enable SAML single sign-on for an enterprise application (Microsoft Learn)](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/add-application-portal-setup-sso), read on 2026-10-11
- [Develop and plan provisioning for a SCIM endpoint, connecting a non-gallery application (Microsoft Learn)](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/use-scim-to-provision-users-and-groups), read on 2026-10-11
