Skip to content

Sign in to Microsoft Entra External ID ​

You can add EntryIdP to a Microsoft Entra External ID tenant as an identity provider, so that people sign up and sign in to your apps with an EntryIdP face scan. No code is involved: External ID's custom OpenID Connect identity provider works with any OpenID Connect provider, and EntryIdP is one.

You'll need about 30 minutes, an EntryIdP tenant administrator, and someone who can manage identity providers and user flows in your external tenant.

External ID only, not your staff directory

This guide is for an external tenant, which holds your customers. A workforce tenant, which holds your own staff, can't use EntryIdP: Entra only federates staff sign-in over SAML or WS-Federation.

How it works ​

  1. Someone selects Sign in with EntryIdP on your app's Entra sign-in page.
  2. Entra sends them to EntryIdP. They do a face scan, and EntryIdP finds their account.
  3. The first time, Entra asks for a display name and creates a user for them. After that, it signs them in as that user.

Entra identifies each person by their EntryIdP account, not by email. EntryIdP sends Entra no email address, so the Entra user has none unless you collect one.

Before you start ​

  • [ ] You have an external tenant, with an app registration and a sign-up and sign-in user flow for it.
  • [ ] Each person who will use it has an EntryIdP account, made at {issuer}/me with Create Entry Account.

Entra never asks EntryIdP to create an account, so a person with no EntryIdP account can't get through.

Step 1: Register Entra as an app in EntryIdP ​

Find your external tenant's subdomain (the part before .onmicrosoft.com in its primary domain) and its tenant ID, on the tenant's overview page. Then, in your tenant's admin portal ({issuer}/tenant), add a new app:

SettingValue
NameThe name of your Entra app
TypeConfidential (it has a client secret)
Scopesopenid profile
Redirect URIshttps://{subdomain}.ciamlogin.com/{tenant ID}/federation/oauth2 and https://{subdomain}.ciamlogin.com/{subdomain}.onmicrosoft.com/federation/oauth2

Leave Allow sign-in without PKCE off. Entra sends PKCE.

Copy the client ID and client secret. The secret is shown only once.

Limit who can use it

Turn on Require access approval for this app. Only people you approve can then sign in through it.

Step 2: Add EntryIdP to Entra ​

In the Microsoft Entra admin center, in your external tenant:

  1. Go to Entra ID → External Identities → All identity providers, open the Custom tab, and select Add new → Open ID Connect.

  2. Fill in:

    FieldValue
    Display nameEntryIdP
    Well-known endpoint{issuer}/.well-known/openid-configuration
    OpenID Issuer URI{issuer}, with no trailing /
    Client IDFrom step 1
    Client authenticationClient secret
    Client secretFrom step 1
    Scopeopenid profile. Don't add email: EntryIdP refuses any scope it doesn't know.
    Response typecode
  3. Select Next: Claims mapping. Map Subject to sub, and leave every other claim empty. EntryIdP's ID token carries no name or email.

  4. Select Review + create.

Your issuer is https://idp.entryidp.com on Production. See How it works for the other environments.

Step 3: Add EntryIdP to your user flow ​

  1. Go to External Identities → User flows and open your sign-up and sign-in flow.
  2. Under Identity providers, select EntryIdP and save.
  3. Under User attributes, keep Display Name, so Entra asks each person for a name the first time.

Step 4: Make email optional ​

Entra requires an email when someone signs up through another provider, and EntryIdP doesn't send one. Until you change this, the first sign-up stops on Entra's Add details page: Next does nothing, because the email field is required but hidden.

The admin center has no setting for this, so use Graph Explorer, following Microsoft's Make email optional:

  1. Open Graph Explorer with ?tenant={subdomain}.onmicrosoft.com on the end of its address, and sign in.
  2. Run GET https://graph.microsoft.com/v1.0/identity/authenticationEventsFlows. If asked, open Modify permissions and consent to EventListener.ReadWrite.All.
  3. Find your user flow by its displayName and run a GET on …/authenticationEventsFlows/{id}.
  4. Copy its onAttributeCollection. Remove the attributes list, set "required": false on the email input, and keep every other input as it is.
  5. Send it back with PATCH …/authenticationEventsFlows/{id}, with "@odata.type": "#microsoft.graph.externalUsersSelfServiceSignUpEventsFlow" at the top of the body. Expect 204 No Content.

The change applies to every app that uses this user flow.

Step 5: Test ​

In the user flow, select Run user flow, pick your app, and open the link in a private browser window.

TestExpected result
A person with an EntryIdP account selects Sign in with EntryIdP for the first timeFace scan, Entra's Add details page, then back in your app, signed in
The same person a second timeFace scan, then signed in as the same Entra user
A person with no EntryIdP accountFace scan, then an error returned to your app: EntryIdP doesn't know their face

In our test, it took about 16 seconds from selecting EntryIdP to Entra's Add details page, including the face scan.

Troubleshooting ​

What the person seesLikely causeWhat to do
Next on Add details does nothingEmail is still required on the user flowMake email optional (step 4)
AADSTS901011: No email address was obtained from the external oidc identity providerEmail is still required on the user flowMake email optional (step 4)
An EntryIdP error that the scope is invalidEntra is asking for email or another scope EntryIdP doesn't knowSet Scope to openid profile
An EntryIdP error about the redirect URIThe app's redirect URIs don't match your tenantCopy both again from step 1, with your own subdomain and tenant ID
No Sign in with EntryIdP buttonEntryIdP isn't added to this app's user flowAdd it (step 3)

Turn it off ​

Remove EntryIdP from the user flow's identity providers. Nothing needs to change in EntryIdP.

Good to know ​

  • Entra reads only the ID token. It never calls EntryIdP's userinfo endpoint, so it gets the person's EntryIdP ID (sub) and nothing else.
  • Entra creates its own user the first time each person signs in through EntryIdP. It doesn't join them to an existing user with the same email.

See Microsoft's own guide: Add OIDC for customer sign-in.

EntryIdP — Synapser