Changes › MC1519855

(Updated) Microsoft Entra: Choose your own telephony provider now generally available

Microsoft Entra Stay informed
Published
21 Oct 2026
Last modified
30 Oct 2026 19:34 UTC
Act by
—
Ends
30 Nov 2026
First archived
22 Oct 2026
Revisions
2
Tags
Updated messageNew featureUser impactAdmin impact

Full post

Updated October 30, 2026: We have updated this post with additional information as the feature is now generally available. Thank you for your patience. 

[What and why]

Choose Your Own Telephony Provider (CYOT) is now generally available in Microsoft Entra ID. With CYOT, your organization can deliver SMS and voice authentication through a supported telecom provider of its choice. You purchase the provider's offer in Microsoft Security Store and manage the commercial relationship directly with the provider. 

Microsoft-provided SMS and voice authentication begins retiring on February 1, 2027. To keep SMS and voice authentication available for users who need it, set up CYOT before that date. 

Microsoft recommends phishing-resistant authentication methods, such as passkeys, instead of SMS or voice. Use telephony-based authentication only for users who have a business, regulatory, or technical need for it.

[What you need to do]

If your organization plans to use CYOT: 

  1. Identify users who need SMS or voice. Confirm which users have a requirement that phishing-resistant methods can't meet. 
  2. Choose a provider. Compare the supported telecom providers on coverage, channels, pricing, support, and compliance. 
  3. Check purchasing requirements. Confirm that you have a paid Azure subscription that is eligible for Security Store purchases, and that you have the Owner role, or Contributor plus Role Based Access Control Administrator. 
  4. Estimate costs. Review provider pricing and Azure hosting costs. 
  5. Set up and roll out. Follow Set up SMS and voice. Start in evaluation mode, then increase traffic to your provider in stages. 
  6. Complete your transition before February 1, 2027. Review the guidance for the retirement of Microsoft-provided SMS and voice authentication.

Learn more 

Related messages

Discussion

No messages yet — start the thread.

Sign in with your email to join the discussion — we send a one-time link, no password.

© Microsoft — archived from the Microsoft 365 Message Center. Content notice

Revision history

  1. 22 Oct 2026 00:05 UTC — Microsoft's lastModified 21 Oct 2026 23:24 UTC
  2. 30 Oct 2026 20:05 UTC — Microsoft's lastModified 30 Oct 2026 19:34 UTC