Microsoft Entra External ID
Authentication

Custom URL Domains

In brief

The documentation now states that Native Authentication API and Bring Your Own UX require a tenant-verified custom domain for all service API call URLs.

What Entra admins need to know

Administrators integrating either approach must verify and configure the custom domain before integration.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Custom URL domains in external tenantsMicrosoft Entra External ID

[!INCLUDE applies-to-external-only]

A custom URL domain allowslets you to branduse your application’s sign-own authentication endpoint names in endpoints with your ownMicrosoft Entra External ID.

[!INCLUDE authentication-approaches]

The current Native Authentication API and Bring Your Own UX (BYO UX) require a tenant-verified custom domain for all service API call URLs. Verify and configure that domain before integrating either approach. Microsoft-hosted authentication can also use a custom URL domain instead of Microsoft’s default domain name.for a consistent sign-in address.

:::image type="content" source="./media/concept-custom-url-domain/custom-domain-user-experience-small.png" alt-text="Screenshot demonstrates an External ID custom URL domain user experience." lightbox="./media/concept-custom-url-domain/custom-domain-user-experience.png":::

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…