Multifactor Authentication
In brief
The page now organizes MFA methods, policies, and availability by authentication approach, API, and SDK version. It adds native authentication registration and browser-flow guidance and links to a support matrix.
What Entra admins need to know
Administrators should consult the revised support matrix and integration guidance when configuring MFA methods or native authentication flows.
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.
Multifactor authentication in Microsoft Entra External ID external tenants
[!INCLUDE applies-to-external-only]
Multifactor authentication (MFA) adds a layer of security toin Microsoft Entra External ID helps protect your applications by requiring users to provide a second method for verifying their identityadditional verification during sign-up or sign-in. External tenants support the
[!INCLUDE authentication-approaches]
The following methods forcan be configured in an external tenant. Runtime method and registration support depends on the selected authentication as a second factor:approach and API/SDK version.
- Email one-time passcode (OTP).
SMS-based authentication,SMS-based authentication, available as an add-on (see details).on.Time-based one-time password (TOTP)Time-based one-time password (TOTP) from Microsoft Authenticator or a supported third-party authenticatorapp (see details).app.Passkey (FIDO2). Passkeys arePasskey (FIDO2), a phishing-resistantauthenticationmethod that can satisfy MFA in a single gesture and also enable passwordless sign-in (see details).in.
Authentication approach applicability
EnforcingConfigure MFA enhancespolicies and methods in your organizationexternal tenant. Confirm method coverage and registration requirements in the MFA support matrix. For policy enforcement and browser fallback support, see the integration and policy comparison.
[!INCLUDE native-authentication-public-preview]
With the Native Authentication API, inline registration uses the returned enroll and activate operations and can satisfy the policy without a separate MFA challenge. Complete required verification after sign-up or password reset before requesting tokens or completing a BYO UX browser flow.
A separate native-app browser sign-in restarts authentication. It isn's security by addingt an extra layer of verification, making it more difficultescape-to-web-and-resume mechanism for unauthorized users to gain access.an active native or BYO UX transaction. See the Native authentication overview and Bring Your Own UX guidance.
CreatingCreate an MFA policy
In an external tenant, you can use Microsoft Entra Conditional Access to create a policy that prompts users for MFA when they sign up or sign in to your app. You create this policy in the Microsoft Entra admin center under Conditional Access in the Protection section. You can specify which users and groups the policy applyapplies to, including all users and excluding any emergency access or break-glass accounts.
In the policy, you define the applications that require MFA. You can apply the policy to all cloud apps or select specific apps, while excluding any applications that don't require MFA. Then you configure the policy to grant access only if users complete the MFA requirement.
Step-up MFA with Conditional Access authentication context
Multifactor authentication (MFA)MFA with authentication context lets you apply stronger security onlyrequire additional verification when users access sensitive data or perform critical actions. You don’t need to enforce MFAactions, rather than for the entire app.
With Microsoft Entra Conditional Access authentication context, developers can add step-up authentication, such as MFA, inside their apps. Use this for scenarios like high-value transactions or viewing personal information.
This approach supports Zero Trust principles. It ensures least principles and least-privilege access and reduceswhile reducing user friction. Users get
This later-operation step-up capability applies to Microsoft-hosted authentication and BYO UX, not Embedded native authentication. Satisfying claims and MFA requirements established at the start of a secure and seamless experience.native authorization transaction is different from requesting step-up for a later operation.
EnablingEnable MFA methods
When you select identity provider options in your user flows, you define the first-factor authentication methods for sign-up and sign-in. Second-factor verification methods for MFA are configured in the Microsoft Entra admin center under Entra ID > Authentication methods.
Depending onWith Microsoft-hosted authentication, the first-factor choice determines which option you choose as the first factor, different second-factor verification methods are available for multifactor authentication (MFA). Native Authentication API and SDK availability is scoped separately in the comparison.
The following method combinations describe Microsoft-hosted coverage. For the Native Authentication API and BYO UX, the supported second factors are email and SMS, subject to the same restriction against reusing email OTP as both factors.
- Email with password or username with password: For these first-factor methods, you can enable email one-time passcode, SMS, TOTP, passkey (FIDO2), or a combination as second-factor verification methods for MFA.
- External identity providers: You can enable email one-time passcode, SMS, TOTP, or a combination as second-factor verification methods for MFA. Passkey (FIDO2) isn't currently available for users who sign in with an external identity provider.
When SMS is enabled for MFA, users sign in with their primary method and are prompted to verify their identity with a code sent via text. They enter their phone number and receive an SMS with the verification code.
:::image type="content" source="media/concept-multifactor-authentication-customers/sms-text.png" alt-text="Screenshot of thean SMS text for MFA.message with an MFA verification code." border="false":::
External ID mitigateshelps prevent fraudulent sign-ups and sign-ins via SMS by enforcing the followingwith these measures:
- Telephony throttling limits help prevent outages and slowdowns. See Service limits and restrictions.
- CAPTCHA for SMS MFA helps prevent automated attacks by distinguishing human users from
automatedbots.If a risky user is detected, we block the user from signing in or ask the user to complete a CAPTCHAMicrosoft-hosted pages can present this challenge beforesendingan SMSverification code.is sent.
SMS pricing tiers by country/region
The following table provides details about the differentlists SMS authentication pricing tiers for SMS based authentication services across various countriesby country or regions.region. For pricing details, see Microsoft Entra External ID pricing.
SMS is an add-on feature and requires a linked subscription. If your subscription expires or is canceled, end users will no longer be able to authenticate using SMS, which could block them from signing in depending on your MFA policy.
| Tier | Countries/Regions |
|---|---|
| Phone Authentication Low Cost | Australia, Brazil, Brunei, Canada, Chile, China, Colombia, Cyprus, North Macedonia, Poland, Portugal, South Korea, Thailand, Türkiye, United States |
| Phone Authentication Mid Low Cost | Greenland, Albania, American Samoa, Austria, Bahamas, Bahrain, Bosnia & Herzegovina, Botswana, Costa Rica, Czech Republic, Denmark, Estonia, Faroe Islands, Finland, France, Greece, Hong Kong SAR, Hungary, Iceland, Ireland, Italy, Japan, Latvia, Lithuania, Luxembourg, Macao SAR, Malta, Mexico, Micronesia, Moldova, Namibia, New Zealand, Nicaragua, Norway, Romania, São Tomé and Príncipe, Seychelles Republic, Singapore, Slovakia, Solomon Islands, Spain, Sweden, Switzerland, Taiwan, United Kingdom, United States Virgin Islands, Uruguay |
| Phone Authentication Mid High Cost | Andorra, Angola, Anguilla, Antarctica, Antigua and Barbuda, Argentina, Armenia, Aruba, Barbados, Belgium, Benin, Bolivia, Bonaire, Curaçao, Saba, Sint Eustatius and Sint Maarten, British Virgin Islands, Bulgaria, Burkina Faso, Cameroon, Cayman Islands, Central African Republic, Cook Islands, Côte d’Ivoire, Croatia, Diego Garcia, Djibouti, Dominican Republic, |
| Phone Authentication High Cost | Liechtenstein, Bermuda, Cabo Verde, Cambodia, Democratic Republic of Congo, Dominica, Egypt, Equatorial Guinea, Ghana, Guatemala, Guinea-Bissau, Israel, |
Opt-in regions for SMS
StartingSince January 2025, certain country codes will beare deactivated by default for SMS verification. If you want toTo allow traffic from deactivated regions, you need to activate them for your application using the Microsoft Graph event policy. See Regions requiring opt-in for SMS verification.onPhoneMethodLoadStarteventonPhoneMethodLoadStart
Time-based one-time password (TOTP)
TOTP is a standards-based method that generates a temporary verification code in Microsoft Authenticator or a supported third-party authenticator app. It works as a second-factor verification method with Microsoft-hosted authentication. It isn't supported through the Native Authentication API or BYO UX.
When TOTP is enabled and MFA is required, users register an authenticator app by scanning a QR code. For subsequent MFA challenges, users enter the verification code displayed in their authenticator app.
Passkeys (FIDO2) provide phishing-resistant, passwordless authentication that uses public-key cryptography. A passkey can be used to satisfy MFA in a single gesture (face, fingerprint, PIN, or security key) or as a primary, passwordless sign-in method. Only email + password and username + password local account users can register a passkey. Passkey registration requires a custom URL domain, and users must complete MFA before registering a passkey.
These passkey capabilities apply to Microsoft-hosted authentication, not the Native Authentication API or BYO UX.
For setup steps, see Sign in with passkeys.
Next steps
@@ -1,34 +1,45 @@ ----title: MFA in external tenants-description: Learn about using MFA to secure apps in your external tenant and enabling email one-time passcodes (EOTP), SMS, time-based one-time passwords (TOTP), or passkeys (FIDO2) for verification.+title: Multifactor Authentication+description: Explore multifactor authentication in Microsoft Entra External ID, including methods, policies, and availability for each authentication approach. ms.topic: concept-article-ms.date: 11/06/2026-ms.custom: it-pro, references_regions+ms.date: 11/13/2026+ms.custom: it-pro, references_regions, msecd-doc-authoring-1030 ai-usage: ai-assisted -#Customer intent: As a dev, devops, or it admin, I want to learn about ways to secure apps in my external tenant by adding multifactor authentication and enabling SMS, email one-time passcodes, TOTP, and passkeys.+#customer intent: As an application developer or IT administrator, I want to understand multifactor authentication methods and policies so that I can secure apps in my external tenant. --- -# Multifactor authentication in external tenants+# Multifactor authentication in Microsoft Entra External ID external tenants -[!INCLUDE [applies-to-external-only](../includes/applies-to-external-only.md)]+Multifactor authentication (MFA) in Microsoft Entra External ID helps protect your applications by requiring additional verification during sign-up or sign-in. -Multifactor authentication (MFA) adds a layer of security to your applications by requiring users to provide a second method for verifying their identity during sign-up or sign-in. External tenants support the following methods for authentication as a second factor:+[!INCLUDE [authentication-approaches](../includes/applies-to-authentication-approaches.md)] -- Email one-time passcode-- SMS-based authentication, available as an add-on ([see details](#sms-based-authentication)).-- Time-based one-time password (TOTP) from Microsoft Authenticator or a supported third-party authenticator app ([see details](#time-based-one-time-password-totp)).-- Passkey (FIDO2). Passkeys are a phishing-resistant authentication method that can satisfy MFA in a single gesture and also enable passwordless sign-in ([see details](#passkey-fido2)).+The following methods can be configured in an external tenant. Runtime method and registration support depends on the selected authentication approach and API/SDK version. -Enforcing MFA enhances your organization's security by adding an extra layer of verification, making it more difficult for unauthorized users to gain access.+- Email one-time passcode (OTP).+- [SMS-based authentication](#sms-based-authentication), available as an add-on.+- [Time-based one-time password (TOTP)](#time-based-one-time-password-totp) from Microsoft Authenticator or a supported third-party authenticator app.+- [Passkey (FIDO2)](#passkey-fido2), a phishing-resistant method that can satisfy MFA in a single gesture and also enable passwordless sign-in. -> [!NOTE]-> MFA is supported for both browser-delegated and native authentication. With browser-delegated authentication, the MFA challenge is handled on the Microsoft-hosted sign-in page. With native authentication, your app surfaces the MFA prompt inline using the MSAL SDK; if the app doesn't advertise the `mfa_required` capability, the native authentication API initiates a [web fallback](/entra/identity-platform/concept-native-authentication-web-fallback) to complete the challenge. For more information about choosing an approach, see [Choose an authentication approach](concept-choose-authentication-approach.md).+## Authentication approach applicability++Configure MFA policies and methods in your external tenant. Confirm method coverage and registration requirements in the [MFA support matrix](concept-supported-features-customers.md#multifactor-authentication-behavior). For policy enforcement and browser fallback support, see the [integration and policy comparison](concept-supported-features-customers.md#integration-policy-and-sessions-by-approach).++[!INCLUDE [native-authentication-public-preview](../includes/native-authentication-public-preview.md)]++With the Native Authentication API, inline registration uses the returned `enroll` and `activate` operations and can satisfy the policy without a separate MFA challenge. Complete required verification after sign-up or password reset before requesting tokens or completing a BYO UX browser flow.++A separate native-app browser sign-in restarts authentication. It isn't an escape-to-web-and-resume mechanism for an active native or BYO UX transaction. See the [Native authentication overview](../../identity-platform/concept-native-authentication.md) and [Bring Your Own UX guidance](concept-choose-authentication-approach.md#when-to-use-bring-your-own-ux).++For architectural guidance, see [Choose an authentication approach](concept-choose-authentication-approach.md). -## Creating an MFA policy+<a name="creating-an-mfa-policy"></a> -In an external tenant, you can use Microsoft Entra Conditional Access to create a policy that prompts users for MFA when they sign up or sign in to your app. You create this policy in the Microsoft Entra admin center under Conditional Access in the Protection section. You can specify which users and groups the policy apply to, including all users and excluding any emergency access or break-glass accounts.+## Create an MFA policy++In an external tenant, you can use Microsoft Entra Conditional Access to create a policy that prompts users for MFA when they sign up or sign in to your app. You create this policy in the Microsoft Entra admin center under Conditional Access in the Protection section. You can specify which users and groups the policy applies to, including all users and excluding any emergency access or break-glass accounts. In the policy, you define the applications that require MFA. You can apply the policy to all cloud apps or select specific apps, while excluding any applications that don't require MFA. Then you configure the policy to grant access only if users complete the MFA requirement. @@ -36,15 +47,21 @@ For details, see [how to create a Conditional Access policy in an external tenan ### Step-up MFA with Conditional Access authentication context -Multifactor authentication (MFA) with authentication context lets you apply stronger security only when users access sensitive data or perform critical actions. You don’t need to enforce MFA for the entire app.+MFA with authentication context lets you require additional verification when users access sensitive data or perform critical actions, rather than for the entire app. With Microsoft Entra [Conditional Access authentication context](/entra/identity-platform/developer-guide-conditional-access-authentication-context), developers can add step-up authentication, such as MFA, inside their apps. Use this for scenarios like high-value transactions or viewing personal information.-This approach supports Zero Trust principles. It ensures least privilege access and reduces user friction. Users get a secure and seamless experience.+This approach supports Zero Trust principles and least-privilege access while reducing user friction.++This later-operation step-up capability applies to Microsoft-hosted authentication and BYO UX, not Embedded native authentication. Satisfying claims and MFA requirements established at the start of a native authorization transaction is different from requesting step-up for a later operation.++<a name="enabling-mfa-methods"></a> -## Enabling MFA methods+## Enable MFA methods When you select identity provider options in your user flows, you define the first-factor authentication methods for sign-up and sign-in. Second-factor verification methods for MFA are configured in the Microsoft Entra admin center under **Entra ID** > **Authentication methods**. -Depending on which option you choose as the first factor, different second-factor verification methods are available for [multifactor authentication (MFA)](how-to-multifactor-authentication-customers.md).+With Microsoft-hosted authentication, the first-factor choice determines which second-factor methods are available for [multifactor authentication (MFA)](how-to-multifactor-authentication-customers.md). Native Authentication API and SDK availability is scoped separately in the comparison.++The following method combinations describe Microsoft-hosted coverage. For the Native Authentication API and BYO UX, the supported second factors are email and SMS, subject to the same restriction against reusing email OTP as both factors. - **Email with password or username with password**: For these first-factor methods, you can enable email one-time passcode, SMS, TOTP, passkey (FIDO2), or a combination as second-factor verification methods for MFA. - **External identity providers**: You can enable email one-time passcode, SMS, TOTP, or a combination as second-factor verification methods for MFA. Passkey (FIDO2) isn't currently available for users who sign in with an external identity provider.@@ -64,36 +81,36 @@ SMS is available at an additional cost for second-factor verification and for se When SMS is enabled for MFA, users sign in with their primary method and are prompted to verify their identity with a code sent via text. They enter their phone number and receive an SMS with the verification code. - :::image type="content" source="media/concept-multifactor-authentication-customers/sms-text.png" alt-text="Screenshot of the SMS text for MFA." border="false":::+ :::image type="content" source="media/concept-multifactor-authentication-customers/sms-text.png" alt-text="Screenshot of an SMS message with an MFA verification code." border="false"::: -External ID mitigates fraudulent sign-ups and sign-ins via SMS by enforcing the following measures:+External ID helps prevent fraudulent sign-ups and sign-ins via SMS with these measures: - Telephony throttling limits help prevent outages and slowdowns. See [Service limits and restrictions](reference-service-limits.md).-- CAPTCHA for SMS MFA helps prevent automated attacks by distinguishing human users from automated bots. If a risky user is detected, we block the user from signing in or ask the user to complete a CAPTCHA before sending an SMS verification code.+- CAPTCHA for SMS MFA helps prevent automated attacks by distinguishing human users from bots. Microsoft-hosted pages can present this challenge before an SMS is sent. ### SMS pricing tiers by country/region -The following table provides details about the different pricing tiers for SMS based authentication services across various countries or regions. For pricing details, see [Microsoft Entra External ID pricing](https://aka.ms/ExternalIDPricing).+The following table lists SMS authentication pricing tiers by country or region. For pricing details, see [Microsoft Entra External ID pricing](https://aka.ms/ExternalIDPricing). SMS is an add-on feature and requires a [linked subscription](../external-identities-pricing.md#link-an-external-tenant-to-a-subscription). If your subscription expires or is canceled, end users will no longer be able to authenticate using SMS, which could block them from signing in depending on your MFA policy. -|Tier |Countries/Regions |-|-----------------------------------|-------------------|-|Phone Authentication Low Cost |Australia, Brazil, Brunei, Canada, Chile, China, Colombia, Cyprus, North Macedonia, Poland, Portugal, South Korea, Thailand, Türkiye, United States |-|Phone Authentication Mid Low Cost |Greenland, Albania, American Samoa, Austria, Bahamas, Bahrain, Bosnia & Herzegovina, Botswana, Costa Rica, Czech Republic, Denmark, Estonia, Faroe Islands, Finland, France, Greece, Hong Kong SAR, Hungary, Iceland, Ireland, Italy, Japan, Latvia, Lithuania, Luxembourg, Macao SAR, Malta, Mexico, Micronesia, Moldova, Namibia, New Zealand, Nicaragua, Norway, Romania, São Tomé and Príncipe, Seychelles Republic, Singapore, Slovakia, Solomon Islands, Spain, Sweden, Switzerland, Taiwan, United Kingdom, United States Virgin Islands, Uruguay |-|Phone Authentication Mid High Cost |Andorra, Angola, Anguilla, Antarctica, Antigua and Barbuda, Argentina, Armenia, Aruba, Barbados, Belgium, Benin, Bolivia, Bonaire, Curaçao, Saba, Sint Eustatius and Sint Maarten, British Virgin Islands, Bulgaria, Burkina Faso, Cameroon, Cayman Islands, Central African Republic, Cook Islands, Côte d’Ivoire, Croatia, Diego Garcia, Djibouti, Dominican Republic, Dominican Republic, Dominican Republic, Ecuador, El Salvador, Eritrea, Falkland Islands, Fiji, French Guiana, French Polynesia, Gambia, Georgia, Germany, Gibraltar, Grenada, Guadeloupe, Guam, Guinea, Guyana, Honduras, India, Kenya, Kiribati, Laos, Liberia, Malaysia, Marshall Islands, Martinique, Mauritius, Monaco, Montenegro, Montserrat, Netherlands, New Caledonia, Niue, Oman, Palau, Panama, Paraguay, Peru, Puerto Rico, Puerto Rico, Réunion, Rwanda, Saint Helena, Ascension and Tristan de Cunha, Saint Kitts & Nevis, Saint Lucia, Saint Pierre & Miquelon, Saint Vincent and the Grenadines, Saipan, Samoa, San Marino, Saudi Arabia, Sint Maarten, Slovenia, South Africa, South Sudan, Suriname, Swaziland (New Name is Kingdom of Eswatini), Timor-Leste, Tokelau, Tonga, Turks & Caicos, Tuvalu, United Arab Emirates, Vanuatu, Venezuela, Vietnam, Wallis and Futuna |-|Phone Authentication High Cost |Liechtenstein, Bermuda, Cabo Verde, Cambodia, Democratic Republic of Congo, Dominica, Egypt, Equatorial Guinea, Ghana, Guatemala, Guinea-Bissau, Israel, Jamaica, Jamaica, Kosovo, Lesotho, Maldives, Mali, Mauritania, Morocco, Mozambique, Papua New Guinea, Philippines, Qatar, Sierra Leone, Trinidad & Tobago, Ukraine, Zimbabwe, Afghanistan, Algeria, Azerbaijan, Bangladesh, Belarus, Belize, Bhutan, Burundi, Chad, Comoros, Congo, Ethiopia, Gabonese Republic, Haiti, Indonesia, Iraq, Jordan, Kuwait, Kyrgyzstan, Lebanon, Libya, Madagascar, Malawi, Mongolia, Myanmar, Nauru, Nepal, Niger, Nigeria, Pakistan, Palestinian National Authority, Russia, Senegal, Serbia, Somalia, Sri Lanka, Sudan, Tajikistan, Tanzania, Togolese Republic, Tunisia, Turkmenistan, Uganda, Uzbekistan, Yemen, Zambia |+| Tier | Countries/Regions |+| ----------------------------------- | ------------------- |+| Phone Authentication Low Cost | Australia, Brazil, Brunei, Canada, Chile, China, Colombia, Cyprus, North Macedonia, Poland, Portugal, South Korea, Thailand, Türkiye, United States |+| Phone Authentication Mid Low Cost | Greenland, Albania, American Samoa, Austria, Bahamas, Bahrain, Bosnia & Herzegovina, Botswana, Costa Rica, Czech Republic, Denmark, Estonia, Faroe Islands, Finland, France, Greece, Hong Kong SAR, Hungary, Iceland, Ireland, Italy, Japan, Latvia, Lithuania, Luxembourg, Macao SAR, Malta, Mexico, Micronesia, Moldova, Namibia, New Zealand, Nicaragua, Norway, Romania, São Tomé and Príncipe, Seychelles Republic, Singapore, Slovakia, Solomon Islands, Spain, Sweden, Switzerland, Taiwan, United Kingdom, United States Virgin Islands, Uruguay |+| Phone Authentication Mid High Cost | Andorra, Angola, Anguilla, Antarctica, Antigua and Barbuda, Argentina, Armenia, Aruba, Barbados, Belgium, Benin, Bolivia, Bonaire, Curaçao, Saba, Sint Eustatius and Sint Maarten, British Virgin Islands, Bulgaria, Burkina Faso, Cameroon, Cayman Islands, Central African Republic, Cook Islands, Côte d’Ivoire, Croatia, Diego Garcia, Djibouti, Dominican Republic, Ecuador, El Salvador, Eritrea, Falkland Islands, Fiji, French Guiana, French Polynesia, Gambia, Georgia, Germany, Gibraltar, Grenada, Guadeloupe, Guam, Guinea, Guyana, Honduras, India, Kenya, Kiribati, Laos, Liberia, Malaysia, Marshall Islands, Martinique, Mauritius, Monaco, Montenegro, Montserrat, Netherlands, New Caledonia, Niue, Oman, Palau, Panama, Paraguay, Peru, Puerto Rico, Réunion, Rwanda, Saint Helena, Ascension and Tristan da Cunha, Saint Kitts & Nevis, Saint Lucia, Saint Pierre & Miquelon, Saint Vincent and the Grenadines, Saipan, Samoa, San Marino, Saudi Arabia, Sint Maarten, Slovenia, South Africa, South Sudan, Suriname, Eswatini, Timor-Leste, Tokelau, Tonga, Turks & Caicos, Tuvalu, United Arab Emirates, Vanuatu, Venezuela, Vietnam, Wallis and Futuna |+| Phone Authentication High Cost | Liechtenstein, Bermuda, Cabo Verde, Cambodia, Democratic Republic of Congo, Dominica, Egypt, Equatorial Guinea, Ghana, Guatemala, Guinea-Bissau, Israel, Jamaica, Kosovo, Lesotho, Maldives, Mali, Mauritania, Morocco, Mozambique, Papua New Guinea, Philippines, Qatar, Sierra Leone, Trinidad & Tobago, Ukraine, Zimbabwe, Afghanistan, Algeria, Azerbaijan, Bangladesh, Belarus, Belize, Bhutan, Burundi, Chad, Comoros, Congo, Ethiopia, Gabonese Republic, Haiti, Indonesia, Iraq, Jordan, Kuwait, Kyrgyzstan, Lebanon, Libya, Madagascar, Malawi, Mongolia, Myanmar, Nauru, Nepal, Niger, Nigeria, Pakistan, Palestinian National Authority, Russia, Senegal, Serbia, Somalia, Sri Lanka, Sudan, Tajikistan, Tanzania, Togolese Republic, Tunisia, Turkmenistan, Uganda, Uzbekistan, Yemen, Zambia | ### Opt-in regions for SMS -Starting January 2025, certain country codes will be deactivated by default for SMS verification. If you want to allow traffic from deactivated regions, you need to activate them for your application using the Microsoft Graph `onPhoneMethodLoadStartevent` policy. See [Regions requiring opt-in for SMS verification](how-to-region-code-opt-in.md).+Since January 2025, certain country codes are deactivated by default for SMS verification. To allow traffic from deactivated regions, activate them for your application using the Microsoft Graph `onPhoneMethodLoadStart` event policy. See [Regions requiring opt-in for SMS verification](how-to-region-code-opt-in.md). ## Time-based one-time password (TOTP) > [!NOTE] > TOTP authentication in external tenants will become generally available at the end of November 2026. Rollout will finish in early December 2026. -TOTP is a standards-based method that generates a temporary verification code in Microsoft Authenticator or a supported third-party authenticator app. It works as a second-factor verification method for MFA in external tenants.+TOTP is a standards-based method that generates a temporary verification code in Microsoft Authenticator or a supported third-party authenticator app. It works as a second-factor verification method with Microsoft-hosted authentication. It isn't supported through the Native Authentication API or BYO UX. When TOTP is enabled and MFA is required, users register an authenticator app by scanning a QR code. For subsequent MFA challenges, users enter the verification code displayed in their authenticator app. @@ -103,8 +120,10 @@ For setup steps, see [Add multifactor authentication (MFA) to an app](how-to-mul Passkeys (FIDO2) provide phishing-resistant, passwordless authentication that uses public-key cryptography. A passkey can be used to satisfy MFA in a single gesture (face, fingerprint, PIN, or security key) or as a primary, passwordless sign-in method. Only email + password and username + password local account users can register a passkey. Passkey registration requires a [custom URL domain](how-to-custom-url-domain.md), and users must complete MFA before registering a passkey. +These passkey capabilities apply to Microsoft-hosted authentication, not the Native Authentication API or BYO UX.+ For setup steps, see [Sign in with passkeys](how-to-sign-in-with-passkey.md). ## Next steps -[Add multifactor authentication (MFA) to an app](how-to-multifactor-authentication-customers.md)+[Add multifactor authentication (MFA) to an app](how-to-multifactor-authentication-customers.md). 