Microsoft 365 passkeys: secure enrolment, recovery and fallback
16 October 2026
Secure Microsoft 365 passkeys with practical checks for enrolment, lost devices, fallback sign-in methods and helpdesk identity verification.
Passkeys make fake sign-in pages much less useful to attackers, but they do not secure every route into an account. Huntress’s discussion of passkey attack paths highlights risks around registration, recovery, compromised devices and alternative authentication flows.
For Australian businesses deploying Microsoft 365 passkeys, the practical question is whether those surrounding processes are equally well controlled. This checklist uses Microsoft’s documentation as the authority for supported controls, rather than treating the Huntress article as a Microsoft product announcement.
Microsoft 365 passkeys: distinguish availability from enforcement
A passkey uses cryptographic credentials tied to the legitimate service. Unlike a password or one-time code, it cannot simply be entered into a lookalike website and relayed as the same credential. That is a substantial improvement, not a reason to remove other security controls.
However, allowing staff to register passkeys is different from requiring phishing-resistant authentication for access.
Microsoft documents these as separate controls: the passkey authentication method policy governs availability and configuration, while Conditional Access authentication strengths govern which authentication combinations satisfy access requirements.
Check the following before rollout:
- Identify the users, applications and administrative roles in scope.
- Confirm supported passkey types, devices, operating systems and browsers against Microsoft’s current documentation.
- Check your licences. Conditional Access generally requires Microsoft Entra ID P1; risk-based policies require P2.
- Review whether existing policies require generic multifactor authentication or a phishing-resistant authentication strength.
- Identify exclusions, guest access and applications outside the intended policy scope.
The built-in phishing-resistant strength is not a passkey-only setting. It also supports other qualifying methods. Review the allowed combinations rather than relying on the policy name.
Protect enrolment before issuing credentials
A correctly functioning passkey can still belong to an attacker if that attacker succeeds in registering it against someone else’s account. Treat enrolment as an identity-sensitive change, not a routine device setup task.
For Microsoft 365 passkeys, document both the first registration process and the process for adding another credential later.
- Confirm the person: for new starters, use an established onboarding process involving the authorised manager and verified employment records.
- Control the bootstrap method: Microsoft supports a Temporary Access Pass, or TAP, for supported onboarding and recovery scenarios. Set a short lifetime and use one-time use where the workflow supports it.
- Protect delivery: do not send bootstrap credentials to a new phone number or email address supplied in the same unverified request.
- Review registration access: Microsoft provides a Conditional Access user action for registering security information. Test the conditions carefully so legitimate first-time registration remains possible.
- Record the change: capture who approved registration, who issued temporary access and which authentication methods were added.
A TAP is a sensitive credential, not proof of identity. Its issuance process must be harder to manipulate than an ordinary password reset.
Rehearse lost-device recovery
Recovery is where security policies often become informal. A staff member is travelling, cannot sign in and needs access immediately. Without a rehearsed process, the helpdesk may improvise a weaker route.
Write a recovery procedure for Microsoft 365 passkeys that covers lost phones, missing security keys, damaged devices and suspected theft.
- Verify identity independently. Use approved records and a separate verification channel before changing authentication methods.
- Establish what was lost. Determine whether the device held a passkey, an active session, business data or several of these.
- Remove affected credentials. Review the account’s registered authentication methods and remove the lost or compromised method where appropriate. Do not assume deleting a device record performs every necessary revocation.
- Contain session and device exposure. Revoke sessions and use supported device lock or wipe actions where warranted. These controls have different effects and should not be treated as interchangeable.
- Restore access through a controlled method. Use a separately held, approved credential or an authorised temporary bootstrap process.
- Confirm recovery is complete. Check the replacement method, temporary access expiry and recent sign-in activity.
Where supported and appropriate, a second registered credential stored separately can reduce pressure to bypass controls. Test recovery with an ordinary user and an administrator before relying on it.
Check every fallback route
A user can prefer a passkey while still retaining weaker ways to satisfy access requirements elsewhere. Review what policies actually allow, not just which method appears first on the sign-in screen.
For Microsoft 365 passkeys, build a simple access matrix: user group, application, permitted methods, required authentication strength and any exception.
- Check whether password plus SMS, voice or push approval can still satisfy policies protecting sensitive applications.
- Review self-service password reset methods separately from sign-in requirements.
- Check legacy authentication exposure. Older protocols may not support modern authentication requirements.
- Review guest and external-user access rather than assuming employee settings apply identically.
- Identify app passwords, service accounts and non-interactive integrations. These need separate controls rather than a forced passkey rollout.
- Test emergency access without creating an undocumented everyday bypass.
Microsoft’s emergency access account guidance explains how to plan for administrative lockout. Maintain strong authentication, monitoring and regular testing for these accounts.
Use Conditional Access report-only mode and sign-in logs to assess likely impact before enforcement. Then test successful and denied access with pilot accounts. Our Microsoft 365 hardening checklist provides a broader framework for prioritising these changes.
Give the helpdesk a repeatable identity-check procedure
Attackers do not need to defeat cryptography if they can persuade support staff to issue new access. Caller ID, a familiar voice, an email signature or knowledge of a manager’s name is not sufficient identity evidence.
Require a consistent procedure for authentication resets:
- Open a ticket and record exactly what access change is requested.
- Contact the requester through a pre-established channel taken from trusted records, not details supplied during the request.
- Use additional verification when the requester has lost access to that channel.
- Require separate authorisation for privileged accounts and high-risk exceptions.
- Restrict authentication administration to appropriate roles rather than granting broad administrative access.
- Log temporary credential issuance, method removal and new enrolment.
A manager’s approval helps establish business authorisation, but does not by itself prove who is making the request. Define a stop-and-escalate path when identity cannot be established, including after-hours requests.
Keep endpoints and sessions in scope
Microsoft 365 passkeys protect authentication; they do not make an infected computer safe. Malware operating within an authenticated session may still access information or perform actions without repeating the original sign-in.
Keep endpoint protection, patching, browser controls and device compliance in the same security plan. Where licensing and platform support permit, evaluate Conditional Access requirements for compliant devices alongside authentication strength.
Monitor authentication-method changes, unusual sign-ins and activity after recovery. Investigate unfamiliar application consent and token-related access as separate issues; our OAuth token theft checks explain why a stronger sign-in method is only one part of identity protection.
The rollout is ready when staff can enrol safely, recover access without improvisation and demonstrate that weaker routes do not undermine the intended policy.
Tech Engine can help review your cyber security and configure, secure and manage Microsoft 365, including authentication policies, recovery procedures and helpdesk access controls. Contact sales@techengine.au or call 1300 088 324 to review your current setup.
Want this applied to your business?
Request an AI Blueprint and we will map the processes worth automating first.
Request an AI Blueprint