Skip to content

Commit aee000c

Browse files
committed
Update how-to-mfa-registration-campaign.md
1 parent 3bb51a2 commit aee000c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/active-directory/authentication/how-to-mfa-registration-campaign.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: conceptual
9-
ms.date: 12/15/2021
9+
ms.date: 02/11/2022
1010

1111
ms.author: justinha
1212
author: mjsantani
@@ -24,11 +24,11 @@ In addition to choosing who can be nudged, you can define how many days a user c
2424

2525
## Prerequisites
2626

27-
- Your organization must have enabled Azure MFA.
27+
- Your organization must have enabled Azure MFA. Every edition of Azure AD includes Azure MFA. No additional license is needed for a registration campaign.
2828
- User must not have already set up Microsoft Authenticator for push notifications on their account.
2929
- Admins need to enable users for Microsoft Authenticator using one of these policies:
3030
- MFA Registration Policy: Users will need to be enabled for **Notification through mobile app**.
31-
- Authentication Methods Policy: Users will need to be enabled for the Microsoft Authenticator and the Authentication mode set to **Any** or **Push**. If the policy is set to **Passwordless**, the user will not be eligible for the nudge.
31+
- Authentication Methods Policy: Users will need to be enabled for the Microsoft Authenticator and the Authentication mode set to **Any** or **Push**. If the policy is set to **Passwordless**, the user will not be eligible for the nudge. For more information about how to set the Authentication mode, see [Enable passwordless sign-in with the Microsoft Authenticator app](howto-authentication-passwordless-phone.md).
3232

3333
## User experience
3434

0 commit comments

Comments
 (0)