Authentication registration campaigns
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit abb1ae6 · +1 −1 lines · also on GitHub
⋯ 223 unchanged lines
224224
| **AAGUID-restricted** | No | After the user registers **one eligible passkey**, the nudge is suppressed across OS and browser combinations under this profile’s rule. |
225225
| **Device-bound with attestation enforced** | No | After the user registers **one eligible passkey**, the nudge is suppressed across OS and browser combinations under this profile’s rule. |
226226
227
−An **eligible passkey** must meet the applicable profile requirements. Registering a passkey that doesn’t meet those requirements doesn’t satisfy the profile’s nudge-suppression condition. Windows Hello for Business registration behavior is separate from passkey profile restrictions.
227
+An **eligible passkey** must meet the applicable profile requirements. Registering a passkey that doesn’t meet those requirements doesn’t satisfy the profile’s nudge-suppression condition. Windows Hello for Business registration doesn’t follow passkey profile restrictions. For example, a user assigned to a synced-only passkey profile can still register Windows Hello for Business.
228228
229229
### Step 2: Evaluate the platform, when required
230230
⋯ 340 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 13 Oct 00:24 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.