Microsoft Entra ID
Authentication

Choose your own telephony provider for SMS and voice authentication

In brief

The page consistently replaces “telecom provider” with “telephony provider” across descriptions, architecture guidance, responsibilities, and related setup, fraud, resiliency, and cost links.

What Entra admins need to know

Administrators will see consistent terminology when using CYOT planning and setup guidance.

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

Documentation change

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


title: Choose your own telephony provider for SMS and voice authentication description: Learn how CYOT works, available telecomtelephony providers, and how to plan setup, fraud protection, resiliency, and costs. ms.topic: concept-article ms.date: 10/30/2026 ai-usage: ai-assisted

Choose Your Own Telephony Provider (CYOT) lets your organization use a supported telecomtelephony provider to deliver SMS and voice authentication for Microsoft Entra ID.

With CYOT, Microsoft Entra continues to manage the authentication experience, including one-time passcode (OTP) generation and validation, while SMS messages and voice calls are delivered through the telecomtelephony provider that your organization selects and configures.

CYOT gives your organization more control over telecomtelephony provider selection, geographic coverage, pricing, and telecomtelephony delivery.

  1. Microsoft Entra initiates the authentication request.
  2. Microsoft Entra sends the request to the CYOT integration deployed in your Azure subscription.
  3. The integration sends the request to your configured telecomtelephony provider.
  4. Your telecomtelephony provider delivers the SMS message or voice call to the user.
  5. Microsoft Entra completes the authentication flow.

The Azure Function deployed in your subscription connects Microsoft Entra with your telecomtelephony provider.

:::image type="content" source="media/concept-phone-providers/telephony-provider-integration-diagram.jpeg" alt-text="Simplified CYOT architecture diagram showing Microsoft Entra connected to a telecomtelephony provider through an Azure Function in your Azure subscription." lightbox="media/concept-phone-providers/telephony-provider-integration-diagram.jpeg":::

Available telephony providers

Select a supported telecomtelephony provider based on your organization's coverage, pricing, and other requirements.

Review pricing and other commercial details for the available provider offers:

Understand your responsibilities

With CYOT, your organization owns the Azure resources deployed in your subscription and your telecomtelephony provider account, so you keep full control over how they run. The guided deployment sets up the integration for you, and your team manages the Azure Function and provider account from there.

Owner Responsibilities
Microsoft Microsoft Entra authentication and the handoff to your endpoint.
Customer Deploying and operating the integration, managing the telecomtelephony provider account, and configuring fraud controls.
Telephony provider SMS and voice delivery, and offering fraud controls.

Get started with CYOT

  1. Evaluate. Validate the integration while Microsoft continues to deliver messages, so users aren't affected.
  2. Roll out. Move traffic to your provider gradually, validating at each stage.

For detailed instructions, see Set up SMS and voice with your own telephony provider in the Microsoft Entra admin center.

Prevent telephony fraud

Work with your telecomtelephony provider to configure the fraud protection, destination, usage, and spending controls appropriate for your organization's traffic and risk requirements.

See Prevent telephony fraud when using your own telephony provider.

Plan for resiliency

Plan the availability and recovery of the Azure resources and telecomtelephony provider used by your CYOT integration.

Organizations with additional availability requirements can implement cross-region resiliency and, where appropriate, configure provider redundancy.

See Plan for resiliency when using your own telephony provider.

Understand costs

CYOT can involve two separate categories of costs:

  • TelecomTelephony provider costs for SMS and voice delivery through your selected provider.
  • Azure costs for the Azure Function and supporting resources deployed in your subscription.

Review both before moving production authentication traffic to CYOT.

See Estimate telephony-provider and Azure hosting costs.

Troubleshoot CYOT

To diagnose SMS or voice issues, identify whether the issue is in Microsoft Entra authentication and configuration, your CYOT integration, or telecomtelephony provider delivery.

See Troubleshoot SMS and voice with your own telephony provider for diagnostic guidance and information about where to get support.

Related content

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…