Skip to content

Commit 90de605

Browse files
authored
Merge pull request #188357 from Justinha/mfa-context
Update how-to-mfa-additional-context.md
2 parents 2f71b95 + aee000c commit 90de605

File tree

2 files changed

+9
-5
lines changed

2 files changed

+9
-5
lines changed

articles/active-directory/authentication/how-to-mfa-additional-context.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to use additional context in MFA notifications
44
ms.service: active-directory
55
ms.subservice: authentication
66
ms.topic: conceptual
7-
ms.date: 12/08/2021
7+
ms.date: 02/11/2022
88
ms.author: justinha
99
author: mjsantani
1010
ms.collection: M365-identity-device-management
@@ -17,7 +17,7 @@ This topic covers how to improve the security of user sign-in by adding applicat
1717

1818
## Prerequisites
1919

20-
Your organization will need to enable Microsoft Authenticator push notifications for some users or groups using the new Authentication Methods Policy API.
20+
Your organization will need to enable Microsoft Authenticator push notifications for some users or groups using the new Authentication Methods Policy API.
2121

2222
>[!NOTE]
2323
>Additional context can be targeted to only a single group, which can be dynamic or nested. On-premises synchronized security groups and cloud-only security groups are supported for the Authentication Method Policy.
@@ -188,6 +188,10 @@ To enable additional context in the Azure AD portal, complete the following step
188188

189189
![Screenshot of enabling additional context.](media/howto-authentication-passwordless-phone/enable-additional-context.png)
190190

191+
## Known issues
192+
193+
Additional context is not supported for Network Policy Server (NPS).
194+
191195
## Next steps
192196

193197
[Authentication methods in Azure Active Directory - Microsoft Authenticator app](concept-authentication-authenticator-app.md)

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)