Microsoft Entra ID
Authentication

Troubleshoot SMS and voice with your own telephony provider

In brief

The article replaces “telecom provider” with “telephony provider,” updates related resource titles and links, and adds an anchor for the previous heading.

What Entra admins need to know

Administrators using CYOT troubleshooting will find more consistent terminology and updated navigation to setup, reliability, fraud, logging, and monitoring 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.

Troubleshoot SMS and voice with your own telecomtelephony provider

Use this article to trace SMS and voice requests end to end with Choose Your Own Telephony Provider (CYOT), find where a request stopped, and contact the right team to resolve it: Microsoft support, your Azure team, or your telecomtelephony provider.

Stage What happens Where to look
1. Microsoft Entra sends the request Microsoft Entra requires an SMS or voice code and sends the request to your endpoint. Microsoft Entra audit logs
2. Your endpoint processes it Your Function App receives the request and sends it to your telecomtelephony provider. Function App logs
3. Your provider delivers it Your provider sends the SMS message or voice call to the user's phone. Your provider's portal
4. The user signs in The user enters the code, and Microsoft Entra completes authentication. Microsoft Entra sign-in logs

| CyotDeliveryFailed with EndpointClientError | Your endpoint rejected the request. Check your Function App logs and authentication settings. | Your Azure team | | CyotDeliveryFailed with EndpointServerError | Your endpoint returned an error or didn't respond in time. Check your Function App logs and your provider's status. | Your Azure team | | CyotDeliveryFailed with NonceMismatch | Your endpoint's response didn't match what Microsoft Entra expects. Compare any customizations with the CYOT sample. | Your Azure team | | CyotDeliverySucceeded, but the user didn't receive the code | Your endpoint accepted the request. Check your provider's delivery records. | Your telecomtelephony provider | | The user received the code, but sign-in failed | Check the sign-in logs for an expired, reused, or incorrect code. | Microsoft support | | Delivery blocked to certain countries/regions, fraud blocks, or unexpected charges | Review your provider's fraud, destination, and spending controls. | Your telecomtelephony provider |

|---|---|---| | Microsoft support | Authentication method policy, Microsoft Entra authentication, and the request to your endpoint | Get support for Microsoft Entra | | Your Azure team | Your Function App, its configuration, and Azure resources | Internal. For Azure platform issues, contact Azure support. | | Your telecomtelephony provider | Provider account, delivery, fraud controls, and usage charges | Support details in the provider's Microsoft Security Store listing |

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…