Microsoft Entra External ID
Authentication

Supported Features

In brief

The support matrix now documents OnPasswordSubmit across the listed integration paths and its support for just-in-time password migration during sign-in. It also clarifies custom URL domain requirements for browser-based API V2 apps versus non-browser native clients, and updates recovery and verification labels.

What Entra admins need to know

Admins can use the revised matrix to validate client domain configuration and sign-in integration support.

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.

title: Supported Features description: Compare Microsoft Entra External ID features in workforce and external tenants, and confirm authentication approach support to plan your customer apps. ms.topic: concept-article ms.date: 11/12/17/2026 ms.custom: it-pro, seo-july-2024, sfi-ropc-nochange, msecd-doc-authoring-1030 ai-usage: ai-assisted

#customer intent: As an application developer or IT administrator, I want to compare tenant features and authentication approach support so that I can plan my customer-facing applications. | --- | --- | --- | --- | | Recovery: email one-time passcode | Supported. | Supported. | Supported. | | Recovery: SMS | Supported. | Supported. | Supported. | | Recovery during sign-in | AvailableSupported through configured sign-in pages. | The API can offer recoverySupported when offered through the current password method. | Can follow recoverySupported when offered by the current transaction. |

Multifactor authentication behavior

| Method registration during sign-in | Supported. | Supported for offered email and SMS methods. | Supported for offered email and SMS methods. | | Time-based one-time password (TOTP) | Supported. | Not supported. | Not supported. | | Passkey sign-in or MFA | Supported, subject to passkey restrictions. | Not supported. | Not supported. | | Additional verification for sensitive actions after sign-in | AvailableSupported through configured authentication context. | Not supported. | AvailableSupported through configured authentication context. |

Branding and language scope

| Tenant-wide company branding | Supported. See Branding. | Hosted branding settings don't apply to native screens. | Hosted branding settings don't apply to the self-hosted page. | | Application-specific branding themes | Supported. See Branding themes. | Hosted themes don't apply to native screens. | Hosted themes don't apply to the self-hosted page. | | Hosted language customization | Supported for Microsoft-hosted pages. | Hosted language settings don't configure native interface text. | Hosted language settings don't configure the self-hosted page's text. | | Service custom URL domain | Optional for Microsoft-hosted authentication. | Required for browser-based apps using the Native Authentication API calls.V2, such as SPAs; not required for non-browser clients using native HTTP transports. | Required for calls to the Native Authentication API calls,API, the custom authentication page, and the Microsoft Entra authentication endpoints. |

The following comparison describes event availability, not interchangeable request or response payloads. Use the event's documented contract and the current operation's returned data.

Legend: Supported Supported; Not supported Not supported.

Event Microsoft-hosted authentication Embedded native authentication Bring Your Own UX
OnAttributeCollectionStart Supported.Supported Not supported.Not supported Not supported.Not supported
OnAttributeCollectionSubmit Supported.Supported Not supported.Not supported Not supported.Not supported
OnOtpSend (email) Supported.Supported Supported.Supported Supported.Supported
OnPasswordSubmitSupportedSupportedSupported
OnTokenIssuanceStart Supported.Supported Supported.Supported Supported.Supported

OnPasswordSubmit supports just-in-time password migration from a legacy identity provider during sign-in. It isn't a general-purpose password-validation event.

Integration, policy, and sessions by approach

| Existing browser session reuse | Supported when the session satisfies the request. | Native authentication does not establish an Entra session. | A session that satisfies the authorization request skips the self-hosted page. | | Persistent browser session | Controlled through Conditional Access and/or the Stay signed in? user prompt. | Native authentication does not establish an Entra session. | Use the Persistent browser session Conditional Access control. | | Browser fallback and transaction resume | Uses Microsoft-hosted pages. | A separately configured browser sign-in starts a new attempt; it doesn't resume native progress. | Inline escape to Microsoft-hosted pages and resumption of the same transaction isn't supported. | | Account selection on the authentication page | Microsoft-hosted account selection appears during OAuth processing. | Not used by the current Native Authentication API integrations. | An account picker on the self-hosted authentication page isn't currently supported. | | Sign-out across applications | Supported for configured browser applications as described in Single sign-on. | Sign-out is application-specific. | Manage relying-application and browser sessions separately; the self-hosted authentication page doesn't currently offer a logout hook. | | Authentication diagnostics | Use sign-in logs. | Record HTTP status codes, request IDs, correlation IDs, and timestamps without exposing sensitive data. See API diagnostics. | Use the Native Authentication API request diagnostics and relying-application authorization diagnostics. |

| Local accounts | Local accounts are supported for internal members of your organization only. | Local accounts are supported for:

  • Consumers and business customers who use self-service sign-up.
  • Admin-created internal accounts (with or without an admin role).
All users in an external tenant have default permissions unless they're assigned an admin role. | | Groups | Use groups to manage administrative and user accounts. | Use groups to manage administrative accounts. Support for Microsoft Entra groups and application roles is being phased into customer tenants. For the latest updates, see Groups and application roles support. | | Roles and administrators | Roles and administrators are fully supported for administrative and user accounts. | Roles are supported for all users. All users in an external tenant have default permissions unless they're assigned an admin role. | | Microsoft Entra ID Protection | This product provides ongoing risk detection for your Microsoft Entra tenant. It allows organizations to discover, investigate, and remediate identity-based risks. | Not available.supported. | | Microsoft Entra ID Governance | This product enables organizations to govern identity and access lifecycles, along with secure privileged access. Learn more. | Not available.supported. | | Self-service password reset | Allow users to reset their password by using up to two authentication methods. | Allow users to reset their password by using email with a one-time passcode or SMS. Learn more. | | Language customization | Customize the sign-in experience based on browser language when users authenticate into your corporate intranet or web-based applications. | Use languages to modify the strings displayed to your customers as part of the sign-in and sign-up process. Learn more. |

Custom attributes Use directory extension attributes to store more data in the Microsoft Entra directory for user objects, groups, tenant details, and service principals. Use directory extension attributes to store more data in the customer directory for user objects. Create custom user attributes and add them to your sign-up user flow. Learn more.
Company branding You can add company branding that applies to all these experiences to create a consistent sign-in experience for your users. Supported. Customize branding.
Language customization Customize the sign-in experience by browser language. Supported. Customize languages.
Custom domain names You can use custom domains for administrative accounts only. A tenant-verified custom URL domain is required for all currentbrowser-based apps using the Native Authentication API V2 and for BYO UX service API calls.UX. It isn'st required for non-browser native HTTP clients and is optional for Microsoft-hosted authentication.
Embedded native authentication for mobile apps Not available.supported. Embedded native authentication gives you control over the design of your mobile application's sign-in experiences. Confirm support for your API or SDK version in the Native Authentication API reference or SDK integration guidance.

Event Workforce tenant External tenant
OnAttributeCollectionStart Not available.supported. This event occurs at the beginning of the sign-up's attribute collection step, before the attribute collection page renders. You can add actions such as prefilling values and displaying a blocking error. Learn more.
OnAttributeCollectionSubmit Not available.supported. This event occurs during the sign-up flow, after the user enters and submits attributes. You can add actions such as validating or modifying the user's entries. Learn more.
OnOtpSend (email) Not available.supported. Configure a custom email provider for one-time passcode send events. Learn more.
OnPasswordSubmitNot supported.Migrate a customer's password from a legacy identity provider during sign-in. See Just-in-time password migration.
OnTokenIssuanceStart Add claims from external systems. Add claims from external systems.

Identity providers and authentication methods

This table lists tenant-level method availability. Confirm method and journey availability for your approach in the approach-specific guidance.

Legend: Supported Supported. Not applicable means the method isn't used for that operation.

Method Sign-in Sign-up Password reset MFA
Email with password Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Not applicable Not applicable
Email one-time passcode Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported
SMS-based authentication Not applicable Not applicable Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported
Time-based one-time password (TOTP) Not applicable Not applicable Not applicable Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported
Passkey (FIDO2) Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Not applicable Not applicable Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported
Apple federation Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Not applicable Not applicable
Facebook federation Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Not applicable Not applicable
Google federation Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Not applicable Not applicable
Microsoft personal account (OpenID Connect) Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Not applicable Not applicable
Microsoft Entra ID federation Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Not applicable Not applicable
OpenID Connect federation Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Not applicable Not applicable
SAML/WS-Fed federation Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false":::Supported Not applicable Not applicable

Application registration

| Implicit grant and hybrid flows for authentication | Request a token directly from the authorization endpoint. | Supported. | | Certificates and secrets | Multiple credentials are available:

| Certificates, client secrets, and federated credentials. | | Rotation for certificates and secrets | Update client credentials to help ensure that they remain valid and secure, while users can continue to sign-in. You can rotate certificates, secrets, and federated credentials by adding a new one and then removing the old one. | Supported for certificates, client secrets, and federated credentials. | | Policy for certificates and secrets | Configure the application management policies to enforce secret and certificate restrictions. | Not available.supported. | | API permissions | Add, remove, and replace permissions to an application. After permissions are added to your application, users or admins need to grant consent to the new permissions. Learn more about updating an app's requested permissions in Microsoft Entra ID. | The following permissions are allowed: Microsoft Graph offline_access, openid, and User.Read, along with your My APIs delegated permissions. Only an admin can consent on behalf of the organization. | | Expose an API | Define custom scopes to restrict access to data and functionality that the API helps protect. An application that requires access to parts of this API can request user or admin consent to one or more of these scopes. | Supported. | | Owners | Application owners can view and edit the application registration. Additionally, any user (who might not be listed) with administrative privileges to manage any application (for example, Cloud Application Administrator) can view and edit the application registration. | App ownership is supported, but default permissions differ from workforce tenants. Owners, including invited users, should be assigned the Application Developer role to manage credentials and other properties of owned app registrations. The Application Administrator and Cloud Application Administrator roles provide broader application-management permissions, regardless of ownership. | | Application gallery | The application gallery contains thousands of applications that are integrated into Microsoft Entra ID. | Choose from a range of integrated apps. To find a partner app, use the search bar. The application gallery catalog isn't available. | | Register a custom enterprise application | Add an enterprise application. | Register a SAML app in your external tenant. | | Self-service application assignment | Let users self-discover apps. | Self-service application assignment in the My Apps portal isn't available. | | Application proxy | Microsoft Entra application proxy provides secure remote access to on-premises web applications. | Not available.supported. | | Deactivate app registration | Deactivate an app registration to prevent token issuance while preserving configuration. | Supported. |

Consent and permission features for enterprise applications

Feature Workforce tenant External tenant
OpenID Connect YesSupported. YesSupported.
Authorization code YesSupported. YesSupported.
Authorization code with Proof Key for Code Exchange (PKCE) YesSupported. YesSupported.
Client credentials YesSupported. Supported for v2.0 applications.
Device authorization YesSupported. YesSupported.
On-behalf-of flow YesSupported. YesSupported.
Implicit grant YesSupported. YesSupported.
Resource owner password credentials YesSupported. No;Not supported; for mobile applications, use Embedded native authentication.

Authority URL in OpenID Connect and OAuth2 flows

The authority URL indicates a directory that the Microsoft Authentication Library (MSAL) can request tokens from. For Microsoft-hosted authentication in external tenants, use the default <tenant-name>.ciamlogin.com domain or a tenant-verified custom URL domain.

For currentbrowser-based apps using the Native Authentication API V2 and Bring Your Own UX (BYO UX) service API calls,, use a tenant-verified custom domain. Include and include the tenant GUID in the URL path. This browser requirement helps protect against cross-site request forgery (CSRF). Non-browser clients, such as iOS and Android apps using native HTTP transports, don't require a custom domain. See Configure the API authority.

The following JSON shows a Microsoft-hosted authentication example in a .NET application's appsettings.json file:

Feature Workforce tenant External tenant
Conditional Access policies See the Microsoft Entra terms of use. Not available.supported.
Self-service sign-up Not available.supported. Add a required attribute linked to your terms-of-use policies on the sign-up page. You can customize the hyperlink to support various languages.
Sign-in page You can add links to the lower-right corner for privacy information by using company branding. Add privacy and terms-of-use links.

Account management

| ------- | ---------------- | --------------- | | Audit logs | These logs provide a detailed report of all events logged in Microsoft Entra ID, including modifications to applications, groups, and users. | Supported. | | Sign-in logs | The sign-in logs track all sign-in activities within a Microsoft Entra tenant, including access to your applications and resources. | Supported. | | Sign-up logs | Not available.supported. | Microsoft Entra External ID logs all self-service sign-up events, including both successful sign-ups and failed attempts. | | Provisioning logs | The provisioning logs provide detailed records of provisioning events within a tenant, such as user account creations, updates, and deletions. | Not available.supported. | | Activity logs for retention policies | Microsoft Entra data retention policies determine how long various types of logs (like audit, sign-in, and provisioning logs) are stored. | Seven days. | | Export activity logs | By using diagnostic settings in Microsoft Entra ID, you can integrate logs with Azure Monitor, stream logs to an event hub, or integrate with security information and event management (SIEM) tools. | Azure Monitor for external tenants. | | Reports for application user activity (retiring August 31, 2026; see migration guidance) | Not available.supported. | Application user activity provides analytics on how users interact with registered applications in your tenant. It tracks metrics like active users, new users, sign-ins, and MFA success rates. |

Microsoft Graph APIs

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…