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;
Not supported.
| Event | Microsoft-hosted authentication | Embedded native authentication | Bring Your Own UX |
|---|---|---|---|
OnAttributeCollectionStart |
![]() |
![]() |
![]() |
OnAttributeCollectionSubmit |
![]() |
![]() |
![]() |
OnOtpSend (email) |
![]() |
![]() |
![]() |
OnPasswordSubmit | ![]() | ![]() | ![]() |
OnTokenIssuanceStart |
![]() |
![]() |
![]() |
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).
| 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 |
| Embedded native authentication for mobile apps | Not |
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 |
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 |
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 |
Configure a custom email provider for one-time passcode send events. Learn more. |
OnPasswordSubmit | Not 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. Not applicable means the method isn't used for that operation.
| Method | Sign-in | Sign-up | Password reset | MFA |
|---|---|---|---|---|
| Email with password | ![]() |
![]() |
Not applicable | Not applicable |
| Email one-time passcode | ![]() |
![]() |
![]() |
![]() |
| SMS-based authentication | Not applicable | Not applicable | ![]() |
![]() |
| Time-based one-time password (TOTP) | Not applicable | Not applicable | Not applicable | ![]() |
| Passkey (FIDO2) | ![]() |
Not applicable | Not applicable | ![]() |
| Apple federation | ![]() |
![]() |
Not applicable | Not applicable |
| Facebook federation | ![]() |
![]() |
Not applicable | Not applicable |
| Google federation | ![]() |
![]() |
Not applicable | Not applicable |
| Microsoft personal account (OpenID Connect) | ![]() |
![]() |
Not applicable | Not applicable |
| Microsoft Entra ID federation | ![]() |
![]() |
Not applicable | Not applicable |
| OpenID Connect federation | ![]() |
![]() |
Not applicable | Not applicable |
| SAML/WS-Fed federation | ![]() |
![]() |
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. | Notoffline_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 Consent and permission features for enterprise applications
| Feature | Workforce tenant | External tenant |
|---|---|---|
| OpenID Connect | ||
| Authorization code | ||
| Authorization code with Proof Key for Code Exchange (PKCE) | ||
| Client credentials | Supported for v2.0 applications. | |
| Device authorization | ||
| On-behalf-of flow | ||
| Implicit grant | ||
| Resource owner password credentials |
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 |
| Self-service sign-up | Not |
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
@@ -2,7 +2,7 @@ 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/2026+ms.date: 11/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.@@ -64,7 +64,7 @@ Password recovery support doesn't imply support for Microsoft-hosted reset-page | --- | --- | --- | --- | | **Recovery: email one-time passcode** | Supported. | Supported. | Supported. | | **Recovery: SMS** | Supported. | Supported. | Supported. |-| **Recovery during sign-in** | Available through configured sign-in pages. | The API can offer recovery through the current password method. | Can follow recovery offered by the current transaction. |+| **Recovery during sign-in** | Supported through configured sign-in pages. | Supported when offered through the current password method. | Supported when offered by the current transaction. | ### Multifactor authentication behavior @@ -76,7 +76,7 @@ For [tenant MFA configuration](concept-multifactor-authentication-customers.md) | **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](concept-multifactor-authentication-customers.md#enabling-mfa-methods). | Not supported. | Not supported. |-| **Additional verification for sensitive actions after sign-in** | Available through configured authentication context. | Not supported. | Available through configured authentication context. |+| **Additional verification for sensitive actions after sign-in** | Supported through configured authentication context. | Not supported. | Supported through configured authentication context. | ### Branding and language scope @@ -87,7 +87,7 @@ These rows describe Microsoft-hosted customization settings, not whether an appl | **Tenant-wide company branding** | Supported. See [Branding](concept-branding-customers.md). | 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](~/fundamentals/how-to-customize-branding-themes-apps.md). | 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 Native Authentication API calls. | Required for Native Authentication API calls, the custom authentication page, and the Entra authentication endpoints. |+| **Service custom URL domain** | Optional for Microsoft-hosted authentication. | Required for browser-based apps using the Native Authentication API V2, such as SPAs; not required for non-browser clients using native HTTP transports. | Required for calls to the Native Authentication API, the custom authentication page, and the Microsoft Entra authentication endpoints. | <a name="custom-authentication-extension-events-by-approach"></a> @@ -95,12 +95,17 @@ These rows describe Microsoft-hosted customization settings, not whether an appl 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;  Not supported.+ | Event | Microsoft-hosted authentication | Embedded native authentication | Bring Your Own UX | | --- | --- | --- | --- |-| **`OnAttributeCollectionStart`** | Supported. | Not supported. | Not supported. |-| **`OnAttributeCollectionSubmit`** | Supported. | Not supported. | Not supported. |-| **`OnOtpSend` (email)** | Supported. | Supported. | Supported. |-| **`OnTokenIssuanceStart`** | Supported. | Supported. | Supported. |+| **`OnAttributeCollectionStart`** |  |  |  |+| **`OnAttributeCollectionSubmit`** |  |  |  |+| **`OnOtpSend` (email)** |  |  |  |+| **`OnPasswordSubmit`** |  |  |  |+| **`OnTokenIssuanceStart`** |  |  |  |++`OnPasswordSubmit` supports [just-in-time password migration](how-to-migrate-passwords-just-in-time.md) from a legacy identity provider during sign-in. It isn't a general-purpose password-validation event. ### Integration, policy, and sessions by approach @@ -113,7 +118,7 @@ Session reuse, persistent sessions, and coordinated sign-out are different capab | **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](~/identity/conditional-access/concept-conditional-access-session.md#persistent-browser-session) and/or the [**Stay signed in?**](how-to-user-flow-sign-up-sign-in-customers.md#control-the-stay-signed-in-prompt) user prompt. | Native authentication does not establish an Entra session. | Use the [**Persistent browser session**](~/identity/conditional-access/concept-session-lifetime.md#persistence-of-browsing-sessions) 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 current Native Authentication API integrations. | An account picker on the self-hosted authentication page isn't currently 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](#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](../../identity-platform/reference-native-authentication.md#security-and-diagnostics). | Use the Native Authentication API request diagnostics and relying-application authorization diagnostics. | @@ -133,8 +138,8 @@ The following table compares the general features and capabilities in workforce | Local accounts | Local accounts are supported for *internal* members of your organization only. | Local accounts are supported for:<ul><li> Consumers and business customers who use self-service sign-up. </li><li>Admin-created internal accounts (with or without an admin role).</li></ul> All users in an external tenant have [default permissions](reference-user-permissions.md) unless they're [assigned an admin role](how-to-manage-admin-accounts.md). | | Groups | Use [groups](/entra/fundamentals/how-to-manage-groups) to manage administrative and user accounts. | Use groups to manage administrative accounts. Support for Microsoft Entra groups and [application roles](how-to-use-app-roles-customers.md) is being phased into customer tenants. For the latest updates, see [Groups and application roles support](reference-group-app-roles-support.md). | | Roles and administrators | [Roles and administrators](~/fundamentals/how-subscriptions-associated-directory.md) are fully supported for administrative and user accounts. | Roles are supported for all users. All users in an external tenant have [default permissions](reference-user-permissions.md) unless they're assigned an [admin role](how-to-manage-admin-accounts.md). |-| 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. |-| Microsoft Entra ID Governance | This product enables organizations to govern identity and access lifecycles, along with secure privileged access. [Learn more](~/id-governance/identity-governance-overview.md). | Not available. |+| 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 supported. |+| Microsoft Entra ID Governance | This product enables organizations to govern identity and access lifecycles, along with secure privileged access. [Learn more](~/id-governance/identity-governance-overview.md). | Not 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](how-to-enable-password-reset-customers.md). | | 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](concept-branding-customers.md). | | 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](how-to-define-custom-attributes.md). |@@ -148,8 +153,8 @@ The following table compares the features for interface customization in workfor | ------- | ---------------- | --------------- | | Company branding | You can add [company branding](~/fundamentals/how-to-customize-branding.md) that applies to all these experiences to create a consistent sign-in experience for your users. | Supported. [Customize branding](how-to-customize-branding-customers.md). | | Language customization | [Customize the sign-in experience by browser language](~/fundamentals/how-to-customize-branding.md). | Supported. [Customize languages](how-to-customize-languages-customers.md). |-| Custom domain names | You can use [custom domains](~/fundamentals/add-custom-domain.md) for administrative accounts only. | A [tenant-verified custom URL domain](concept-custom-url-domain.md) is required for all current Native Authentication API and BYO UX service API calls. It's optional for Microsoft-hosted authentication. |-| Embedded native authentication for mobile apps | Not available. | [Embedded native authentication](../../identity-platform/concept-native-authentication.md) 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](~/identity-platform/reference-native-authentication.md) or [SDK integration guidance](~/identity-platform/concept-native-authentication.md#how-to-use-native-authentication). |+| Custom domain names | You can use [custom domains](~/fundamentals/add-custom-domain.md) for administrative accounts only. | A [tenant-verified custom URL domain](concept-custom-url-domain.md) is required for browser-based apps using the Native Authentication API V2 and for BYO UX. It isn't required for non-browser native HTTP clients and is optional for Microsoft-hosted authentication. |+| Embedded native authentication for mobile apps | Not supported. | [Embedded native authentication](../../identity-platform/concept-native-authentication.md) 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](~/identity-platform/reference-native-authentication.md) or [SDK integration guidance](~/identity-platform/concept-native-authentication.md#how-to-use-native-authentication). | <a name="adding-your-own-business-logic"></a> @@ -161,9 +166,10 @@ The following table compares the events for custom authentication extensions in | Event | Workforce tenant | External tenant | | ----- | ---------------- | --------------- |-| **`OnAttributeCollectionStart`** | Not available. | 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](~/identity-platform/custom-extension-attribute-collection.md?toc=%2Fentra%2Fexternal-id%2Ftoc.json&bc=%2Fentra%2Fexternal-id%2Fbreadcrumb%2Ftoc.json&tabs=start-continue%2Csubmit-continue). |-| **`OnAttributeCollectionSubmit`** | Not available. | 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](~/identity-platform/custom-extension-attribute-collection.md?toc=%2Fentra%2Fexternal-id%2Ftoc.json&bc=%2Fentra%2Fexternal-id%2Fbreadcrumb%2Ftoc.json&tabs=start-continue%2Csubmit-continue). |-| **`OnOtpSend` (email)** | Not available. | Configure a custom email provider for one-time passcode send events. [Learn more](~/identity-platform/custom-extension-email-otp-get-started.md?toc=%2Fentra%2Fexternal-id%2Ftoc.json&bc=%2Fentra%2Fexternal-id%2Fbreadcrumb%2Ftoc.json&tabs=azure-communication-services%2Cazure-portal). |+| **`OnAttributeCollectionStart`** | Not 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](~/identity-platform/custom-extension-attribute-collection.md?toc=%2Fentra%2Fexternal-id%2Ftoc.json&bc=%2Fentra%2Fexternal-id%2Fbreadcrumb%2Ftoc.json&tabs=start-continue%2Csubmit-continue). |+| **`OnAttributeCollectionSubmit`** | Not 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](~/identity-platform/custom-extension-attribute-collection.md?toc=%2Fentra%2Fexternal-id%2Ftoc.json&bc=%2Fentra%2Fexternal-id%2Fbreadcrumb%2Ftoc.json&tabs=start-continue%2Csubmit-continue). |+| **`OnOtpSend` (email)** | Not supported. | Configure a custom email provider for one-time passcode send events. [Learn more](~/identity-platform/custom-extension-email-otp-get-started.md?toc=%2Fentra%2Fexternal-id%2Ftoc.json&bc=%2Fentra%2Fexternal-id%2Fbreadcrumb%2Ftoc.json&tabs=azure-communication-services%2Cazure-portal). |+| **`OnPasswordSubmit`** | Not supported. | Migrate a customer's password from a legacy identity provider during sign-in. See [Just-in-time password migration](how-to-migrate-passwords-just-in-time.md). | | **`OnTokenIssuanceStart`** | [Add claims from external systems](~/identity-platform/custom-extension-overview.md). | [Add claims from external systems](./concept-custom-extensions.md). | ## Identity providers and authentication methods@@ -184,20 +190,22 @@ You can use some authentication methods as the primary factor when users sign in This table lists tenant-level method availability. Confirm method and journey availability for your approach in the [approach-specific guidance](#authentication-approach-supportability). +**Legend:**  Supported. Not applicable means the method isn't used for that operation.+ | Method | Sign-in | Sign-up | Password reset | MFA | | --------- | --------- | --------- | --------- | --------- |-| [Email with password](./concept-authentication-methods-customers.md#email-and-password-sign-in) | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| [Email one-time passcode](./concept-authentication-methods-customers.md#email-with-one-time-passcode-sign-in) | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: |-| [SMS-based authentication](./concept-multifactor-authentication-customers.md#sms-based-authentication) | | | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: |-| [Time-based one-time password (TOTP)](./concept-multifactor-authentication-customers.md#time-based-one-time-password-totp) | | | | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: |-| [Passkey (FIDO2)](./how-to-sign-in-with-passkey.md) | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: |-| [Apple federation](./how-to-apple-federation-customers.md) | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| [Facebook federation](./how-to-facebook-federation-customers.md) | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| [Google federation](./how-to-google-federation-customers.md) | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| Microsoft personal account ([OpenID Connect](./how-to-custom-oidc-federation-customers.md)) | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| [Microsoft Entra ID federation](./how-to-entra-id-federation-customers.md) | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| [OpenID Connect federation](./how-to-custom-oidc-federation-customers.md) | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| [SAML/WS-Fed federation](../direct-federation.md) | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |+| [Email with password](./concept-authentication-methods-customers.md#email-and-password-sign-in) |  |  | Not applicable | Not applicable |+| [Email one-time passcode](./concept-authentication-methods-customers.md#email-with-one-time-passcode-sign-in) |  |  |  |  |+| [SMS-based authentication](./concept-multifactor-authentication-customers.md#sms-based-authentication) | Not applicable | Not applicable |  |  |+| [Time-based one-time password (TOTP)](./concept-multifactor-authentication-customers.md#time-based-one-time-password-totp) | Not applicable | Not applicable | Not applicable |  |+| [Passkey (FIDO2)](./how-to-sign-in-with-passkey.md) |  | Not applicable | Not applicable |  |+| [Apple federation](./how-to-apple-federation-customers.md) |  |  | Not applicable | Not applicable |+| [Facebook federation](./how-to-facebook-federation-customers.md) |  |  | Not applicable | Not applicable |+| [Google federation](./how-to-google-federation-customers.md) |  |  | Not applicable | Not applicable |+| Microsoft personal account ([OpenID Connect](./how-to-custom-oidc-federation-customers.md)) |  |  | Not applicable | Not applicable |+| [Microsoft Entra ID federation](./how-to-entra-id-federation-customers.md) |  |  | Not applicable | Not applicable |+| [OpenID Connect federation](./how-to-custom-oidc-federation-customers.md) |  |  | Not applicable | Not applicable |+| [SAML/WS-Fed federation](../direct-federation.md) |  |  | Not applicable | Not applicable | ## Application registration @@ -213,7 +221,7 @@ The following table compares the features for [application registration](../../i | Implicit grant and hybrid flows for authentication | Request a token directly from the authorization endpoint. | Supported. | | Certificates and secrets | Multiple credentials are available: <ul><li>[Certificates](../../identity-platform/how-to-add-credentials.md?tabs=certificate)</li><li>[Client secrets](../../identity-platform/how-to-add-credentials.md?tabs=client-secret)</li><li>[Federated credentials](../../identity-platform/how-to-add-credentials.md?tabs=federated-credential)</li></ul> | 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](../../identity-platform/how-to-add-credentials.md?tabs=certificate), [secrets](../../identity-platform/how-to-add-credentials.md?tabs=client-secret), and [federated credentials](../../identity-platform/how-to-add-credentials.md?tabs=federated-credential) 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](~/identity/enterprise-apps/tutorial-enforce-secret-standards.md) to enforce secret and certificate restrictions. | Not available. |+| Policy for certificates and secrets | Configure the [application management policies](~/identity/enterprise-apps/tutorial-enforce-secret-standards.md) to enforce secret and certificate restrictions. | Not 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](../../identity-platform/howto-update-permissions.md). | 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](../../identity-platform/quickstart-configure-app-expose-web-apis.md) 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](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator)) can view and edit the application registration. | App ownership is supported, but [default permissions](reference-user-permissions.md#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. |@@ -239,7 +247,7 @@ The following table compares the unique features for [enterprise application](/e | Application gallery | The [application gallery](/entra/identity/enterprise-apps/overview-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.](/entra/identity/enterprise-apps/add-application-portal) | [Register a SAML app in your external tenant.](/entra/external-id/customers/how-to-register-saml-app) | | Self-service application assignment | Let users [self-discover apps](/entra/identity/enterprise-apps/manage-self-service-access). | Self-service application assignment in the [My Apps portal](/entra/identity/enterprise-apps/myapps-overview) isn't available. |-| Application proxy | [Microsoft Entra application proxy](/entra/identity/app-proxy/overview-what-is-app-proxy) provides secure remote access to on-premises web applications. | Not available. |+| Application proxy | [Microsoft Entra application proxy](/entra/identity/app-proxy/overview-what-is-app-proxy) provides secure remote access to on-premises web applications. | Not supported. | | Deactivate app registration | [Deactivate an app registration](/entra/identity/enterprise-apps/deactivate-app-registration) to prevent token issuance while preserving configuration. | Supported. | ### Consent and permission features for enterprise applications@@ -261,20 +269,20 @@ The following table compares tenant-level OAuth 2.0 and OpenID Connect capabilit | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- |-| [OpenID Connect](../../identity-platform/v2-protocols-oidc.md) | Yes | Yes |-| [Authorization code](../../identity-platform/v2-oauth2-auth-code-flow.md) | Yes | Yes |-| [Authorization code with Proof Key for Code Exchange (PKCE)](../../identity-platform/v2-oauth2-auth-code-flow.md) | Yes | Yes |-| [Client credentials](../../identity-platform/v2-oauth2-client-creds-grant-flow.md) | Yes | [v2.0 applications](../../identity-platform/reference-app-manifest.md) |-| [Device authorization](../../identity-platform/v2-oauth2-device-code.md) | Yes | Yes |-| [On-behalf-of flow](../../identity-platform/v2-oauth2-on-behalf-of-flow.md) | Yes | Yes |-| [Implicit grant](../../identity-platform/v2-oauth2-implicit-grant-flow.md) | Yes | Yes |-| [Resource owner password credentials](../../identity-platform/v2-oauth-ropc.md) | Yes | No; for mobile applications, use [Embedded native authentication](../../identity-platform/concept-native-authentication.md) |+| [OpenID Connect](../../identity-platform/v2-protocols-oidc.md) | Supported. | Supported. |+| [Authorization code](../../identity-platform/v2-oauth2-auth-code-flow.md) | Supported. | Supported. |+| [Authorization code with Proof Key for Code Exchange (PKCE)](../../identity-platform/v2-oauth2-auth-code-flow.md) | Supported. | Supported. |+| [Client credentials](../../identity-platform/v2-oauth2-client-creds-grant-flow.md) | Supported. | Supported for [v2.0 applications](../../identity-platform/reference-app-manifest.md). |+| [Device authorization](../../identity-platform/v2-oauth2-device-code.md) | Supported. | Supported. |+| [On-behalf-of flow](../../identity-platform/v2-oauth2-on-behalf-of-flow.md) | Supported. | Supported. |+| [Implicit grant](../../identity-platform/v2-oauth2-implicit-grant-flow.md) | Supported. | Supported. |+| [Resource owner password credentials](../../identity-platform/v2-oauth-ropc.md) | Supported. | Not supported; for mobile applications, use [Embedded native authentication](../../identity-platform/concept-native-authentication.md). | ### 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 current Native Authentication API and Bring Your Own UX (BYO UX) service API calls, use a [tenant-verified custom domain](concept-custom-url-domain.md). Include the tenant GUID in the URL path.+For browser-based apps using the Native Authentication API V2 and Bring Your Own UX (BYO UX), use a [tenant-verified custom domain](concept-custom-url-domain.md) 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](~/identity-platform/how-to-native-authentication-configure-app.md#configure-the-api-authority). The following JSON shows a Microsoft-hosted authentication example in a .NET application's `appsettings.json` file: @@ -305,8 +313,8 @@ The following table compares the features for terms-of-use policies in each type | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- |-| Conditional Access policies | See the [Microsoft Entra terms of use](~/identity/conditional-access/terms-of-use.md). | Not available. |-| Self-service sign-up | Not available. | Add a [required attribute](how-to-define-custom-attributes.md#configure-a-single-select-checkbox-checkboxsingleselect) linked to your terms-of-use policies on the sign-up page. You can customize the hyperlink to support various languages. |+| Conditional Access policies | See the [Microsoft Entra terms of use](~/identity/conditional-access/terms-of-use.md). | Not supported. |+| Self-service sign-up | Not supported. | Add a [required attribute](how-to-define-custom-attributes.md#configure-a-single-select-checkbox-checkboxsingleselect) 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](~/fundamentals/how-to-customize-branding.md). | [Add privacy and terms-of-use links](how-to-customize-branding-customers.md#to-customize-the-logo-privacy-link-and-terms-of-use). | ## Account management@@ -392,11 +400,11 @@ The following table compares the features for activity logs and reports across v | ------- | ---------------- | --------------- | | [Audit logs](~/identity/monitoring-health/concept-audit-logs.md) | 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](~/identity/monitoring-health/concept-sign-ins.md) | 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](~/identity/monitoring-health/concept-sign-ups.md) | Not available. | Microsoft Entra External ID logs all self-service sign-up events, including both successful sign-ups and failed attempts. |-| [Provisioning logs](~/identity/monitoring-health/concept-provisioning-logs.md) | The provisioning logs provide detailed records of provisioning events within a tenant, such as user account creations, updates, and deletions. | Not available. |+| [Sign-up logs](~/identity/monitoring-health/concept-sign-ups.md) | Not supported. | Microsoft Entra External ID logs all self-service sign-up events, including both successful sign-ups and failed attempts. |+| [Provisioning logs](~/identity/monitoring-health/concept-provisioning-logs.md) | The provisioning logs provide detailed records of provisioning events within a tenant, such as user account creations, updates, and deletions. | Not supported. | | [Activity logs for retention policies](~/identity/monitoring-health/concept-provisioning-logs.md) | 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](~/identity/monitoring-health/howto-configure-diagnostic-settings.md) | 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](./how-to-azure-monitor.md). |-| [Reports for application user activity](./how-to-user-insights.md) (retiring August 31, 2026; see [migration guidance](./how-to-user-insights.md#migrate-from-user-insights)) | Not available. | 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. |+| [Reports for application user activity](./how-to-user-insights.md) (retiring August 31, 2026; see [migration guidance](./how-to-user-insights.md#migrate-from-user-insights)) | Not 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 