
Microsoft 365
Entra Passkey Migration: The Default Problem
On 1 September 2026 Entra put SMS and voice users into a passkey profile with attestation off. What it costs you, and the runbook change it forces.
By Paul Bentley16 min read
On this page
- The credential that survives your remediation
- What Entra changed on 1 September
- The five-minute rule that looks like a control
- What attestation refuses, and what key restrictions add
- Why the permissive default is not carelessness
- Tightening attestation afterwards does not undo anything
- What your logs will and will not tell you
- What to change now
- What is verified, and what is not
Here is the procedure. A user reports a phish, or your tooling catches one. You reset the password, revoke the sessions, and close the ticket. It has been the correct sequence for a decade, and it is what almost every account-compromise runbook still says.
There is now a credible technique it does not cover, and on 1 September Microsoft made the conditions for it a great deal more common across every tenant still using SMS or voice. The technique is claimed rather than captured, and I will be precise at the end about how much weight that supports. What matters more is what your own tenant would do about it, because that part is documented and has a date attached.