Passkey Update

In an effort to enhance security, Microsoft has announced that passkeys will become the default authentication method for its Entra ID enterprise identity service starting September 2026. This change aims to provide a more secure and convenient way for users to access their accounts.

What does this mean for users?

Users who are currently using phone-based SMS and voice authentication will be automatically enabled for passkeys. The next time they perform multifactor authentication, they will be prompted to register a passkey. However, users who are already using passkeys, Windows Hello for Business, FIDO2 security keys, smart cards, or other phishing-resistant methods can continue to use these methods without any changes.

Impact on organizations

Organizations are advised to ensure that all users are using a phishing-resistant method to avoid sign-in disruptions. As of February 1, 2027, Microsoft will retire Microsoft-provided telecom delivery for SMS and voice authentication, and these methods will no longer be available as a native Microsoft Entra capability.

Preparing for the transition

Admins can use the Entra SMS/Voice Policy Scanner PowerShell script to identify users who are currently using SMS or voice authentication. Organizations that still require phone-based authentication will need to configure third-party telecom providers through the Microsoft Security Store.

Benefits of passkeys

Passkeys offer a more secure and convenient way to authenticate, reducing the risk of identity attacks and improving account security. Some of the benefits of using passkeys include:

Improved security against phishing attacks

Conclusion

Technology teams are watching passkey update closely because changes in this space often arrive faster than internal policies can adapt.

For product and engineering leaders, the practical question is how this could reshape roadmaps, vendor choices, and security reviews over the next few quarters.

Organizations that document lessons early tend to respond more calmly when similar patterns appear again.

In many companies, the first impact shows up in planning meetings: teams reassess priorities, revisit risk registers, and check whether existing tooling still fits.

Smaller businesses feel these shifts too. A single platform change or market move can affect customer trust, delivery timelines, and hiring plans.

The most resilient teams treat stories like this as input for quarterly reviews rather than one-day headlines.

If your business depends on modern software, ERP, VoIP, or customer-facing apps, staying informed helps you separate noise from decisions that require action.

Looking ahead, disciplined follow-through matters: assign owners, set review dates, and measure whether your response improved outcomes.

Security and compliance stakeholders should ask whether current controls still match the pace of change described in this update.

Operations leaders can reduce friction by translating the headline into a short internal brief with clear next steps for each department.

Customer support teams may see early signals through tickets, outages, or policy questions long before leadership reviews are scheduled.

Finance and procurement groups should note whether licensing, vendor risk, or implementation costs need revisiting after this development.

Training programs benefit from timely updates so staff understand what changed, what did not change, and what requires escalation.

Architecture reviews are a practical place to test assumptions, especially when new tools, platforms, or threats enter the conversation.

Documentation quality often determines how quickly a company recovers from surprises; capture decisions while context is still clear.