Microsoft Entra External ID
Fundamentals

Microsoft Entra External ID Overview

In brief

The overview now lists Microsoft-hosted authentication, Embedded native authentication, and BYO UX for customer-app authentication. It also specifies that company branding customizes Microsoft-hosted sign-in pages.

What Entra admins need to know

Administrators can use the updated guidance to understand which authentication experience the branding settings apply to.

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.

Organizations and developers can use External ID in an external tenant as their CIAM solution when publishing their apps to consumers and business customers.

You can create a separate Microsoft Entra tenant in an external configuration to manage your apps and user accounts separately from your workforce. For customer-app authentication, choose Microsoft-hosted authentication, Embedded native authentication, or Bring Your Own UX (BYO UX). See Choose an authentication approach for selection criteria and current availability.

Within this tenant, you can configure custom-branded sign-upauthentication experiences and user management features:for your apps:

  • Set up self-service registration flows that define the sign-up steps that customers follow and the sign-in methods that they can use. These methods include email and password, one-time passcodes, or social accounts from Google or Facebook.

  • Create a custom experience for users who sign For Microsoft-hosted authentication, customize sign-in to your appspages by configuring company branding settings for your tenant. With these settings, you can addAdd your own background images, colors, company logos, and text for sign-ins across your apps.

  • Collect information from customers during sign-up by selecting from built-in user attributes or adding your own custom attributes.

| Intended for | Collaborating with business partners from external organizations like suppliers, partners, and vendors. These users might or might not have Microsoft Entra ID or managed IT. | Consumers and business customers of your app. These users are managed in a Microsoft Entra tenant that's configured for external apps and users. | | User management | You manage B2B collaboration users in the same workforce tenant as employees but typically annotate them as guest users. You can manage guest users the same way as employees and add them to the same groups. You can use cross-tenant access settings to determine which users have access to B2B collaboration. | You manage app users in an external tenant that you create for consumers of your application. Users in an external tenant have different default permissions than users in a workforce tenant. The external tenant is separate from the organization's employee directory. | | Single sign-on (SSO) | SSO to all Microsoft Entra-connected apps is supported. For example, you can provide access to Microsoft 365 or on-premises apps, and to other SaaS apps such as Salesforce or Workday. | SSO to apps registered in the external tenant is supported. SSO to Microsoft 365 or to other Microsoft SaaS apps isn't supported. | | Company branding | The default state for the authentication experience is a Microsoft design. Administrators can customize the guest sign-in experience with their company branding. | TheFor Microsoft-hosted authentication, the default branding for the external tenant is neutral and doesn't include any existing Microsoft branding. Administrators can customize the branding for the organization or per application. Learn more. |
| Microsoft cloud settings | Supported. | Not applicable. | | Entitlement management | Supported. | Not applicable. |

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…