Authentication strengths
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 96655d7 · +1 −3 lines · also on GitHub
⋯ 5 unchanged lines
66
ms.service: entra-id
77
ms.subservice: authentication
88
ms.topic: conceptual
9
−ms.date: 11/16/2024
9
+ms.date: 11/18/2024
1010
1111
ms.author: justinha
1212
author: inbarckms
⋯ 94 unchanged lines
107107
For example, let's say a resource requires passkey (FIDO2) for the authentication strength, and a 1-hour sign-in frequency. 24 hours ago, a user signed in with passkey (FIDO2) to access the resource.
108108
109109
When the user unlocks their Windows device using Windows Hello for Business, they can access the resource again. Yesterday's sign-in satisfies the authentication strength requirement, and today's device unlock satisfies the sign-in frequency requirement.
110
−
111
−- **FIDO2 security key Advanced options** - Advanced options aren't supported for external users with a home tenant that is located in a different Microsoft cloud than the resource tenant.
112110
113111
- **Authentication strength blade double representation** - Platform credentials, such as Windows Hello for Business and **Platform Credential for macOS** are both represented in authentication strength under **Windows Hello For Business**. To configure a custom authentication strength that allows the use of **Platform Credential for macOS**, use **Windows Hello For Business**.
114112
⋯ 20 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 03:01 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.