HomeServicesManaged IT ServicesClaude DeploymentInsightsAnswersAboutContact
Identity & access

How do we roll out passkeys and passwordless sign-in in Microsoft 365?

Short answer

Enable passkeys in the Entra ID authentication methods policy, pilot with IT and admins, then register users in waves using Temporary Access Pass for onboarding. Combine passkeys in Microsoft Authenticator, security keys and Windows Hello for Business, then require phishing-resistant authentication strength in Conditional Access for admins first and everyone later.

Key facts

  • Passkeys are phishing-resistant because the credential is bound to the real sign-in site.
  • Entra ID supports device-bound passkeys in Microsoft Authenticator, FIDO2 security keys and Windows Hello for Business.
  • Temporary Access Pass lets new or locked-out users register a passkey without a password.
  • Conditional Access authentication strengths enforce which methods count for which apps or users.
  • Plan account recovery before you remove passwords and weaker MFA methods.

Why passkeys, and why now

Most account takeovers in Microsoft 365 start with a stolen password or an MFA prompt approved on a fake site. Passkeys stop both, because there is no shared secret to steal and the credential only works on the genuine Microsoft sign-in page.

Microsoft has been moving Entra ID toward passkeys as the default sign-in experience, and admin portals already require MFA. Organizations that plan the rollout now control the timing instead of reacting to default changes.

Choose your methods

MethodBest forNotes
Passkey in Microsoft AuthenticatorMost users with a company or personal phoneDevice-bound passkey on iOS or Android
FIDO2 security keyAdmins, shared or phone-free workersKeep a spare per admin; works across devices
Windows Hello for BusinessDaily sign-in on managed Windows PCsPIN or biometric tied to the device TPM
Certificate-based authenticationOrganizations with existing smart cardsPhishing-resistant; needs PKI
Authenticator push with number matchingTransition periodBetter than SMS but not phishing-resistant

Rollout plan

  • Confirm the authentication methods policy is the single place where methods are managed, and that legacy per-user MFA settings are cleaned up.
  • Enable passkeys (FIDO2) for a pilot group. Decide whether to restrict to specific authenticator models using attestation and AAGUIDs.
  • Enable Temporary Access Pass with a short lifetime so IT can onboard users and recover lost devices.
  • Deploy Windows Hello for Business through Intune for managed PCs.
  • Pilot with IT and administrators, including break-glass account testing.
  • Register users in waves by department, with a short guide and drop-in help.
  • Create a Conditional Access policy requiring phishing-resistant authentication strength for admin roles, then extend to all users and sensitive apps.
  • Remove SMS and voice as sign-in methods once registration is high, keeping a documented recovery path.

Recovery and edge cases

The hardest part of passwordless is not sign-in, it is the day someone loses their phone. Decide in advance who can issue a Temporary Access Pass, how the user proves identity, and how quickly it happens.

Plan for shared workstations, frontline staff without company phones, contractors, and staff who travel to places where phones are restricted. Security keys usually solve these cases.

Keep two break-glass accounts excluded from the passwordless policy but protected with strong credentials such as FIDO2 keys stored securely, and monitor their use.

Measuring progress

Use the authentication methods activity and registration reports in Entra ID to track who has registered a passkey and who still signs in with a password. Sign-in logs show which authentication strength was satisfied. Aim to move privileged users to phishing-resistant methods first, then high-risk groups such as finance and executives, then everyone.

How Accred Consulting approaches it

Accred Consulting begins with a review of your current authentication methods policy, Conditional Access, device estate and user groups. The proposal sets the method mix, waves, recovery process, fixed price and timeline. Our US-based specialists configure passkeys, Temporary Access Pass, Windows Hello for Business through Intune and phishing-resistant authentication strengths, then run the pilot and user waves with check-ins after each. At handover you get the policy documentation, the help desk recovery runbook and user guides, with optional support for ongoing registrations and lost devices.

Track record: 475+ client projects, 2,000+ migration workstreams and 210,000+ users migrated by a US-based team. Company facts · Case studies

Related questions

During the transition most users still have one, but they stop using it day to day. Over time you can reduce password use further. Removing passwords entirely is a later step that depends on every app and device supporting passwordless sign-in.
Entra ID has been extending support for different passkey types. Many businesses start with device-bound passkeys in Microsoft Authenticator and security keys because they are easier to control. Check the current Microsoft guidance and decide based on your risk tolerance and user base.
Passkeys and the authentication methods policy are available broadly in Entra ID. Conditional Access authentication strengths need Entra ID P1, which is included in Microsoft 365 Business Premium and E3. Windows Hello for Business deployment is easiest with Intune.
Configuration takes days. Registration is what takes time, because every user has to enroll a passkey or Windows Hello. Small organizations often finish in a few weeks; larger ones run waves over a couple of months. Help desk capacity, device mix and how fast you can remove weaker methods drive the schedule, which is set after discovery.

Want this scoped for your environment?

Book a free consultation. After discovery you get a written plan with scope, a fixed price and a timeline.

Book a free consultation