Colour theme
Book a consultation

Introducing passkeys at work

Pilot passkeys with supported services, choose how credentials are stored and test recovery and staff departures before changing sign-in requirements.

Person typing on a laptop at a table.

Passkeys can reduce the risk of staff entering a reusable password into a fake sign-in page. They also change how credentials are stored and recovered, so introducing them needs more planning than turning on a setting.

Start with the services and devices your staff use. Decide which passkey methods the business will allow and test a small rollout before requiring those methods across the organization.

Understand what the sign-in does

A passkey uses a cryptographic key pair. The service stores a public key, and an authenticator uses the private key to answer a sign-in challenge. The user confirms it with the device’s usual unlock method, such as a PIN or biometric.

FIDO’s specifications overview explains that the credential is bound to the service’s domain. This is what makes it resist a fake website collecting a password. Biometric verification happens on the device; the website doesn’t receive a fingerprint or face scan.

Passkeys don’t prevent every account attack. A compromised device, stolen session or weak recovery route can still create problems. Keep device security and account-response procedures in place.

Choose where work credentials may be stored

There are different passkey storage models. FIDO’s enterprise introduction distinguishes synced passkeys from device-bound credentials. Synced passkey material can be copied through the provider’s service to other devices signed in to the same provider account. A device-bound credential stays on its authenticator, such as a compatible security key.

Decide which providers and device types are permitted for business accounts. Consider who controls the provider account, how its recovery works and how you remove work access when a person leaves.

A staff member’s personal cloud account may not be a suitable place for a business credential. Make that decision alongside your BYOD and account-access policies. Don’t collect employees’ personal account passwords as a workaround.

Confirm support in your own environment

Microsoft Entra’s passkey configuration guidance covers prerequisites, permitted methods and administrative settings. Have IT verify those settings in your tenant, together with the applications, browsers and devices staff use.

Some older tools or sign-in flows may not support the chosen method. Test remote work, mobile access, shared workstations and specialist applications. Check required licences and any hardware costs before approving the rollout.

Registering a passkey doesn’t necessarily disable passwords or weaker fallbacks. Decide which authentication methods each application will accept and when any policy change is safe to make.

Plan recovery before requiring the method

Test what happens when a phone is lost, a security key fails or someone changes devices. Provide a backup authenticator of a permitted type or a documented recovery path, with stricter checks for higher-risk accounts.

Have the help desk verify identity before resetting access. Don’t let an urgent phone call bypass that step. Protect recovery and administrative access with the same care as everyday sign-in.

When someone leaves, remove their work access and registered credentials through the account-management process. Don’t rely on recovering their personal phone or deleting a synced copy you may not control.

Pilot with the people who use the systems

Choose a small group that includes an administrator, a frequent mobile user and someone using your important business applications. Train them to start sign-ins by going to the service directly and to report unexpected prompts.

Passkeys can support sign-in between devices, including QR-based flows. Explain that difference so staff don’t trust every QR code or treat every QR sign-in as a scam.

The Cyber Centre’s phishing-resistant MFA guidance identifies FIDO2 methods among the options for resisting intercepted sign-ins. Ordinary one-time codes and number-matching approval prompts don’t provide the same protection.

Record successful sign-ins, failures, recovery tests and remaining application exceptions. Expand the rollout once staff can complete their normal work and support can recover access safely.


Featured Image Credit