A cloud-based identity and access management service for securing user authentication and resource access
Yes. After the applicable retirement date, the blocking behavior is tied to the SMS/voice retirement enforcement, not to whether a Conditional Access policy happens to require MFA from a specific location.
For users in scope of the February 1, 2027 retirement, if their only available MFA method is SMS or voice, they are required to register a passkey during sign-in to continue accessing their account. The documentation states this prompt is blocking and that there is no opt out for users in scope of the February 1 retirement.
That means a user signing in from the corporate network is still subject to this enforcement if all of the following are true:
- The user is in the February 1, 2027 retirement scope.
- The user still relies on Microsoft-provided SMS or voice.
- The user’s only available MFA method is SMS or voice.
- No customer-managed telecom provider has been configured and the user migrated to it before the retirement date.
A few important scope details:
- February 1, 2027 applies to all users except Global Administrators and external users.
- Global Administrators and external users follow July 1, 2027 instead.
- Internal guest users still follow February 1, 2027.
If the organization needs to keep using SMS or voice after the retirement date, the supported path is to configure a customer-managed telecom provider through the Microsoft Security Store before the applicable deadline. If that is configured and affected users are migrated before the deadline, those users won’t receive the blocking passkey registration prompt as part of this retirement enforcement.
References: