Passkeys in Microsoft Authenticator
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit b1ac236 · +6 −2 lines · also on GitHub
11
---
22
title: Enable passkeys in Authenticator for Microsoft Entra ID
33
description: Learn about how to enable passkeys in Microsoft Authenticator for Microsoft Entra ID.
4
+ms.service: entra-id
5
+ms.subservice: authentication
46
ms.topic: how-to
57
ms.date: 01/27/2026
8
+ms.author: justinha
9
+author: justinha
10
+manager: dougeby
611
ms.reviewer: mjsantani
712
ms.custom: sfi-ga-nochange, sfi-image-nochange
813
# Customer intent: As a Microsoft Entra administrator, I want to learn how to enable and enforce passkeys in Microsoft Authenticator sign-in for users.
⋯ 10 unchanged lines
1924
- Make sure that Bluetooth and an active internet connection are enabled on both devices.
2025
If your organization restricts Bluetooth usage, you can [permit Bluetooth pairing exclusively with passkey-enabled FIDO2 authenticators](/windows/security/identity-protection/passkeys/?tabs=windows%2Cintune#passkeys-in-bluetooth-restricted-environments) to allow cross-device passkey sign-in and registration.
2126
Your organization needs to allow connectivity to endpoints in the following table to enable cross-device registration and authentication.
22
− Devices must be allowed to reach these URLs without interception.
23
− They need to be excluded from network proxies, interception, and other enterprise systems.
27
+ Devices must be allowed to reach these URLs. For more information about requirements for Apple devices, see [Use Apple products on enterprise networks](https://support.apple.com/101555).
2428
2529
Platform | URL
2630
---------|----
⋯ 128 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 02:15 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.