Supported Features
In brief
The Supported Features page now compares customer authentication methods, journeys, integration, policies, and sessions across external-tenant approaches. It also clarifies API-version and SDK support and identifies Native Authentication API V2, BYO UX, and username or alias sign-in as previews.
What Entra admins need to know
Administrators can use the updated comparisons to plan customer apps and verify required tenant methods, policies, API versions, and SDK 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.
Supported features in Microsoft Entra External ID workforce and external tenants
There are two ways to configure a Microsoft Entra tenant,External ID supports two tenant configurations, depending on how an organization intends to use the tenantyour audience and the resources that you want to manage:
- A workforce tenant configuration is for your employees, internal business apps, and other organizational resources. A workforce tenant uses
B2Bbusiness-to-business (B2B) collaboration in Microsoft Entra External IDfor collaborationto work with external business partners and guests. - An external tenant configuration is exclusively for External ID scenarios where you want to publish apps to consumers or business customers.
This article gives a detailed comparison of the features and capabilitiesprovides two comparisons:
- To choose how customer apps present authentication, review authentication approach support in external tenants.
- To compare workforce and external
tenants.tenant capabilities, start with the general feature comparison.
For more information about these tenants, see Workforce and external tenant configurations in Microsoft Entra External ID.
General feature comparison
The following table compares the general features and capabilities in workforce and external tenants.
| Feature | Workforce tenant | External tenant |
Interface customization
The following table compares the features for interface customization in workforce and external tenants.
| Feature | Workforce tenant | External tenant | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Company branding | You can add company brandingAuthentication approach supportCompare methods and journeys and integration, policy, and sessions for customer-app authentication in external tenants. For architectural choices, see Choose an authentication approach. Company branding and branding themes are presentation options within Microsoft-hosted authentication, not separate authentication approaches. For SDK integrations, use a release compatible with the current API that supports the operations your app requires. See the Native authentication overview and platform-specific SDK guidance. SDK support varies by platform and version. For API operations, see the Native Authentication API reference. How to read the comparison: "Supported" applies to the approach and API version described here, not to every SDK. Configure required tenant methods and policies before using a supported operation. Methods and journeys by approachThe following table compares local-account methods and federation. For provider configuration, see Identity providers for external tenants. Password recovery and multifactor authentication (MFA) have separate comparisons.
Use only methods and operations returned for the active transaction. A tenant can contain providers or methods that aren't available through the selected integration. Password reset behavior and controlsPassword recovery support doesn't imply support for Microsoft-hosted reset-page settings. Passwordless email one-time-passcode accounts don't have a password to reset.
Multifactor authentication behaviorFor tenant MFA configuration and first-factor restrictions, see the MFA guidance. For SDK integrations, confirm that the SDK supports the steps to enroll and activate an MFA method.
Branding and language scopeThese rows describe Microsoft-hosted customization settings, not whether an application or website can implement its own design.
Custom authentication extension applicabilityThe following comparison describes event availability, not interchangeable request or response payloads. Use the event's documented contract and the current operation's returned data.
Integration, policy, and sessions by approachSession reuse, persistent sessions, and coordinated sign-out are different capabilities. See Single sign-on and Conditional Access for tenant configuration.
For platform guidance, see Supported languages and frameworks. For package versions and continuation interfaces, see SDK compatibility. Native SDKs don't orchestrate the BYO UX handoff-to-finish transaction. For architecture and integration guidance, see the Bring Your Own UX overview. General feature comparisonThe remaining tables compare tenant-level capabilities in workforce and external tenants. An external-tenant capability doesn't establish that every authentication approach or SDK supports it; use the approach comparison for those differences. The following table compares the general features and capabilities in workforce and external tenants. | Feature | Workforce tenant | External tenant | Interface customizationThe following table compares the features for interface customization in workforce and external tenants. Company branding and language customization apply to Microsoft-hosted pages. For Embedded native authentication and BYO UX, your team styles and localizes the interface it manages.
|
| 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. |
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. |
OnOtpSend (email) |
Not available. | Configure a custom email provider for one-time passcode send events. Learn more. |
OnTokenIssuanceStart | Add claims from external systems. | Add claims from external systems. |
Identity providers and authentication methods
The following table compares the identity providers and methods for primary authentication and multifactor authentication (MFA)MFA in workforce and external tenants. Federation options include Security Assertion Markup Language (SAML), WS-Federation (WS-Fed), and OpenID Connect (OIDC).
| Feature | Workforce tenant | External tenant |
|---|---|---|
| Identity providers for external users (primary authentication) | For self-service sign-up guests:
|
For self-service sign-up users (consumers, business customers):For invited guests
|
| Authentication methods for MFA | For internal users (employees and admins):For guests (invited or self-service sign-up): | For self-service sign-up users (consumers, business customers):For invited |
Authentication methods available in External ID
You can use some authentication methods as the primary factor when users sign in to an application, such as username and password. Other authentication methods are available only as a secondary factor. The following table outlines when you can use an authentication method during sign-in, self-service sign-up, self-service password reset, and MFA in External ID.
This table lists tenant-level method availability. Confirm method and journey availability for your approach in the approach-specific guidance.
| Method | Sign-in | Sign-up | Password reset | MFA |
|---|---|---|---|---|
| Email with password | ||||
| Email one-time passcode | ||||
| SMS-based authentication | Yes :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | |||
| Time-based one-time password (TOTP) | ||||
| Passkey (FIDO2) | ||||
| Apple federation | ||||
| Facebook federation | ||||
| Google federation | ||||
| Microsoft personal account (OpenID Connect) | ||||
| Microsoft Entra ID federation | ||||
| OpenID Connect federation | ||||
| SAML/WS-Fed federation |
Application registration
| Feature | Workforce tenant | External tenant |
|---|---|---|
| Protocol | Protocols include SAML relying parties, OpenID Connect, and OAuth2. | Protocols include SAML relying parties, |
| Supported account types | The following account types are available:
|
Always use accounts in this organizational directory only (single tenant). |
| Platform | The following platforms are available:
|
The following platforms are available:
|
| Redirect URIs for authentication | Microsoft Entra ID accepts these URIs as destinations when it returns authentication responses (tokens) after successfully authenticating or signing out users. | |
| Front-channel logout URL for authentication | This URL is where Microsoft Entra ID sends a request to have the application clear the user's session data. The front-channel logout URL is required for single sign-out to work correctly. | |
| Implicit grant and hybrid flows for authentication | Request a token directly from the authorization endpoint. | |
| Certificates and secrets | Multiple credentials are available: | |
| 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. | |
| Policy for certificates and secrets | Configure the application management policies to enforce secret and certificate restrictions. | Not available. |
| 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. | |
| 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. | |
| Roles and administrators | Administrative roles are used for granting access for privileged actions in Microsoft Entra ID. |
Access control for applications
| Feature | Workforce tenant | External tenant |
|---|---|---|
| Role-based access control (RBAC) | You can define application roles for your application and assign those roles to users and groups. Microsoft Entra ID includes the user roles in the security token. Your application can then make authorization decisions based on the values in the security token. | |
| Security groups | You can use security groups to implement RBAC in your applications, where the memberships of users in specific groups are interpreted as their role memberships. Microsoft Entra ID includes user group membership in the security token. Your application can then make authorization decisions based on the values in the security token. | |
| Attribute-based access control (ABAC) | You can configure the app to include user attributes in the access token. Your application can then make authorization decisions based on the values in the security token. For more information, see Token customization. | |
| Require user assignment | When user assignment is required, only the users you assign to the application (either through direct user assignment or based on group membership) can sign in. For more information, see Manage user and group assignments to an application. |
Enterprise applications
| 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. |
| Deactivate app registration | Deactivate an app registration to prevent token issuance while preserving configuration. | Same as workforce.Supported. |
Consent and permission features for enterprise applications
| Feature | Workforce tenant | External tenant |
|---|---|---|
| Admin consent for enterprise applications | You can grant tenant-wide admin permissions. You can also review and revoke them. | |
| User consent for enterprise applications | You can configure how users consent to applications, and you can update these permissions. | Limited to permissions that don't require admin consent. |
| Review or revoke admin consent | Review and revoke permissions. | Use the Microsoft Entra admin center to revoke admin consent. |
| Review or revoke user consent | Review and revoke permissions. | Use Microsoft Graph API or PowerShell to revoke user consent. |
| Assign users or groups to apps | You can manage access to apps in an individual or group-based assignment. Nested group memberships aren't supported. | |
| RBAC for app roles | You can define and assign roles for fine-grained access control. |
OpenID Connect and OAuth2 flows
The following table compares the features fortenant-level OAuth 2.0 and OpenID Connect authorization flows in each type of tenant.capabilities. It doesn't define the supported request parameters for the Native Authentication API or the BYO UX handoff.
| Feature | Workforce tenant | External tenant |
|---|---|---|
| Device authorization | Yes | Yes |
| On-behalf-of flow | Yes | Yes |
| Implicit grant | Yes | Yes |
| Resource owner password credentials | Yes | No; for mobile applications, use |
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 appsMicrosoft-hosted authentication in external tenants, always use the following format: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. Include the tenant GUID in the URL path.
The following JSON shows ana Microsoft-hosted authentication example ofin a .NET application's appsettings.json file with an authority URL:file:
{
| Target resources | <ul><li>[Cloud apps](~/identity/conditional-access/concept-conditional-access-cloud-apps.md)</li><li>[User actions](~/identity/conditional-access/concept-conditional-access-cloud-apps.md#user-actions)</li><li>[Global Secure Access](~/identity/conditional-access/concept-conditional-access-cloud-apps.md#traffic-forwarding-profiles)</li><li>[Authentication context](~/identity/conditional-access/concept-conditional-access-cloud-apps.md#authentication-context)</li></ul> | <ul><li>[All resources, selected apps](./how-to-multifactor-authentication-customers.md), or [filter applications](~/identity/conditional-access/concept-filter-for-applications.md)</li><li>[Authentication context](~/identity/conditional-access/concept-conditional-access-cloud-apps.md#authentication-context)</li></ul> |
| Conditions | <ul><li>[Sign-in risk](~/identity/conditional-access/concept-conditional-access-conditions.md#sign-in-risk)</li><li>[User risk](~/identity/conditional-access/concept-conditional-access-conditions.md#user-risk)</li><li>[Device platforms](~/identity/conditional-access/concept-conditional-access-conditions.md#device-platforms)</li><li>[Locations](~/identity/conditional-access/concept-conditional-access-conditions.md#locations)</li><li>[Client apps](~/identity/conditional-access/concept-conditional-access-conditions.md#client-apps)</li><li>[Filter for devices](~/identity/conditional-access/concept-conditional-access-conditions.md#filter-for-devices)</li></ul> | <ul><li>[Device platforms](~/identity/conditional-access/concept-conditional-access-conditions.md#device-platforms)</li><li>[Locations](~/identity/conditional-access/concept-conditional-access-conditions.md#locations)</li></ul> |
| Grant | [Grant or block access to resources](~/identity/conditional-access/concept-conditional-access-grant.md) | <ul><li>[Block access](~/identity/conditional-access/concept-conditional-access-grant.md#block-access)</li><li>[Require multifactor authentication](./how-to-multifactor-authentication-customers.md)</li><li>[Require password reset](./how-to-enable-password-reset-customers.md)</li></ul> |
| Session | [Session controls](~/identity/conditional-access/concept-conditional-access-session.md) | The following session controls are available: <ul><li>[Sign-in frequency (SIF)](../../identity/conditional-access/concept-session-lifetime.md#user-sign-in-frequency) for Microsoft-hosted authentication and supported Embedded native authentication integrations. Availability can differ by approach and API or SDK version.</li><li>Persistent browser session for browser-based sessions.</li></ul> |
## Terms-of-use policies
| ------- | ---------------- | --------------- |
| 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. |
| 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). | [Same as workforce][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
| Feature | Workforce tenant | External tenant |
| ------- | ---------------- | --------------- |
| Types of accounts | <ul><li>Internal members, such as employees and admins.</li><li>External users who are [invited](../what-is-b2b.md) or use self-service sign-up.</li></ul> | <ul><li> External users created through self-service sign-up or [by an admin](how-to-manage-customer-accounts.md).</li><li> Internal users, with or without an admin role. </li><li> Invited users (preview),users, 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). |
| Manage user profile info | <ul><li>Manage users programmatically and by [using the admin center](~/fundamentals/how-to-manage-user-profile-info.md).</li><li>Manage guest users across tenants with [cross-tenant synchronization](/entra/identity/multi-tenant-organizations/cross-tenant-synchronization-overview).</li></ul> | Same as workforce, except cross-Manage users in the admin center or programmatically. Cross-tenant synchronization isn't available. |
| Reset a user's password | Administrators can [reset a user's password](~/fundamentals/users-reset-password-azure-portal.md) if the user forgets the password, is locked out of a device, or never received a password. | Same as workforce.Supported. |
| Restore or remove a recently deleted user | After you delete a user, the account remains in a suspended state for 30 days. During that 30-day window, the user account can be restored, along with all its properties. | Same as workforce.Supported. Restore users and their properties within 30 days. |
| Disable accounts | Prevent the new user from signing in. | Same as workforce.Supported. |
## Password protection
| Feature | Workforce tenant | External tenant |
| ------- | ---------------- | --------------- |
| Smart lockout | [Smart lockout](~/identity/authentication/howto-password-smart-lockout.md) helps lock out bad actors who try to guess your users' passwords or use brute-force methods to get in. | Same as workforce.Supported. |
| Global banned passwords | The [global banned passwords list](~/identity/authentication/concept-password-ban-bad.md#global-banned-password-list) automatically blocks commonly used weak or compromised passwords based on analysis of Microsoft Entra security data. | Same as workforce.Supported. |
| Custom banned passwords | Use the [custom banned passwords list](../../identity/authentication/tutorial-configure-custom-password-protection.md) to add specific strings to evaluate and block during password creation and reset. | Same as workforce.Supported. |
## Token customization
| Feature | Workforce tenant | External tenant |
| ------- | ---------------- | --------------- |
| Claims mapping | [Customize claims](~/identity-platform/jwt-claims-customization.md) issued in the JSON web token (JWT) for enterprise applications. | Same as workforce. OptionalSupported. Configure optional claims must be configured through [Attributes & Claims](how-to-add-attributes-to-token.md). |
| Claims transformation | [Apply a transformation to a user attribute](~/identity-platform/jwt-claims-customization.md) issued in the JWT for enterprise applications. | Same as workforce.Supported. |
| Custom claims provider | Use a [custom authentication extension](~/identity-platform/custom-extension-overview.md) that calls an external REST API to fetch claims from external systems. | Same as workforce. [Learn more]Supported. [Custom claims provider](../../identity-platform/custom-claims-provider-overview.md). |
| Security groups | [Configure group optional claims](../../identity-platform/optional-claims.md#configure-groups-optional-claims). | [Configure group optional claims](../../identity-platform/optional-claims.md#configure-groups-optional-claims), limited to the group object ID. |
| Token lifetimes | [Specify the lifetime](../../identity-platform/configurable-token-lifetimes.md) of security tokens issued by Microsoft Entra ID. | Same as workforce.Supported. |
| Session and token revocation | An administrator can [invalidate all the refresh tokens and session](/graph/api/user-revokesigninsessions) for a user. | Same as workforce.Supported. |
## Single sign-on
[Single sign-on (SSO)](../../identity-platform/msal-js-sso.md) provides a more seamless experience by reducing the number of times a user is asked for credentials. Users enter their credentials once. Other applications can reuse the established session on the same device and web browser without further prompting.
The following table compares the features forbrowser-based SSO in each type of tenant. For Embedded native authentication and BYO UX session boundaries, see [Integration, policy, and sessions by approach](#integration-policy-and-sessions-by-approach).
| Feature | Workforce tenant | External tenant |
| ------- | ---------------- | --------------- |
| Types of application registration | <ul><li>OpenID Connect</li> <li>OAuth 2.0</li> <li>SAML (enterprise application)</li></ul><br>Enterprise applications offer [more options](../../identity/enterprise-apps/plan-sso-deployment.md), like password-based, linked, and header-based registration. | <ul><li>OpenID Connect</li> <li>OAuth 2.0</li> <li>SAML (enterprise application)</li></ul> |
| Domain name | When a user is authenticated, a session cookie is set on the Microsoft Entra domain `login.microsoftonline.com` in the web browser. | When a user is authenticated, a session cookie is set on the Microsoft Entra External ID domain `<tenant-name>.ciamlogin.com` or a [custom URL domain](concept-custom-url-domain.md) in the web browser. To ensure that SSO functions correctly, use a single URL domain. |
| Stay signed in | You can turn on or turn off the option to [stay signed in](~/fundamentals/how-to-manage-stay-signed-in-prompt.yml). | The **Stay signed in?** prompt appears by default. To change or suppress it, use the **Persistent browser session** session control in a Conditional Access policy. [Learn more](how-to-user-flow-sign-up-sign-in-customers.md#control-the-stay-signed-in-prompt). |
| User provisioning | Use [automatic user provisioning](/entra/architecture/sync-scim) with System for Cross-domain Identity Management (SCIM) to sync user accounts between External ID and supported apps. This approach keeps user data up to date automatically.<br><br> User provisioning supports differential queries. These queries sync only the changes since the last update. This behavior improves performance and reduces system load. | Same as workforce.Supported, including differential queries. |
| Session invalidation | Scenarios where SSO might be invalidated, which requires reauthentication: <ul><li>Session expiry</li><li>Browser issues, such as clearing browser cookies or cache</li><li>Conditional Access policy, such as a multifactor authentication requirement</li><li>[Session revocation](/graph/api/user-revokesigninsessions)</li><li>Security issues, such as suspicious activity</li></ul><br>The application specifies in the authorization request to prompt the user for credentials by using the `login=prompt``prompt=login` query string parameter in OpenID Connect and the `ForceAuthn` attribute in the SAML request. | Same as workforce.Session expiration, browser state, Conditional Access, revocation, and security events can require reauthentication. Apps can also request reauthentication. |
| Conditional Access | Check the [Conditional Access](#conditional-access) section. | Check the [Conditional Access](#conditional-access) section. |
| Microsoft Entra native authentication | Not available. | [Native authentication](concept-native-authentication.md) supports SSO for embedded web views. Cross-app SSO through system browsers isn't available with native authentication. |
| Sign-out | When a [SAML](../../identity-platform/single-sign-out-saml-protocol.md) or [OpenID Connect](../../identity-platform/v2-protocols-oidc.md#send-a-sign-out-request) application directs the user to the logout endpoint, Microsoft Entra ID removes and invalidates the user's session from the browser. | Same as workforce.Supported for SAML and OpenID Connect apps. |
| Single sign-out | Upon successful sign-out, Microsoft Entra ID sends a sign-out notification to all other [SAML](../../identity-platform/single-sign-out-saml-protocol.md) and [OpenID Connect](../../identity-platform/v2-protocols-oidc.md#single-sign-out) applications that the user is signed in to. | Same as workforce.Supported for SAML and OpenID Connect apps. |
Review your approach's session requirements for browser-session reuse and single sign-out.
## Integrated security solutions
The following table compares the features for activity logs and reports across various types of tenants.
|
| Feature | Workforce tenant | External tenant |
|---|---|---|
| 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. | 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. |
| 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 | 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. |
Microsoft Graph APIs
Use Microsoft Graph APIs All features that areto automate supported in external tenants are also supported for automation throughtenant administration operations. Check each operation's permissions and requirements; tenant administration support doesn't establish direct Microsoft Graph APIs. Some features that are in preview in external tenants might be generally available through Microsoft Graph.access from a BYO UX page or interoperability with native-issued tokens. For more information, see [Manage Microsoft Entra identity and network access by using Microsoft Graph](/graph/api/resources/identity-network-access-overview)Manage Microsoft Entra identity and network access by using Microsoft Graph.
##
Related content
- [Planning for customer identity and access management](concept-planning-your-solution.md)
- Planning for customer identity and access management.
- For existing integrations, see the Native Authentication API V1 reference. This version remains supported, but its capabilities differ from the current API.
@@ -1,27 +1,130 @@ ----title: External Tenant Features-description: Compare features and capabilities of a workforce versus an external tenant configuration. Determine which tenant type applies to your external identities scenario.+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: 09/02/2026-ms.custom: it-pro, seo-july-2024, sfi-ropc-nochange+ms.date: 11/12/2026+ms.custom: it-pro, seo-july-2024, sfi-ropc-nochange, msecd-doc-authoring-1030 ai-usage: ai-assisted-#Customer intent: As a dev, DevOps, or IT admin, I want to learn about features supported in a CIAM tenant so that I can configure tenants according to my organization's needs.+#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. --- -# Supported features in workforce and external tenants+# Supported features in Microsoft Entra External ID workforce and external tenants -There are two ways to configure a Microsoft Entra tenant, depending on how an organization intends to use the tenant and the resources that you want to manage:+Microsoft Entra External ID supports two tenant configurations, depending on your audience and the resources you want to manage: -- A *workforce* tenant configuration is for your employees, internal business apps, and other organizational resources. A workforce tenant uses B2B collaboration in Microsoft Entra External ID for collaboration with external business partners and guests.+- A *workforce* tenant configuration is for your employees, internal business apps, and other organizational resources. A workforce tenant uses business-to-business (B2B) collaboration in Microsoft Entra External ID to work with external business partners and guests. - An *external* tenant configuration is exclusively for External ID scenarios where you want to publish apps to consumers or business customers. -This article gives a detailed comparison of the features and capabilities in workforce and external tenants. For more information about these tenants, see [Workforce and external tenant configurations in Microsoft Entra External ID](../tenant-configurations.md).+This article provides two comparisons: -> [!NOTE]-> During the preview, features or capabilities that require a premium license are unavailable in external tenants.+- To choose how customer apps present authentication, review [authentication approach support](#authentication-approach-supportability) in external tenants.+- To compare workforce and external tenant capabilities, start with the [general feature comparison](#general-feature-comparison).++For more information about these tenants, see [Workforce and external tenant configurations in Microsoft Entra External ID](../tenant-configurations.md).++> [!IMPORTANT]+> The Embedded native authentication and Bring Your Own UX (BYO UX) comparisons describe the current Native Authentication API (V2, preview). BYO UX is also in preview. SDK support varies by platform and version. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to preview features.++<a name="authentication-approach-supportability"></a>++## Authentication approach support++Compare [methods and journeys](#methods-and-journeys-by-approach) and [integration, policy, and sessions](#integration-policy-and-sessions-by-approach) for customer-app authentication in **external tenants**. For architectural choices, see [Choose an authentication approach](concept-choose-authentication-approach.md). Company branding and branding themes are presentation options within Microsoft-hosted authentication, not separate authentication approaches.++For SDK integrations, use a release compatible with the current API that supports the operations your app requires. See the [Native authentication overview](../../identity-platform/concept-native-authentication.md) and [platform-specific SDK guidance](~/identity-platform/concept-native-authentication.md#how-to-use-native-authentication). SDK support varies by platform and version.++For API operations, see the [Native Authentication API reference](~/identity-platform/reference-native-authentication.md).++**How to read the comparison:** "Supported" applies to the approach and API version described here, not to every SDK. Configure required tenant methods and policies before using a supported operation.++### Methods and journeys by approach++The following table compares local-account methods and federation. For provider configuration, see [Identity providers for external tenants](concept-authentication-methods-customers.md). Password recovery and multifactor authentication (MFA) have separate comparisons.++> [!IMPORTANT]+> Username or alias sign-in is in preview. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to preview features.++| Journey or method | Microsoft-hosted authentication | Embedded native authentication | Bring Your Own UX |+| --- | --- | --- | --- |+| **Sign-up: email and password** | Supported. | Supported. | Supported. |+| **Sign-up: email one-time passcode** | Supported. | Supported. | Supported. |+| **Sign-in: email and password** | Supported. | Supported. | Supported. |+| **Sign-in: username and password** | Supported for configured local accounts. | Supported for configured local accounts. | Supported for configured local accounts. |+| **Sign-in: email one-time passcode** | Supported. | Supported. | Supported. |+| **Phone number as first factor** | Not supported. | Not supported. | Not supported. |+| **Social or federated identity providers** | Supported through configured identity providers. | Not supported. | Not supported. |++Use only methods and operations returned for the active transaction. A tenant can contain providers or methods that aren't available through the selected integration.++### Password reset behavior and controls++Password recovery support doesn't imply support for Microsoft-hosted reset-page settings. Passwordless email one-time-passcode accounts don't have a password to reset.++| Capability | Microsoft-hosted authentication | Embedded native authentication | Bring Your Own UX |+| --- | --- | --- | --- |+| **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. |++### Multifactor authentication behavior++For [tenant MFA configuration](concept-multifactor-authentication-customers.md) and [first-factor restrictions](concept-multifactor-authentication-customers.md#enabling-mfa-methods), see the MFA guidance. For SDK integrations, confirm that the SDK supports the steps to enroll and activate an MFA method.++| Capability | Microsoft-hosted authentication | Embedded native authentication | Bring Your Own UX |+| --- | --- | --- | --- |+| **Email or SMS one-time passcode (OTP)** | Supported, subject to first-factor restrictions in [MFA methods](concept-multifactor-authentication-customers.md#enabling-mfa-methods). | Supported. Accounts that use email OTP as the first factor use a different second factor, such as SMS. | Supported. Accounts that use email OTP as the first factor use a different second factor, such as SMS. |+| **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. |++### Branding and language scope++These rows describe Microsoft-hosted customization settings, not whether an application or website can implement its own design.++| Capability | Microsoft-hosted authentication | Embedded native authentication | Bring Your Own UX |+| --- | --- | --- | --- |+| **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. |++<a name="custom-authentication-extension-events-by-approach"></a>++### Custom authentication extension applicability++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.++| 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. |++### Integration, policy, and sessions by approach++Session reuse, persistent sessions, and coordinated sign-out are different capabilities. See [Single sign-on](#single-sign-on) and [Conditional Access](#conditional-access) for tenant configuration.++| Capability | Microsoft-hosted authentication | Embedded native authentication | Bring Your Own UX |+| --- | --- | --- | --- |+| **Application model** | Browser-based integration, including single-page applications (SPAs). | Public clients, including SPAs; browser integrations require a cross-origin resource sharing (CORS) proxy or edge origin policy. | Public or confidential relying applications with a registered web-type redirect URI. |+| **MFA policy enforcement** | Supported through Conditional Access. | Supported through Conditional Access and orchestrated by the native app. | Supported through Conditional Access and orchestrated by the custom authentication page. |+| **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. |+| **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. |++For platform guidance, see [Supported languages and frameworks](concept-choose-authentication-approach.md#supported-languages-and-frameworks). For package versions and continuation interfaces, see [SDK compatibility](~/identity-platform/how-to-migrate-native-authentication-v1-v2.md#sdk-compatibility). Native SDKs don't orchestrate the BYO UX handoff-to-finish transaction.++For architecture and integration guidance, see the [Bring Your Own UX overview](concept-bring-your-own-ux.md). ## General feature comparison +The remaining tables compare **tenant-level capabilities** in workforce and external tenants. An external-tenant capability doesn't establish that every authentication approach or SDK supports it; use the [approach comparison](#authentication-approach-supportability) for those differences.+ The following table compares the general features and capabilities in workforce and external tenants. | Feature | Workforce tenant | External tenant |@@ -39,55 +142,62 @@ The following table compares the general features and capabilities in workforce ## Interface customization -The following table compares the features for interface customization in workforce and external tenants.+The following table compares the features for interface customization in workforce and external tenants. Company branding and language customization apply to Microsoft-hosted pages. For Embedded native authentication and BYO UX, your team styles and localizes the interface it manages. | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- |-| 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. | Same as workforce. [Learn more](how-to-customize-branding-customers.md). |-| Language customization | [Customize the sign-in experience by browser language](~/fundamentals/how-to-customize-branding.md). | Same as workforce. [Learn more](how-to-customize-languages-customers.md). |-| Custom domain names | You can use [custom domains](~/fundamentals/add-custom-domain.md) for administrative accounts only. | You can use the [custom URL domain](concept-custom-url-domain.md) feature for external tenants to brand app sign-in endpoints with your own domain name. |-| Native authentication for mobile apps | Not available. | Microsoft Entra [native authentication](concept-native-authentication.md) gives you full control over the design of your mobile application's sign-in experiences. |+| 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). |++<a name="adding-your-own-business-logic"></a> -## Adding your own business logic+## Add your own business logic -You can use [custom authentication extensions](./concept-custom-extensions.md) to customize the Microsoft Entra authentication experience by integrating with external systems. A custom authentication extension is essentially an event listener. When you activate it, it makes an HTTP call to a REST API endpoint where you define your own business logic.+Use [custom authentication extensions](./concept-custom-extensions.md) to integrate external systems with the Microsoft Entra authentication experience. A custom authentication extension listens for an event and makes an HTTP call to a REST API endpoint where you define your business logic. -The following table compares the events for custom authentication extensions in workforce and external tenants.+The following table compares the events for custom authentication extensions in workforce and external tenants. For support by authentication approach, see the [custom authentication extension comparison](#custom-authentication-extension-applicability). | Event | Workforce tenant | External tenant | | ----- | ---------------- | --------------- |-| `TokenIssuanceStart` | [Add claims from external systems](~/identity-platform/custom-extension-overview.md). | [Add claims from external systems](./concept-custom-extensions.md). | -| `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` | 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 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). |+| **`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 -The following table compares the [identity providers](../identity-providers.md) and methods for primary authentication and multifactor authentication (MFA) in workforce and external tenants.+The following table compares the [identity providers](../identity-providers.md) and methods for primary authentication and MFA in workforce and external tenants. Federation options include Security Assertion Markup Language (SAML), WS-Federation (WS-Fed), and OpenID Connect (OIDC).++> [!IMPORTANT]+> Invitations in external tenants are in preview. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to preview features. | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- |-| Identity providers for external users (primary authentication) | For self-service sign-up guests:<ul><li>Microsoft Entra accounts</li><li>Microsoft accounts</li><li>Emailed one-time passcode</li><li>Google federation</li><li>Facebook federation</li></ul></br>For invited guests:<ul><li>Microsoft Entra accounts</li><li>Microsoft accounts</li><li>Emailed one-time passcode</li><li>Google federation</li><li>SAML/WS-Fed federation</li></ul> | For self-service sign-up users (consumers, business customers):<ul><li>[Authentication methods available in External ID](#authentication-methods-available-in-external-id)</li></ul></br>For invited guests (preview) via a directory role (for example, admins):<ul><li>Microsoft Entra accounts</li><li>Microsoft accounts</li><li>[Emailed one-time passcode](./concept-authentication-methods-customers.md#email-with-one-time-passcode-sign-in)</li><li>[SAML/WS-Fed federation](../direct-federation.md)</li></ul></br> You can invite external users for administrative purposes only. You can't use this feature to invite customers to sign in to your apps. This feature isn't compatible with customer identity and access management (CIAM) user flows. |-| Authentication methods for MFA | For internal users (employees and admins):<ul><li>[Authentication and verification methods](~/identity/authentication/overview-authentication.md)</li></ul></br>For guests (invited or self-service sign-up):<ul><li>[Authentication methods for guest MFA](../authentication-conditional-access.md#table-1-authentication-strength-mfa-methods-for-external-users)</li></ul> | For self-service sign-up users (consumers, business customers):<ul><li>[Emailed one-time passcode](concept-multifactor-authentication-customers.md#email-one-time-passcode)</li><li>[SMS-based authentication](concept-multifactor-authentication-customers.md#sms-based-authentication)</li><li>[Time-based one-time password (TOTP)](concept-multifactor-authentication-customers.md#time-based-one-time-password-totp)</li><li>[Passkey (FIDO2)](how-to-sign-in-with-passkey.md)</li></ul></br>For invited users (preview):<ul><li>[Emailed one-time passcode](concept-multifactor-authentication-customers.md#email-one-time-passcode)</li><li>[SMS-based authentication](concept-multifactor-authentication-customers.md#sms-based-authentication)</li></ul> |+| Identity providers for external users (primary authentication) | For self-service sign-up guests:<ul><li>Microsoft Entra accounts</li><li>Microsoft accounts</li><li>Emailed one-time passcode</li><li>Google federation</li><li>Facebook federation</li></ul></br>For invited guests:<ul><li>Microsoft Entra accounts</li><li>Microsoft accounts</li><li>Emailed one-time passcode</li><li>Google federation</li><li>SAML/WS-Fed federation</li></ul> | For self-service sign-up users (consumers, business customers):<ul><li>[Authentication methods available in External ID](#authentication-methods-available-in-external-id)</li></ul></br>For invited guests via a directory role (for example, admins):<ul><li>Microsoft Entra accounts</li><li>Microsoft accounts</li><li>[Emailed one-time passcode](./concept-authentication-methods-customers.md#email-with-one-time-passcode-sign-in)</li><li>[SAML/WS-Fed federation](../direct-federation.md)</li></ul></br> You can invite external users for administrative purposes only. You can't use this feature to invite customers to sign in to your apps. This feature isn't compatible with customer identity and access management (CIAM) user flows. |+| Authentication methods for MFA | For internal users (employees and admins):<ul><li>[Authentication and verification methods](~/identity/authentication/overview-authentication.md)</li></ul></br>For guests (invited or self-service sign-up):<ul><li>[Authentication methods for guest MFA](../authentication-conditional-access.md#table-1-authentication-strength-mfa-methods-for-external-users)</li></ul> | For self-service sign-up users (consumers, business customers):<ul><li>[Emailed one-time passcode](concept-multifactor-authentication-customers.md#email-one-time-passcode)</li><li>[SMS-based authentication](concept-multifactor-authentication-customers.md#sms-based-authentication)</li><li>[Time-based one-time password (TOTP)](concept-multifactor-authentication-customers.md#time-based-one-time-password-totp)</li><li>[Passkey (FIDO2)](how-to-sign-in-with-passkey.md)</li></ul></br>For invited users:<ul><li>[Emailed one-time passcode](concept-multifactor-authentication-customers.md#email-one-time-passcode)</li><li>[SMS-based authentication](concept-multifactor-authentication-customers.md#sms-based-authentication)</li></ul> | ### Authentication methods available in External ID -You can use some authentication methods as the primary factor when users sign in to an application, such username and password. Other authentication methods are available only as a secondary factor. The following table outlines when you can use an authentication method during sign-in, self-service sign-up, self-service password reset, and MFA in External ID.--|Method |Sign-in |Sign-up |Password reset |MFA |-|---------|---------|---------|---------|---------|-| [Email with password](./concept-authentication-methods-customers.md#email-and-password-sign-in) | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | :::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)| :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: |:::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: |-| [SMS-based authentication](./concept-multifactor-authentication-customers.md#sms-based-authentication)| | | | :::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)| | | | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: |-| [Passkey (FIDO2)](./how-to-sign-in-with-passkey.md) | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: |-| [Apple federation](./how-to-apple-federation-customers.md)| :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: |:::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| [Facebook federation](./how-to-facebook-federation-customers.md)| :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| [Google federation](./how-to-google-federation-customers.md) | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| Microsoft personal account ([OpenID Connect](./how-to-custom-oidc-federation-customers.md)) | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| [Microsoft Entra ID federation](./how-to-entra-id-federation-customers.md)| :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| [OpenID Connect federation](./how-to-custom-oidc-federation-customers.md)| :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |-| [SAML/WS-Fed federation](../direct-federation.md)| :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | :::image type="icon" source="../media/common/applies-to-yes.png" border="false"::: | | |+You can use some authentication methods as the primary factor when users sign in to an application, such as username and password. Other authentication methods are available only as a secondary factor. The following table outlines when you can use an authentication method during sign-in, self-service sign-up, self-service password reset, and MFA in External ID.++This table lists tenant-level method availability. Confirm method and journey availability for your approach in the [approach-specific guidance](#authentication-approach-supportability).++| 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"::: | | | ## Application registration @@ -95,19 +205,19 @@ The following table compares the features for [application registration](../../i | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- |-| Protocol | Protocols include SAML relying parties, OpenID Connect, and OAuth2. | Protocols include [SAML relying parties](how-to-register-saml-app.md), [OpenID Connect](how-to-register-ciam-app.md), and OAuth2. |+| Protocol | Protocols include SAML relying parties, OpenID Connect, and OAuth2. | Protocols include [SAML relying parties](how-to-register-saml-app.md), [OpenID Connect](../../identity-platform/quickstart-register-app.md), and OAuth2. | | Supported account types | The following [account types](~/identity-platform/quickstart-register-app.md#register-an-application) are available: <ul><li>Accounts in this organizational directory only (single tenant)</li><li>Accounts in any organizational directory (any Microsoft Entra tenant in a multitenant configuration)</li><li>Accounts in any organizational directory (any Microsoft Entra tenant in a multitenant configuration) and personal Microsoft accounts (such as Skype and Xbox)</li><li>Personal Microsoft accounts only</li></ul> | Always use accounts in this organizational directory only (single tenant). |-| Platform | The following [platforms](../../identity-platform/how-to-add-redirect-uri.md) are available: <ul><li>Public client/native (mobile and desktop)</li><li>Web</li><li>Single-page application (SPA)</li></ul> | The following [platforms](../../identity-platform/how-to-add-redirect-uri.md) are available: <ul><li>Public client (mobile and desktop)</li><li>Web</li><li>SPA</li><li>Native authentication for [mobile](concept-native-authentication.md) and [single-page](how-to-native-authentication-cors-solution-production-environment.md) applications </li></ul> |-| Redirect URIs for authentication | Microsoft Entra ID accepts these URIs as destinations when it returns authentication responses (tokens) after successfully authenticating or signing out users. | Same as workforce. |-| Front-channel logout URL for authentication | This URL is where Microsoft Entra ID sends a request to have the application clear the user's session data. The front-channel logout URL is required for single sign-out to work correctly. | Same as workforce. |-| Implicit grant and hybrid flows for authentication | Request a token directly from the authorization endpoint. | Same as workforce. |-| 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> | Same as workforce. |-| 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. | Same as workforce. |+| Platform | The following [platforms](../../identity-platform/how-to-add-redirect-uri.md) are available: <ul><li>Public client/native (mobile and desktop)</li><li>Web</li><li>Single-page application (SPA)</li></ul> | The following [platforms](../../identity-platform/how-to-add-redirect-uri.md) are available: <ul><li>Public client (mobile and desktop)</li><li>Web</li><li>SPA</li><li>Embedded native authentication for [mobile](../../identity-platform/concept-native-authentication.md) and [single-page](~/identity-platform/concept-native-authentication-cors.md#proxy-contract) applications </li></ul> |+| Redirect URIs for authentication | Microsoft Entra ID accepts these URIs as destinations when it returns authentication responses (tokens) after successfully authenticating or signing out users. | Supported. |+| Front-channel logout URL for authentication | This URL is where Microsoft Entra ID sends a request to have the application clear the user's session data. The front-channel logout URL is required for single sign-out to work correctly. | Supported; required for single sign-out. |+| 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. | | 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. | Same as workforce. |-| 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. | Same as workforce. |-| Roles and administrators | [Administrative roles](~/identity/role-based-access-control/permissions-reference.md) are used for granting access for privileged actions in Microsoft Entra ID. | Only the [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator) role can be used for apps in external tenants. This role grants the ability to create and manage all aspects of application registrations and enterprise applications. |+| 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. |+| Roles and administrators | [Administrative roles](~/identity/role-based-access-control/permissions-reference.md) are used for granting access for privileged actions in Microsoft Entra ID. | [Cloud Application Administrators](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator) can create and manage application registrations and enterprise applications in external tenants. Other roles support application management according to their permissions. For users who need to manage only app registrations they own, Application Developer is the least-privileged built-in role. | ### Access control for applications @@ -115,10 +225,10 @@ The following table compares the features for application authorization in each | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- |-| Role-based access control (RBAC) | You can define [application roles](../../identity-platform/custom-rbac-for-developers.md#app-roles) for your application and assign those roles to users and groups. Microsoft Entra ID includes the user roles in the security token. Your application can then make authorization decisions based on the values in the security token. | Same as workforce. [Learn more about using role-based access control for applications in an external tenant](how-to-use-app-roles-customers.md). For available features, see [Groups and application roles support](./reference-group-app-roles-support.md). |-| Security groups | You can use [security groups](../../identity-platform/custom-rbac-for-developers.md#groups) to implement RBAC in your applications, where the memberships of users in specific groups are interpreted as their role memberships. Microsoft Entra ID includes user group membership in the security token. Your application can then make authorization decisions based on the values in the security token. | Same as workforce. The [group optional claims](../../identity-platform/optional-claims.md#configure-groups-optional-claims) are limited to the group object ID. |-| Attribute-based access control (ABAC) | You can configure the app to include user attributes in the access token. Your application can then make authorization decisions based on the values in the security token. For more information, see [Token customization](#token-customization). | Same as workforce. |-| Require user assignment | When user assignment is required, only the users you assign to the application (either through direct user assignment or based on group membership) can sign in. For more information, see [Manage user and group assignments to an application](../../identity-platform/howto-restrict-your-app-to-a-set-of-users.md). | Same as workforce. For details, see [Groups and application roles support](./reference-group-app-roles-support.md). |+| Role-based access control (RBAC) | You can define [application roles](../../identity-platform/custom-rbac-for-developers.md#app-roles) for your application and assign those roles to users and groups. Microsoft Entra ID includes the user roles in the security token. Your application can then make authorization decisions based on the values in the security token. | Supported. [Use role-based access control for applications in an external tenant](how-to-use-app-roles-customers.md). For available features, see [Groups and application roles support](./reference-group-app-roles-support.md). |+| Security groups | You can use [security groups](../../identity-platform/custom-rbac-for-developers.md#groups) to implement RBAC in your applications, where the memberships of users in specific groups are interpreted as their role memberships. Microsoft Entra ID includes user group membership in the security token. Your application can then make authorization decisions based on the values in the security token. | Supported. The [group optional claims](../../identity-platform/optional-claims.md#configure-groups-optional-claims) are limited to the group object ID. |+| Attribute-based access control (ABAC) | You can configure the app to include user attributes in the access token. Your application can then make authorization decisions based on the values in the security token. For more information, see [Token customization](#token-customization). | Supported. |+| Require user assignment | When user assignment is required, only the users you assign to the application (either through direct user assignment or based on group membership) can sign in. For more information, see [Manage user and group assignments to an application](../../identity-platform/howto-restrict-your-app-to-a-set-of-users.md). | Supported. For details, see [Groups and application roles support](./reference-group-app-roles-support.md). | ## Enterprise applications @@ -130,7 +240,7 @@ The following table compares the unique features for [enterprise application](/e | 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. |-| Deactivate app registration | [Deactivate an app registration](/entra/identity/enterprise-apps/deactivate-app-registration) to prevent token issuance while preserving configuration. | Same as workforce. |+| 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 @@ -138,16 +248,16 @@ The following table shows which consent and permission features are available fo | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- |-| Admin consent for enterprise applications | You can [grant tenant-wide admin permissions](/entra/identity/enterprise-apps/grant-admin-consent). You can also [review and revoke](/entra/identity/enterprise-apps/manage-application-permissions?pivots=portal) them. | Same as workforce. |+| Admin consent for enterprise applications | You can [grant tenant-wide admin permissions](/entra/identity/enterprise-apps/grant-admin-consent). You can also [review and revoke](/entra/identity/enterprise-apps/manage-application-permissions?pivots=portal) them. | Supported. | | User consent for enterprise applications | You can configure how [users consent to applications](/entra/identity/enterprise-apps/configure-user-consent), and you can [update these permissions](/entra/identity-platform/howto-update-permissions). | Limited to permissions that don't require [admin consent](/entra/identity/enterprise-apps/grant-admin-consent). | | Review or revoke admin consent | [Review and revoke](/entra/identity/enterprise-apps/manage-application-permissions) permissions. | [Use the Microsoft Entra admin center](/entra/identity/enterprise-apps/manage-application-permissions?pivots=portal) to revoke admin consent. | | Review or revoke user consent | [Review and revoke](/entra/identity/enterprise-apps/manage-application-permissions) permissions. | Use [Microsoft Graph API](/entra/identity/enterprise-apps/manage-application-permissions?pivots=ms-graph) or [PowerShell](/entra/identity/enterprise-apps/manage-application-permissions?pivots=entra-powershell) to revoke user consent. |-| Assign users or groups to apps | You can [manage access to apps](/entra/identity/enterprise-apps/what-is-access-management) in an individual or group-based assignment. [Nested group](/entra/fundamentals/how-to-manage-groups) memberships aren't supported. | Same as workforce. |-| RBAC for app roles | You can define and assign roles for fine-grained [access control](/entra/external-id/customers/how-to-use-app-roles-customers). | Same as workforce. |+| Assign users or groups to apps | You can [manage access to apps](/entra/identity/enterprise-apps/what-is-access-management) in an individual or group-based assignment. [Nested group](/entra/fundamentals/how-to-manage-groups) memberships aren't supported. | Supported; nested groups aren't supported. |+| RBAC for app roles | You can define and assign roles for fine-grained [access control](/entra/external-id/customers/how-to-use-app-roles-customers). | Supported. | ## OpenID Connect and OAuth2 flows -The following table compares the features for OAuth 2.0 and OpenID Connect authorization flows in each type of tenant.+The following table compares tenant-level OAuth 2.0 and OpenID Connect capabilities. It doesn't define the supported request parameters for the Native Authentication API or the BYO UX handoff. | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- |@@ -158,13 +268,15 @@ The following table compares the features for OAuth 2.0 and OpenID Connect autho | [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 [native authentication](concept-native-authentication.md) |+| [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) | ### 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 apps in external tenants, always use the following format: `<tenant-name>.ciamlogin.com`.+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. -The following JSON shows an example of a .NET application `appsettings.json` file with an authority URL:+The following JSON shows a Microsoft-hosted authentication example in a .NET application's `appsettings.json` file: ```json {@@ -185,7 +297,7 @@ The following table compares the features for Microsoft Entra Conditional Access | Target resources | <ul><li>[Cloud apps](~/identity/conditional-access/concept-conditional-access-cloud-apps.md)</li><li>[User actions](~/identity/conditional-access/concept-conditional-access-cloud-apps.md#user-actions)</li><li>[Global Secure Access](~/identity/conditional-access/concept-conditional-access-cloud-apps.md#traffic-forwarding-profiles)</li><li>[Authentication context](~/identity/conditional-access/concept-conditional-access-cloud-apps.md#authentication-context)</li></ul> | <ul><li>[All resources, selected apps](./how-to-multifactor-authentication-customers.md), or [filter applications](~/identity/conditional-access/concept-filter-for-applications.md)</li><li>[Authentication context](~/identity/conditional-access/concept-conditional-access-cloud-apps.md#authentication-context)</li></ul> | | Conditions | <ul><li>[Sign-in risk](~/identity/conditional-access/concept-conditional-access-conditions.md#sign-in-risk)</li><li>[User risk](~/identity/conditional-access/concept-conditional-access-conditions.md#user-risk)</li><li>[Device platforms](~/identity/conditional-access/concept-conditional-access-conditions.md#device-platforms)</li><li>[Locations](~/identity/conditional-access/concept-conditional-access-conditions.md#locations)</li><li>[Client apps](~/identity/conditional-access/concept-conditional-access-conditions.md#client-apps)</li><li>[Filter for devices](~/identity/conditional-access/concept-conditional-access-conditions.md#filter-for-devices)</li></ul> | <ul><li>[Device platforms](~/identity/conditional-access/concept-conditional-access-conditions.md#device-platforms)</li><li>[Locations](~/identity/conditional-access/concept-conditional-access-conditions.md#locations)</li></ul> | | Grant | [Grant or block access to resources](~/identity/conditional-access/concept-conditional-access-grant.md) | <ul><li>[Block access](~/identity/conditional-access/concept-conditional-access-grant.md#block-access)</li><li>[Require multifactor authentication](./how-to-multifactor-authentication-customers.md)</li><li>[Require password reset](./how-to-enable-password-reset-customers.md)</li></ul> |-| Session | [Session controls](~/identity/conditional-access/concept-conditional-access-session.md) | The following session controls are available: <ul><li>Sign-in frequency</li><li>Persistent browser session</li></ul> |+| Session | [Session controls](~/identity/conditional-access/concept-conditional-access-session.md) | The following session controls are available: <ul><li>[Sign-in frequency (SIF)](../../identity/conditional-access/concept-session-lifetime.md#user-sign-in-frequency) for Microsoft-hosted authentication and supported Embedded native authentication integrations. Availability can differ by approach and API or SDK version.</li><li>Persistent browser session for browser-based sessions.</li></ul> | ## Terms-of-use policies @@ -195,7 +307,7 @@ The following table compares the features for terms-of-use policies in each type | ------- | ---------------- | --------------- | | 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. |-| 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). | [Same as workforce](how-to-customize-branding-customers.md#to-customize-the-logo-privacy-link-and-terms-of-use). |+| 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 @@ -203,11 +315,11 @@ The following table compares the features for user management in each type of te | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- |-| Types of accounts | <ul><li>Internal members, such as employees and admins.</li><li>External users who are [invited](../what-is-b2b.md) or use self-service sign-up.</li></ul> | <ul><li> External users created through self-service sign-up or [by an admin](how-to-manage-customer-accounts.md).</li><li> Internal users, with or without an admin role. </li><li> Invited users (preview), 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). |-| Manage user profile info | <ul><li>Manage users programmatically and by [using the admin center](~/fundamentals/how-to-manage-user-profile-info.md).</li><li>Manage guest users across tenants with [cross-tenant synchronization](/entra/identity/multi-tenant-organizations/cross-tenant-synchronization-overview).</li></ul> | Same as workforce, except cross-tenant synchronization isn't available. |-| Reset a user's password | Administrators can [reset a user's password](~/fundamentals/users-reset-password-azure-portal.md) if the user forgets the password, is locked out of a device, or never received a password. | Same as workforce. |-| Restore or remove a recently deleted user | After you delete a user, the account remains in a suspended state for 30 days. During that 30-day window, the user account can be restored, along with all its properties. | Same as workforce. |-| Disable accounts | Prevent the new user from signing in. | Same as workforce. |+| Types of accounts | <ul><li>Internal members, such as employees and admins.</li><li>External users who are [invited](../what-is-b2b.md) or use self-service sign-up.</li></ul> | <ul><li> External users created through self-service sign-up or [by an admin](how-to-manage-customer-accounts.md).</li><li> Internal users, with or without an admin role. </li><li> Invited users, 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). |+| Manage user profile info | <ul><li>Manage users programmatically and by [using the admin center](~/fundamentals/how-to-manage-user-profile-info.md).</li><li>Manage guest users across tenants with [cross-tenant synchronization](/entra/identity/multi-tenant-organizations/cross-tenant-synchronization-overview).</li></ul> | Manage users in the admin center or programmatically. Cross-tenant synchronization isn't available. |+| Reset a user's password | Administrators can [reset a user's password](~/fundamentals/users-reset-password-azure-portal.md) if the user forgets the password, is locked out of a device, or never received a password. | Supported. |+| Restore or remove a recently deleted user | After you delete a user, the account remains in a suspended state for 30 days. During that 30-day window, the user account can be restored, along with all its properties. | Supported. Restore users and their properties within 30 days. |+| Disable accounts | Prevent the new user from signing in. | Supported. | ## Password protection @@ -215,9 +327,9 @@ The following table compares the features for password protection in each type o | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- |-| Smart lockout | [Smart lockout](~/identity/authentication/howto-password-smart-lockout.md) helps lock out bad actors who try to guess your users' passwords or use brute-force methods to get in. | Same as workforce. |-| Global banned passwords | The [global banned passwords list](~/identity/authentication/concept-password-ban-bad.md#global-banned-password-list) automatically blocks commonly used weak or compromised passwords based on analysis of Microsoft Entra security data. | Same as workforce. |-| Custom banned passwords | Use the [custom banned passwords list](../../identity/authentication/tutorial-configure-custom-password-protection.md) to add specific strings to evaluate and block during password creation and reset. | Same as workforce. |+| Smart lockout | [Smart lockout](~/identity/authentication/howto-password-smart-lockout.md) helps lock out bad actors who try to guess your users' passwords or use brute-force methods to get in. | Supported. |+| Global banned passwords | The [global banned passwords list](~/identity/authentication/concept-password-ban-bad.md#global-banned-password-list) automatically blocks commonly used weak or compromised passwords based on analysis of Microsoft Entra security data. | Supported. |+| Custom banned passwords | Use the [custom banned passwords list](../../identity/authentication/tutorial-configure-custom-password-protection.md) to add specific strings to evaluate and block during password creation and reset. | Supported. | ## Token customization @@ -225,30 +337,31 @@ The following table compares the features for token customization in each type o | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- |-| Claims mapping | [Customize claims](~/identity-platform/jwt-claims-customization.md) issued in the JSON web token (JWT) for enterprise applications. | Same as workforce. Optional claims must be configured through [Attributes & Claims](how-to-add-attributes-to-token.md). |-| Claims transformation | [Apply a transformation to a user attribute](~/identity-platform/jwt-claims-customization.md) issued in the JWT for enterprise applications. | Same as workforce. |-| Custom claims provider | Use a [custom authentication extension](~/identity-platform/custom-extension-overview.md) that calls an external REST API to fetch claims from external systems. | Same as workforce. [Learn more](../../identity-platform/custom-claims-provider-overview.md). |+| Claims mapping | [Customize claims](~/identity-platform/jwt-claims-customization.md) issued in the JSON web token (JWT) for enterprise applications. | Supported. Configure optional claims through [Attributes & Claims](how-to-add-attributes-to-token.md). |+| Claims transformation | [Apply a transformation to a user attribute](~/identity-platform/jwt-claims-customization.md) issued in the JWT for enterprise applications. | Supported. |+| Custom claims provider | Use a [custom authentication extension](~/identity-platform/custom-extension-overview.md) that calls an external REST API to fetch claims from external systems. | Supported. [Custom claims provider](../../identity-platform/custom-claims-provider-overview.md). | | Security groups | [Configure group optional claims](../../identity-platform/optional-claims.md#configure-groups-optional-claims). | [Configure group optional claims](../../identity-platform/optional-claims.md#configure-groups-optional-claims), limited to the group object ID. |-| Token lifetimes | [Specify the lifetime](../../identity-platform/configurable-token-lifetimes.md) of security tokens issued by Microsoft Entra ID. | Same as workforce. |-| Session and token revocation | An administrator can [invalidate all the refresh tokens and session](/graph/api/user-revokesigninsessions) for a user. | Same as workforce. |+| Token lifetimes | [Specify the lifetime](../../identity-platform/configurable-token-lifetimes.md) of security tokens issued by Microsoft Entra ID. | Supported. |+| Session and token revocation | An administrator can [invalidate all the refresh tokens and session](/graph/api/user-revokesigninsessions) for a user. | Supported. | ## Single sign-on [Single sign-on (SSO)](../../identity-platform/msal-js-sso.md) provides a more seamless experience by reducing the number of times a user is asked for credentials. Users enter their credentials once. Other applications can reuse the established session on the same device and web browser without further prompting. -The following table compares the features for SSO in each type of tenant.+The following table compares browser-based SSO in each type of tenant. For Embedded native authentication and BYO UX session boundaries, see [Integration, policy, and sessions by approach](#integration-policy-and-sessions-by-approach). | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- | | Types of application registration | <ul><li>OpenID Connect</li> <li>OAuth 2.0</li> <li>SAML (enterprise application)</li></ul><br>Enterprise applications offer [more options](../../identity/enterprise-apps/plan-sso-deployment.md), like password-based, linked, and header-based registration. | <ul><li>OpenID Connect</li> <li>OAuth 2.0</li> <li>SAML (enterprise application)</li></ul> | | Domain name | When a user is authenticated, a session cookie is set on the Microsoft Entra domain `login.microsoftonline.com` in the web browser. | When a user is authenticated, a session cookie is set on the Microsoft Entra External ID domain `<tenant-name>.ciamlogin.com` or a [custom URL domain](concept-custom-url-domain.md) in the web browser. To ensure that SSO functions correctly, use a single URL domain. | | Stay signed in | You can turn on or turn off the option to [stay signed in](~/fundamentals/how-to-manage-stay-signed-in-prompt.yml). | The **Stay signed in?** prompt appears by default. To change or suppress it, use the **Persistent browser session** session control in a Conditional Access policy. [Learn more](how-to-user-flow-sign-up-sign-in-customers.md#control-the-stay-signed-in-prompt). |-| User provisioning | Use [automatic user provisioning](/entra/architecture/sync-scim) with System for Cross-domain Identity Management (SCIM) to sync user accounts between External ID and supported apps. This approach keeps user data up to date automatically.<br><br> User provisioning supports differential queries. These queries sync only the changes since the last update. This behavior improves performance and reduces system load. | Same as workforce. |-| Session invalidation | Scenarios where SSO might be invalidated, which requires reauthentication: <ul><li>Session expiry</li><li>Browser issues, such as clearing browser cookies or cache</li><li>Conditional Access policy, such as a multifactor authentication requirement</li><li>[Session revocation](/graph/api/user-revokesigninsessions)</li><li>Security issues, such as suspicious activity</li></ul><br>The application specifies in the authorization request to prompt the user for credentials by using the `login=prompt` query string parameter in OpenID Connect and the `ForceAuthn` attribute in the SAML request. | Same as workforce. |+| User provisioning | Use [automatic user provisioning](/entra/architecture/sync-scim) with System for Cross-domain Identity Management (SCIM) to sync user accounts between External ID and supported apps. This approach keeps user data up to date automatically.<br><br> User provisioning supports differential queries. These queries sync only the changes since the last update. This behavior improves performance and reduces system load. | Supported, including differential queries. |+| Session invalidation | Scenarios where SSO might be invalidated, which requires reauthentication: <ul><li>Session expiry</li><li>Browser issues, such as clearing browser cookies or cache</li><li>Conditional Access policy, such as a multifactor authentication requirement</li><li>[Session revocation](/graph/api/user-revokesigninsessions)</li><li>Security issues, such as suspicious activity</li></ul><br>The application specifies in the authorization request to prompt the user for credentials by using the `prompt=login` query string parameter in OpenID Connect and the `ForceAuthn` attribute in the SAML request. | Session expiration, browser state, Conditional Access, revocation, and security events can require reauthentication. Apps can also request reauthentication. | | Conditional Access | Check the [Conditional Access](#conditional-access) section. | Check the [Conditional Access](#conditional-access) section. |-| Microsoft Entra native authentication | Not available. | [Native authentication](concept-native-authentication.md) supports SSO for embedded web views. Cross-app SSO through system browsers isn't available with native authentication. |-| Sign-out | When a [SAML](../../identity-platform/single-sign-out-saml-protocol.md) or [OpenID Connect](../../identity-platform/v2-protocols-oidc.md#send-a-sign-out-request) application directs the user to the logout endpoint, Microsoft Entra ID removes and invalidates the user's session from the browser. | Same as workforce. |-| Single sign-out | Upon successful sign-out, Microsoft Entra ID sends a sign-out notification to all other [SAML](../../identity-platform/single-sign-out-saml-protocol.md) and [OpenID Connect](../../identity-platform/v2-protocols-oidc.md#single-sign-out) applications that the user is signed in to. | Same as workforce. |+| Sign-out | When a [SAML](../../identity-platform/single-sign-out-saml-protocol.md) or [OpenID Connect](../../identity-platform/v2-protocols-oidc.md#send-a-sign-out-request) application directs the user to the logout endpoint, Microsoft Entra ID removes and invalidates the user's session from the browser. | Supported for SAML and OpenID Connect apps. |+| Single sign-out | Upon successful sign-out, Microsoft Entra ID sends a sign-out notification to all other [SAML](../../identity-platform/single-sign-out-saml-protocol.md) and [OpenID Connect](../../identity-platform/v2-protocols-oidc.md#single-sign-out) applications that the user is signed in to. | Supported for SAML and OpenID Connect apps. |++Review your approach's session requirements for browser-session reuse and single sign-out. ## Integrated security solutions @@ -272,20 +385,24 @@ When you integrate either service with External ID, you can apply these security The following table compares the features for activity logs and reports across various types of tenants. +> [!IMPORTANT]+> Sign-up logs and Azure Monitor for external tenants are in preview. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to preview features.+ | Feature | Workforce tenant | External tenant | | ------- | ---------------- | --------------- |-| [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. | Same as workforce. |-| [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. | Same as workforce. |-| [Sign-up logs](~/identity/monitoring-health/concept-sign-ups.md) (preview) | Not available. | Microsoft Entra External ID logs all self-service sign-up events, including both successful sign-ups and failed attempts. |+| [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. | | [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 (preview)](./how-to-azure-monitor.md). |+| [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. | ## Microsoft Graph APIs -All features that are supported in external tenants are also supported for automation through Microsoft Graph APIs. Some features that are in preview in external tenants might be generally available through Microsoft Graph. For more information, see [Manage Microsoft Entra identity and network access by using Microsoft Graph](/graph/api/resources/identity-network-access-overview).+Use Microsoft Graph APIs to automate supported tenant administration operations. Check each operation's permissions and requirements; tenant administration support doesn't establish direct Microsoft Graph access from a BYO UX page or interoperability with native-issued tokens. For more information, see [Manage Microsoft Entra identity and network access by using Microsoft Graph](/graph/api/resources/identity-network-access-overview). ## Related content -- [Planning for customer identity and access management](concept-planning-your-solution.md)+- [Planning for customer identity and access management](concept-planning-your-solution.md).+- For existing integrations, see the [Native Authentication API V1 reference](~/identity-platform/reference-native-authentication-api-v1.md). This version remains supported, but its capabilities differ from the current API. 