Security

Microsoft Entra ID Passkeys Default Rollout Dates

3 min read

Summary

Microsoft will make passkeys the default authentication experience in Entra ID starting September 1, 2026, automatically prompting users currently using SMS or voice MFA to register a passkey. The change matters because Microsoft-provided SMS and voice authentication will be retired on February 1, 2027, pushing organizations toward phishing-resistant authentication and requiring admins to plan migrations now.

Need help with Security?Talk to an Expert

Introduction

Microsoft is accelerating its move to phishing-resistant authentication in Entra ID. As AI-driven phishing and identity attacks become more effective, Microsoft is making passkeys the default sign-in experience to reduce dependence on weaker methods like SMS and voice.

For IT teams, this is more than a user experience update. It introduces a firm migration timeline, changes how MFA is delivered, and requires planning for any users who still depend on telecom-based authentication.

What’s new

Passkeys become the default

  • Starting September 1, 2026, Microsoft will roll out passkeys as the default authentication experience in Microsoft Entra ID.
  • Users currently enabled for SMS or voice authentication will be automatically enabled for passkeys.
  • On their next MFA prompt, those users will be asked to register a passkey.

Microsoft-provided SMS and voice are being retired

  • February 1, 2027: Microsoft will end its native telecom delivery for SMS and voice authentication in Entra ID.
  • After that date, organizations that still need SMS or voice must use a supported telecom partner through the Microsoft Security Store.
  • Those organizations will be responsible for any related telecom costs.

Key support dates

  • September 18, 2026: Microsoft will publish supported providers, pricing details, and deployment guidance.
  • October 30, 2026: Admins can begin selecting and configuring a telecom provider if SMS or voice must remain in use.
  • After February 1, 2027: Users relying on SMS or voice will be required to register a passkey before signing in, with no opt-out.

Impact on administrators and users

For administrators, this means reviewing authentication method policies now and identifying users or groups still tied to SMS or voice. Organizations should also decide which passkey types best fit their environment, including synced passkeys, device-bound passkeys, Microsoft Authenticator passkeys, Windows passkeys, or FIDO2 security keys.

For end users, the biggest visible change will be a registration prompt during MFA. In most environments, passkeys should improve both security and sign-in speed, but user communication and onboarding will be important to avoid confusion.

  • Audit which users still use SMS or voice MFA.
  • Enable and test passkey deployment in Entra ID.
  • Use the registration campaign feature to drive adoption.
  • Prepare user communications about the new sign-in prompt.
  • If SMS or voice must remain for regulatory or operational reasons, evaluate telecom partner options as soon as Microsoft publishes them.

This update makes Microsoft’s direction clear: phishing-resistant authentication is becoming the standard, and Entra ID admins should begin the transition well before the 2027 cutoff.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Entra IDpasskeysMFAauthenticationsecurity

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.