Microsoft Entra ID

Choose a telephony provider for SMS and voice authentication

5 August 2026New+44 / −0 lines

In brief

A new concept article explains planned customer-managed providers for SMS and voice authentication. Provider information is expected beginning September 18, 2026, with configuration beginning October 30, 2026; providers aren't available to configure yet.

What Entra admins need to know

Administrators should identify users who require telephony authentication, evaluate providers and organizational requirements, and plan a limited pilot and fallback method. Microsoft recommends phishing-resistant methods such as passkeys where possible.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

View full page diff

View on Microsoft Learn

The comparison below shows only the changed extract. Use the full-page view for complete context.

new file mode 100644

title: Choose a telephony provider for SMS and voice authentication description: Learn about customer-managed telephony providers for SMS and voice authentication in Microsoft Entra ID. ms.topic: concept-article ms.date: 08/04/2026 ai-usage: ai-generated

Customer intent: As an identity administrator, I want to understand customer-managed telephony providers so that I can plan continued use of SMS or voice authentication.

Choose a telephony provider for SMS and voice authentication

Microsoft Entra ID will support customer-managed telephony providers for organizations that need to continue using SMS or voice authentication. You select a telecommunications provider through the Microsoft Security Store and manage the provider relationship for your organization.

Microsoft recommends phishing-resistant authentication methods, such as passkeys, instead of SMS or voice. Use a telephony provider only for user populations that have a business, regulatory, or technical requirement for telephony-based authentication.

How telephony providers work

A customer-managed telephony provider delivers the SMS messages or voice calls that users need to complete authentication. Microsoft Entra ID continues to apply your authentication method policies and coordinates the authentication experience.

Your organization is responsible for selecting a provider, reviewing its regional coverage and terms, completing the provider agreement, configuring the provider for Microsoft Entra ID, and monitoring the service.

For the full transition schedule, see Passkeys by default and retirement of Microsoft-provided SMS and voice authentication.

Plan your provider adoption

Before you select a provider:

Identify the users who have a documented requirement for SMS or voice authentication.
Confirm that a phishing-resistant method doesn't meet the requirement.
Compare provider availability, geographic coverage, supported delivery channels, pricing, support, security, and compliance capabilities.
Review procurement, privacy, and regulatory requirements with the appropriate teams in your organization.
Plan a pilot with a limited group before you expand deployment.
Prepare a fallback authentication method and support process for delivery interruptions.

Next steps

@@ -0,0 +1,44 @@+---+title: Choose a telephony provider for SMS and voice authentication+description: Learn about customer-managed telephony providers for SMS and voice authentication in Microsoft Entra ID.+ms.topic: concept-article+ms.date: 08/04/2026+ai-usage: ai-generated++# Customer intent: As an identity administrator, I want to understand customer-managed telephony providers so that I can plan continued use of SMS or voice authentication.+---++# Choose a telephony provider for SMS and voice authentication++Microsoft Entra ID will support customer-managed telephony providers for organizations that need to continue using SMS or voice authentication. You select a telecommunications provider through the Microsoft Security Store and manage the provider relationship for your organization.++Microsoft recommends phishing-resistant authentication methods, such as [passkeys](concept-authentication-passkeys-fido2.md), instead of SMS or voice. Use a telephony provider only for user populations that have a business, regulatory, or technical requirement for telephony-based authentication.++> [!IMPORTANT]+> Customer-managed telephony providers aren't available to configure yet. Provider information becomes available beginning September 18, 2026, and configuration becomes available beginning October 30, 2026.++## How telephony providers work++A customer-managed telephony provider delivers the SMS messages or voice calls that users need to complete authentication. Microsoft Entra ID continues to apply your authentication method policies and coordinates the authentication experience.++Your organization is responsible for selecting a provider, reviewing its regional coverage and terms, completing the provider agreement, configuring the provider for Microsoft Entra ID, and monitoring the service.++For the full transition schedule, see [Passkeys by default and retirement of Microsoft-provided SMS and voice authentication](concept-sms-voice-retirement.md).++## Plan your provider adoption++Before you select a provider:++- Identify the users who have a documented requirement for SMS or voice authentication.+- Confirm that a phishing-resistant method doesn't meet the requirement.+- Compare provider availability, geographic coverage, supported delivery channels, pricing, support, security, and compliance capabilities.+- Review procurement, privacy, and regulatory requirements with the appropriate teams in your organization.+- Plan a pilot with a limited group before you expand deployment.+- Prepare a fallback authentication method and support process for delivery interruptions.++## Next steps++- [Review frequently asked questions about telephony providers](phone-providers-faq.yml).+- [Prepare for the retirement of Microsoft-provided SMS and voice authentication](concept-sms-voice-retirement.md).+- [Plan a passkey deployment](how-to-deploy-phishing-resistant-passwordless-authentication.md).+- [Review voice call authentication](concept-authentication-phone-options.md).