Authentication registration campaigns
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit fa394f2 · +5 −5 lines · also on GitHub
⋯ 5 unchanged lines
66
author: justinha
77
ms.reviewer: marisanchez
88
ai-usage: ai-assisted
9
−ms.custom: sfi-ga-nochange, sfi-image-nochange, msecd-doc-authoring-108
9
+ms.custom: sfi-ga-nochange, sfi-image-nochange, msecd-doc-authoring-1012
1010
#Customer intent: As an identity administrator, I want to encourage users to set up a passkey or Microsoft Authenticator in Microsoft Entra ID to improve and secure user sign-in events.
1111
---
1212
⋯ 17 unchanged lines
3030
3131
## Prerequisites
3232
33
−- If you want to know the number of users who registered each authentication method before you configure the registration campaign, see [the Authentication methods activity report](howto-authentication-methods-activity.md#registration-details).
33
+- If you want to know the number of users who registered each authentication method before you configure the registration campaign, see [Authentication methods activity report](howto-authentication-methods-activity.md#registration-details).
3434
- Your organization must enable Microsoft Entra multifactor authentication. The registration campaign has no license requirements.
3535
- **For Authenticator campaigns**: Users can't already have the Authenticator app set up for push notifications on their account. Enable users for the Authenticator app in the Authentication methods policy. The **Authentication mode** must be set to **Any** or **Push**. If the mode is set to **Passwordless**, users aren't eligible for the nudge. For more information, see [Enable passwordless sign-in with Microsoft Authenticator](howto-authentication-passwordless-phone.md).
3636
- **For passkey campaigns**: The passkey (FIDO2) authentication method must be enabled in the Authentication methods policy. In addition, the **Allow self-service setup** toggle must be enabled in the passkey (FIDO2) method configuration. For more information, see [Enable passkeys](how-to-enable-passkey-fido2.md).
⋯ 282 unchanged lines
319319
## Limitations
320320
321321
> [!IMPORTANT]
322
−> The passkey nudge is evaluated on a per-user basis. When a user signs in and is scoped into the registration campaign, their passkey profile is checked for restrictions. If the user's passkey profile has any of the following restrictions, they don't see a nudge upon MFA completion:
322
+> The passkey nudge is evaluated on a per-user basis under Microsoft managed mode. When a user signs in and is scoped into the registration campaign, their passkey profile is checked for restrictions. If the user's passkey profile has any of the following restrictions, they don't see a nudge upon MFA completion:
323323
>
324324
> - Synced only
325325
> - Device-bound only
⋯ 18 unchanged lines
344344
| Any non-platform provider (such as security keys or authenticator apps) | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
345345
346346
> [!NOTE]
347
−> - **Linux**: Users aren't nudged. FIDO2 passkeys aren't available on Linux.
347
+> **Linux**: Users aren't nudged. FIDO2 passkeys aren't available on Linux.
348348
349349
## Frequently asked questions
350350
⋯ 55 unchanged lines
406406
407407
**Will Guest/B2B users in my tenant be nudged?**
408408
409
−Yes. If they have been scoped for the nudge using the policy.
409
+Yes, if they're included in the registration campaign policy.
410410
411411
**What if the user closes the browser?**
412412
⋯ 23 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 9 Oct 21:34 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.