Support for passkeys in Windows

• Platí pro:

  ✅ Windows 11, ✅ Windows 10

Passkeys provide a more secure and convenient method to logging into websites and applications compared to passwords. Unlike passwords, which users must remember and type, passkeys are stored as secrets on a device and can use a device's unlock mechanism (such as biometrics or a PIN). Passkeys can be used without the need for other sign-in challenges, making the authentication process faster, secure, and more convenient.

You can use passkeys with any applications or websites that support them, to create and sign in with Windows Hello. Once a passkey is created and stored with Windows Hello, you can use your device's biometrics or PIN to sign in. Alternatively, you can use a companion device (phone or tablet) to sign in.

Note

Starting in Windows 11, version 22H2 with KB5030310, Windows provides a native experience for passkey management. However, passkeys can be used in all supported versions of Windows clients.

This article describes how to create and use passkeys on Windows devices.

How passkeys work

Microsoft has long been a founding member of the FIDO Alliance and has helped to define and use passkeys natively within a platform authenticator like Windows Hello. Passkeys utilize the FIDO industry security standard, which is adopted by all major platforms. Leading technology companies like Microsoft are backing passkeys as part of the FIDO Alliance, and numerous websites and apps are integrating support for passkeys.

The FIDO protocols rely on standard public/private key cryptography techniques to offer more secure authentication. When a user registers with an online service, their client device generates a new key pair. The private key is stored securely on the user's device, while the public key is registered with the service. To authenticate, the client device must prove that it possesses the private key by signing a challenge. The private keys can only be used after they're unlocked by the user using the Windows Hello unlock factor (biometrics or PIN).

FIDO protocols prioritize user privacy, as they're designed to prevent online services from sharing information or tracking users across different services. Additionally, any biometric information used in the authentication process remains on the user's device and isn't transmitted across the network or to the service.

Passkeys compared to passwords

Passkeys have several advantages over passwords, including their ease of use and intuitive nature. Unlike passwords, passkeys are easy to create, don't need to be remembered, and don't need to be safeguarded. Additionally, passkeys are unique to each website or application, preventing their reuse. They're highly secure because they're only stored on the user's devices, with the service only storing public keys. Passkeys are designed to prevent attackers to guess or obtain them, which helps to make them resistant to phishing attempts where the attacker might try to trick the user into revealing the private key. Passkeys are enforced by the browsers or operating systems to only be used for the appropriate service, rather than relying on human verification. Finally, passkeys provide cross-device and cross-platform authentication, meaning that a passkey from one device can be used to sign in on another device.

Windows edition and licensing requirements

The following table lists the Windows editions that support passkeys:

Windows Pro	Windows Enterprise	Windows Pro Education/SE	Windows Education
Yes	Yes	Yes	Yes

Passkeys license entitlements are granted by the following licenses:

Windows Pro/Pro Education/SE	Windows Enterprise E3	Windows Enterprise E5	Windows Education A3	Windows Education A5
Yes	Yes	Yes	Yes	Yes

For more information about Windows licensing, see Windows licensing overview.

User experiences

Create a passkey

By default, Windows offers to save the passkey locally on the Windows device, in which case the passkey is protected by Windows Hello (biometrics and PIN). You can also choose to save the passkey in one of the following locations:

• iPhone, iPad or Android device: the passkey is saved on a phone or tablet, protected by the device's biometrics, if offered by the device. This option requires you to scan a QR code with your phone or tablet, which must be in proximity of the Windows device
• Linked device: the passkey is saved on a phone or tablet, protected by the device's biometrics, if offered by the device. This option requires the linked device to be in proximity of the Windows device, and it's only supported for Android devices
• Security key: the passkey is saved to a FIDO2 security key, protected by the key's unlock mechanism (for example, biometrics or PIN)

Pick one of the following options to learn how to save a passkey, based on where you want to store it.

Windows device

1. Open a website or app that supports passkeys

2. Create a passkey from your account settings

3. Select the option Use another device > Next

4. Select This Windows device > Next

5. Select a Windows Hello verification method and proceed with the verification, then select OK

6. The passkey is saved to your Windows device. To confirm select OK

New phone or tablet

1. Open a website or app that supports passkeys

2. Create a passkey from your account settings

3. Select the option Use another device > Next

4. Select iPhone, iPad or Android device > Next

5. Scan the QR code with your phone or tablet. Wait for the connection to the device to be established and follow the instructions to save the passkey

6. Once the passkey is saved to your phone or tablet, select OK

Linked phone or tablet

1. Open a website or app that supports passkeys

2. Create a passkey from your account settings

3. Select the option Use another device > Next

4. Select your linked device name (for example, Pixel) > Next

5. Once the connection to the linked device is established, follow the instructions on the device to save the passkey

6. Once the passkey is saved to your linked device, select OK

Security key

1. Open a website or app that supports passkeys

2. Create a passkey from your account settings

3. Select the option Use another device > Next

4. Select Security key > Next

5. Select OK to confirm that you want to set up a security key, and unlock the security key using the key's unlock mechanism

6. Once the passkey is saved to the security key, select OK

Use a passkey

When you open a website or app that supports passkeys, if a passkey is stored locally, you're automatically prompted to use Windows Hello to sign in. You can also choose to use a passkey from one of the following locations:

• iPhone, iPad or Android device: use this option if you want to sign in with a passkey stored on a phone or tablet. This option requires you to scan a QR code with your phone or tablet, which must be in proximity of the Windows device
• Linked device: use this option if you want to sign in with a passkey stored on a device that is in proximity of the Windows device. This option is only supported for Android devices
• Security key: use this option if you want to sign in with a passkey stored on a FIDO2 security key

Pick one of the following options to learn how to use a passkey, based on where you saved it.

Windows device

1. Open a website or app that supports passkeys

2. Select Sign in with a passkey, or a similar option

3. Select the option Use another device > Next

4. Select This Windows device > Next

5. Select a Windows Hello unlock option

6. Select OK to continue signing in

Phone or tablet

1. Open a website or app that supports passkeys

2. Select Sign in with a passkey, or a similar option

3. Select the option Use another device > Next

4. Select iPhone, iPad or Android device > Next

5. Scan the QR code with your phone or tablet where you saved the passkey. Once the connection to the device is established, follow the instructions to use the passkey

6. You're signed in to the website or app

Linked phone or tablet

1. Open a website or app that supports passkeys

2. Select Sign in with a passkey, or a similar option

3. Select the option Use another device > Next

4. Select your linked device name (for example, Pixel) > Next

5. Once the connection to the linked device is established, follow the instructions on the device to use the passkey

6. You're signed in to the website or app

Security key

1. Open a website or app that supports passkeys

2. Select Sign in with a passkey, or a similar option

3. Select the option Use another device > Next

4. Select Security key > Next

5. Unlock the security key using the key's unlock mechanism

6. You're signed in to the website or app

Manage passkeys

Starting in Windows 11, version 22H2 with KB5030310, you can use the Settings app to view and manage passkeys saved for apps or websites. Go to Settings > Accounts > Passkeys, or use the following shortcut:

Manage passkeys

• A list of saved passkeys is displayed and you can filter them by name
• To delete a passkey, select ... > Delete passkey next to the passkey name

Note

Some passkeys for login.microsoft.com can't be deleted, as they're used with Microsoft Entra ID and/or Microsoft Account for signing in to the device and Microsoft services.

Passkeys in Bluetooth-restricted environments

For passkey cross-device authentication scenarios, both the Windows device and the mobile device must have Bluetooth enabled and connected to the Internet. This allows the user to authorize another device securely over Bluetooth without transferring or copying the passkey itself.

Some organizations restrict Bluetooth usage, which includes the use of passkeys. In such cases, organizations can allow passkeys by permitting Bluetooth pairing exclusively with passkey-enabled FIDO2 authenticators.

To limit the use of Bluetooth to only passkey use cases, use the Bluetooth Policy CSP and the DeviceInstallation Policy CSP.

Device configuration

The following instructions provide details about how to configure your devices. Select the option that best suits your needs.

Intune/CSP

To configure devices with Microsoft Intune, you can use a custom policy with these settings:

Setting
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Bluetooth/AllowAdvertising Data type: Integer Value: 0 When set to 0, the device doesn't send out advertisements.
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Bluetooth/AllowDiscoverableMode Data type: Integer Value: 0 When set to 0, other devices can't detect the device.
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Bluetooth/AllowPrepairing Data type: Integer Value: 0 Prevents specific bundled Bluetooth peripherals from automatically pairing with the host device.
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Bluetooth/AllowPromptedProximalConnections Data type: Integer Value: 0 Prevents users from using Swift Pair and other proximity-based scenarios.
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Bluetooth/ServicesAllowedList Data type: String Value: {0000FFFD-0000-1000-8000-00805F9B34FB};{0000FFF9-0000-1000-8000-00805F9B34FB} Set a list of allowable Bluetooth services and profiles: - FIDO Alliance Universal Second Factor Authenticator service (0000fffd-0000-1000-8000-00805f9b34fb) - FIDO2 secure client-to-authenticator transport service (0000FFF9-0000-1000-8000-00805F9B34FB) For more information, see FIDO CTAP 2.1 standard specification and Bluetooth Assigned Numbers document.
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceIDs Data type: String Value: <enabled/><data id="DeviceInstall_IDs_Deny_Retroactive" value="true"/><data id="DeviceInstall_IDs_Deny_List" value="1&#xF000;BTH\MS_BTHPAN"/> Disables the existing Bluetooth Personal Area Network (PAN) network adapter, preventing the installation of the Bluetooth Network Adapter that can be used for network connectivity or tethering.

PowerShell

Configure your devices using PowerShell scripts via the MDM Bridge WMI Provider.

Important

For all device settings, the WMI Bridge client must be executed as SYSTEM (LocalSystem) account.

To test the PowerShell script, you can:

1. Download the psexec tool
2. Open an elevated command prompt and run: psexec.exe -i -s powershell.exe
3. Run the script in the PowerShell session

# Bluetooth configuration
$namespaceName = "root\cimv2\mdm\dmmap"
$className = "MDM_Policy_Config01_Bluetooth02"
New-CimInstance -Namespace $namespaceName -ClassName $className -Property @{
    ParentID="./Vendor/MSFT/Policy/Config";
    InstanceID="Bluetooth";
    AllowDiscoverableMode=0;
    AllowAdvertising=0;
    AllowPrepairing=0;
    AllowPromptedProximalConnections=0;
    ServicesAllowedList="{0000FFF9-0000-1000-8000-00805F9B34FB};{0000FFFD-0000-1000-8000-00805F9B34FB}"
}


# Device installation configuration
$namespaceName = "root\cimv2\mdm\dmmap"
$className = "MDM_Policy_Config01_DeviceInstallation02"
New-CimInstance -Namespace $namespaceName -ClassName $className -Property @{
    ParentID="./Vendor/MSFT/Policy/Config";
    InstanceID="DeviceInstallation";
    PreventInstallationOfMatchingDeviceIDs='<![CDATA[<Enabled/><Data id="DeviceInstall_IDs_Deny_List" value="1&#xF000;BTH\MS_BTHPAN"/><Data id="DeviceInstall_IDs_Deny_Retroactive" value="true"/>]]>'
}

For more information, see Use PowerShell scripting with the WMI Bridge Provider.

Note

Once the settings are applied, if you try to pair a device via Bluetooth, it will initially pair and immediately disconnect. The Bluetooth device is blocked from loading and not available from Settings nor Device Manager.

Provide feedback

To provide feedback for passkeys, open Feedback Hub and use the category Security and Privacy > Passkey.