Microsoft delays Entra SMS and voice retirement dates

Global Admins and external users now have another five months before Microsoft switches off its SMS and voice authentication service. The original version of MC1426371 put every affected user on the same 1 February 2027 deadline, but Microsoft’s September update moves these two groups to 1 July 2027.

The revised message also explains how organisations can keep telephony-based authentication after Microsoft stops providing it. You will need to select and pay for a telecom provider through the Microsoft Security Store. Microsoft still wants users on passkeys, but SMS and voice are no longer facing an outright retirement from Entra ID.

Two retirement dates replace one

Most users remain subject to the original 1 February 2027 deadline. After that date, Microsoft-provided SMS and voice will stop working for them. If SMS or voice is their only available MFA method and the tenant has no customer-managed telecom provider, Microsoft says Entra ID will show a blocking passkey registration prompt. The user must register before continuing to sign in.

Global Administrators and external users now retain Microsoft-provided SMS and voice until 1 July 2027. MC1426371 does not explain whether those users will receive the same blocking registration experience after July, but it does say that only customer-configured telecom providers will support telephony for them from that date.

There is already a documentation mismatch. Microsoft’s current retirement guidance and supporting FAQ still describe 1 February as the enforcement date for all tenants and do not mention the July exception. Until Microsoft updates those pages, use the revised Message Centre post when planning for privileged and external accounts.

Microsoft may be protecting difficult accounts from lockout

Microsoft has not said why it moved Global Administrators and external users to July. My reading is that the company is separating the accounts with the most complicated recovery and registration paths from the general population.

A failed migration for a normal user creates a support incident. The same failure for a Global Administrator can remove access to the controls needed to fix it. External users also bring a different problem, their authentication method, home tenant and resource tenant may sit under different administrative control. Microsoft’s FAQ says passkey support for B2B and internal guest users is due by the end of 2026, so enforcing the retirement against external identities in February would leave little time to deploy and test that support.

I suspect the Security Store schedule contributed too. Customers cannot select a provider until 30 October, and Microsoft has not yet published the available regions, terms or integration details. The July deadline gives Microsoft longer to establish that provider route before it withdraws its own service from privileged and external accounts. That is an inference from the revised schedule, not an explanation Microsoft has confirmed.

Run Microsoft’s SMS and voice usage analyser now, then separate Global Administrators and external identities from the rest of the results. Plan to migrate ordinary users before 1 February, and use the July extension to test privileged recovery rather than postponing the same work for five months.

Daniel

Daniel Bradley is a UK-based technical architect and Microsoft MVP in Security. He specialises in Microsoft Entra, Intune, and Microsoft Graph PowerShell and is the author of Microsoft Graph PowerShell for Administrators. He writes and edits Our Cloud Network using experience gained from working with Microsoft cloud environments.

Leave a Reply