Skip to content

Commit c697fb7

Browse files
authored
Merge pull request #202704 from MicrosoftDocs/main
6/23 PM Publish
2 parents 2069167 + c96f270 commit c697fb7

File tree

284 files changed

+3992
-1182
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

284 files changed

+3992
-1182
lines changed

articles/active-directory-b2c/conditional-access-user-flow.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -270,11 +270,7 @@ The following template can be used to create a Conditional Access policy with di
270270

271271
## Template 3: Block locations with Conditional Access
272272

273-
With the location condition in Conditional Access, you can control access to your cloud apps based on the network location of a user. More information about the location condition in Conditional Access can be found in the article,
274-
[Using the location condition in a Conditional Access policy](../active-directory/conditional-access/location-condition.md
275-
276-
Configure Conditional Access through Azure portal or Microsoft Graph APIs to enable a Conditional Access policy blocking access to specific locations.
277-
For more information about the location condition in Conditional Access can be found in the article, [Using the location condition in a Conditional Access policy](../active-directory/conditional-access/location-condition.md)
273+
With the location condition in Conditional Access, you can control access to your cloud apps based on the network location of a user. Configure Conditional Access via the Azure portal or Microsoft Graph APIs to enable a Conditional Access policy blocking access to specific locations. For more information, see [Using the location condition in a Conditional Access policy](../active-directory/conditional-access/location-condition.md)
278274

279275
### Define locations
280276

articles/active-directory/authentication/concept-authentication-phone-options.md

Lines changed: 2 additions & 2 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: 06/09/2022
9+
ms.date: 06/23/2022
1010

1111
ms.author: justinha
1212
author: justinha
@@ -59,7 +59,7 @@ With phone call verification during SSPR or Azure AD Multi-Factor Authentication
5959
If you have problems with phone authentication for Azure AD, review the following troubleshooting steps:
6060

6161
* “You've hit our limit on verification calls” or “You’ve hit our limit on text verification codes” error messages during sign-in
62-
* Microsoft may limit repeated authentication attempts that are performed by the same user or organization in a short period of time. This limitation does not apply to the Microsoft Entra Authenticator app or verification codes. If you have hit these limits, you can use the Authenticator App, verification code or try to sign in again in a few minutes.
62+
* Microsoft may limit repeated authentication attempts that are performed by the same user or organization in a short period of time. This limitation does not apply to Microsoft Authenticator or verification codes. If you have hit these limits, you can use the Authenticator App, verification code or try to sign in again in a few minutes.
6363
* "Sorry, we're having trouble verifying your account" error message during sign-in
6464
* Microsoft may limit or block voice or SMS authentication attempts that are performed by the same user, phone number, or organization due to high number of voice or SMS authentication attempts. If you are experiencing this error, you can try another method, such as Authenticator App or verification code, or reach out to your admin for support.
6565
* Blocked caller ID on a single device.

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
11
---
2-
title: Use additional context in Microsoft Entra Authenticator notifications (Preview) - Azure Active Directory
2+
title: Use additional context in Microsoft Authenticator notifications (Preview) - Azure Active Directory
33
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: 06/08/2022
7+
ms.date: 06/23/2022
88
ms.author: justinha
99
author: mjsantani
1010
ms.collection: M365-identity-device-management
1111

1212
# Customer intent: As an identity administrator, I want to encourage users to use the Microsoft Authenticator app in Azure AD to improve and secure user sign-in events.
1313
---
14-
# How to use additional context in Microsoft Entra Authenticator app notifications (Preview) - Authentication Methods Policy
14+
# How to use additional context in Microsoft Authenticator app notifications (Preview) - Authentication Methods Policy
1515

16-
This topic covers how to improve the security of user sign-in by adding the application and location in Microsoft Entra Authenticator app push notifications.
16+
This topic covers how to improve the security of user sign-in by adding the application and location in Microsoft Authenticator app push notifications.
1717

1818
## Prerequisites
1919

@@ -182,7 +182,7 @@ To turn off additional context, you'll need to PATCH remove **displayAppInformat
182182

183183
To enable additional context in the Azure AD portal, complete the following steps:
184184

185-
1. In the Azure AD portal, click **Security** > **Authentication methods** > **Microsoft Entra Authenticator**.
185+
1. In the Azure AD portal, click **Security** > **Authentication methods** > **Microsoft Authenticator**.
186186
1. Select the target users, click the three dots on the right, and click **Configure**.
187187

188188
![Screenshot of how to configure number match.](media/howto-authentication-passwordless-phone/configure.png)
@@ -197,5 +197,5 @@ Additional context is not supported for Network Policy Server (NPS).
197197

198198
## Next steps
199199

200-
[Authentication methods in Azure Active Directory - Microsoft Entra Authenticator app](concept-authentication-authenticator-app.md)
200+
[Authentication methods in Azure Active Directory - Microsoft Authenticator app](concept-authentication-authenticator-app.md)
201201

articles/active-directory/authentication/how-to-mfa-number-match.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to use number matching in MFA notifications
44
ms.service: active-directory
55
ms.subservice: authentication
66
ms.topic: conceptual
7-
ms.date: 06/09/2022
7+
ms.date: 06/23/2022
88
ms.author: justinha
99
author: mjsantani
1010
ms.collection: M365-identity-device-management
@@ -13,7 +13,7 @@ ms.collection: M365-identity-device-management
1313
---
1414
# How to use number matching in multifactor authentication (MFA) notifications (Preview) - Authentication Methods Policy
1515

16-
This topic covers how to enable number matching in Microsoft Entra Authenticator push notifications to improve user sign-in security.
16+
This topic covers how to enable number matching in Microsoft Authenticator push notifications to improve user sign-in security.
1717

1818
>[!NOTE]
1919
>Number matching is a key security upgrade to traditional second factor notifications in the Authenticator app that will be enabled by default for all tenants a few months after general availability (GA).<br>
@@ -233,7 +233,7 @@ To turn number matching off, you will need to PATCH remove **numberMatchingRequi
233233

234234
To enable number matching in the Azure AD portal, complete the following steps:
235235

236-
1. In the Azure AD portal, click **Security** > **Authentication methods** > **Microsoft Entra Authenticator**.
236+
1. In the Azure AD portal, click **Security** > **Authentication methods** > **Microsoft Authenticator**.
237237
1. Select the target users, click the three dots on the right, and click **Configure**.
238238

239239
![Screenshot of configuring number match.](media/howto-authentication-passwordless-phone/configure.png)

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

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,24 @@
11
---
2-
title: Nudge users to set up Microsoft Entra Authenticator app - Azure Active Directory
3-
description: Learn how to move your organization away from less secure authentication methods to the Microsoft Entra Authenticator app
2+
title: Nudge users to set up Microsoft Authenticator - Azure Active Directory
3+
description: Learn how to move your organization away from less secure authentication methods to Microsoft Authenticator
44

55
services: active-directory
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: conceptual
9-
ms.date: 06/09/2022
9+
ms.date: 06/23/2022
1010

1111
ms.author: justinha
1212
author: mjsantani
1313
manager: karenhoran
1414

1515
ms.collection: M365-identity-device-management
1616

17-
# Customer intent: As an identity administrator, I want to encourage users to use the Microsoft Entra Authenticator app in Azure AD to improve and secure user sign-in events.
17+
# Customer intent: As an identity administrator, I want to encourage users to use the Microsoft Authenticator app in Azure AD to improve and secure user sign-in events.
1818
---
19-
# How to run a registration campaign to set up Microsoft Entra Authenticator - Microsoft Entra Authenticator app
19+
# How to run a registration campaign to set up Microsoft Authenticator - Microsoft Authenticator
2020

21-
You can nudge users to set up the Microsoft Entra Authenticator app during sign-in. Users will go through their regular sign-in, perform multifactor authentication as usual, and then be prompted to set up the Microsoft Entra Authenticator app. You can include or exclude users or groups to control who gets nudged to set up the app. This allows targeted campaigns to move users from less secure authentication methods to the Authenticator app.
21+
You can nudge users to set up Microsoft Authenticator during sign-in. Users will go through their regular sign-in, perform multifactor authentication as usual, and then be prompted to set up Microsoft Authenticator. You can include or exclude users or groups to control who gets nudged to set up the app. This allows targeted campaigns to move users from less secure authentication methods to the Authenticator app.
2222

2323
In addition to choosing who can be nudged, you can define how many days a user can postpone, or "snooze", the nudge. If a user taps **Not now** to snooze the app setup, they'll be nudged again on the next MFA attempt after the snooze duration has elapsed.
2424

@@ -28,7 +28,7 @@ In addition to choosing who can be nudged, you can define how many days a user c
2828
- Users can't have already set up the Authenticator app for push notifications on their account.
2929
- Admins need to enable users for the Authenticator app 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 Authenticator app and the Authentication mode set to **Any** or **Push**. If the policy is set to **Passwordless**, the user won't be eligible for the nudge. For more information about how to set the Authentication mode, see [Enable passwordless sign-in with the Microsoft Entra Authenticator app](howto-authentication-passwordless-phone.md).
31+
- Authentication Methods Policy: Users will need to be enabled for the Authenticator app and the Authentication mode set to **Any** or **Push**. If the policy is set to **Passwordless**, the user won't be eligible for the nudge. For more information about how to set the Authentication mode, see [Enable passwordless sign-in with Microsoft Authenticator](howto-authentication-passwordless-phone.md).
3232

3333
## User experience
3434

@@ -41,11 +41,11 @@ In addition to choosing who can be nudged, you can define how many days a user c
4141
1. User taps **Next** and steps through the Authenticator app setup.
4242
1. First download the app.
4343

44-
![User downloads the Microsoft Entra Authenticator app](./media/how-to-nudge-authenticator-app/download.png)
44+
![User downloads Microsoft Authenticator](./media/how-to-nudge-authenticator-app/download.png)
4545

4646
1. See how to set up the Authenticator app.
4747

48-
![User sets up the Microsoft Entra Authenticator app](./media/how-to-nudge-authenticator-app/setup.png)
48+
![User sets up Microsoft Authenticator](./media/how-to-nudge-authenticator-app/setup.png)
4949

5050
1. Scan the QR Code.
5151

@@ -308,4 +308,4 @@ It's the same as snoozing.
308308

309309
## Next steps
310310

311-
[Enable passwordless sign-in with the Microsoft Entra Authenticator app](howto-authentication-passwordless-phone.md)
311+
[Enable passwordless sign-in with Microsoft Authenticator](howto-authentication-passwordless-phone.md)

articles/active-directory/authentication/howto-authentication-passwordless-phone.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Passwordless sign-in with the Microsoft Entra Authenticator app - Azure Active Directory
3-
description: Enable passwordless sign-in to Azure AD using the Microsoft Entra Authenticator app
2+
title: Passwordless sign-in with Microsoft Authenticator - Azure Active Directory
3+
description: Enable passwordless sign-in to Azure AD using Microsoft Authenticator
44

55
services: active-directory
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: how-to
9-
ms.date: 06/15/2022
9+
ms.date: 06/23/2022
1010

1111

1212
ms.author: justinha
@@ -16,9 +16,9 @@ ms.reviewer: librown
1616

1717
ms.collection: M365-identity-device-management
1818
---
19-
# Enable passwordless sign-in with the Microsoft Entra Authenticator app
19+
# Enable passwordless sign-in with Microsoft Authenticator
2020

21-
The Microsoft Entra Authenticator app can be used to sign in to any Azure AD account without using a password. Microsoft Authenticator uses key-based authentication to enable a user credential that is tied to a device, where the device uses a PIN or biometric. [Windows Hello for Business](/windows/security/identity-protection/hello-for-business/hello-identity-verification) uses a similar technology.
21+
Microsoft Authenticator can be used to sign in to any Azure AD account without using a password. Microsoft Authenticator uses key-based authentication to enable a user credential that is tied to a device, where the device uses a PIN or biometric. [Windows Hello for Business](/windows/security/identity-protection/hello-for-business/hello-identity-verification) uses a similar technology.
2222

2323
This authentication technology can be used on any device platform, including mobile. This technology can also be used with any app or website that integrates with Microsoft Authentication Libraries.
2424

@@ -47,13 +47,13 @@ To use passwordless authentication in Azure AD, first enable the combined regist
4747

4848
### Enable passwordless phone sign-in authentication methods
4949

50-
Azure AD lets you choose which authentication methods can be used during the sign-in process. Users then register for the methods they'd like to use. The **Microsoft Entra Authenticator** authentication method policy manages both the traditional push MFA method, as well as the passwordless authentication method.
50+
Azure AD lets you choose which authentication methods can be used during the sign-in process. Users then register for the methods they'd like to use. The **Microsoft Authenticator** authentication method policy manages both the traditional push MFA method, as well as the passwordless authentication method.
5151

5252
To enable the authentication method for passwordless phone sign-in, complete the following steps:
5353

5454
1. Sign in to the [Azure portal](https://portal.azure.com) with an *authentication policy administrator* account.
5555
1. Search for and select *Azure Active Directory*, then browse to **Security** > **Authentication methods** > **Policies**.
56-
1. Under **Microsoft Entra Authenticator**, choose the following options:
56+
1. Under **Microsoft Authenticator**, choose the following options:
5757
1. **Enable** - Yes or No
5858
1. **Target** - All users or Select users
5959
1. Each added group or user is enabled by default to use Microsoft Authenticator in both passwordless and push notification modes ("Any" mode). To change this, for each row:
@@ -72,10 +72,10 @@ Users register themselves for the passwordless authentication method of Azure AD
7272
1. Sign in, then click **Add method** > **Authenticator app** > **Add** to add Microsoft Authenticator.
7373
1. Follow the instructions to install and configure the Microsoft Authenticator app on your device.
7474
1. Select **Done** to complete Authenticator configuration.
75-
1. In **Microsoft Entra Authenticator**, choose **Enable phone sign-in** from the drop-down menu for the account registered.
75+
1. In **Microsoft Authenticator**, choose **Enable phone sign-in** from the drop-down menu for the account registered.
7676
1. Follow the instructions in the app to finish registering the account for passwordless phone sign-in.
7777

78-
An organization can direct its users to sign in with their phones, without using a password. For further assistance configuring Microsoft Authenticator and enabling phone sign-in, see [Sign in to your accounts using the Microsoft Entra Authenticator app](https://support.microsoft.com/account-billing/sign-in-to-your-accounts-using-the-microsoft-authenticator-app-582bdc07-4566-4c97-a7aa-56058122714c).
78+
An organization can direct its users to sign in with their phones, without using a password. For further assistance configuring Microsoft Authenticator and enabling phone sign-in, see [Sign in to your accounts using the Microsoft Authenticator app](https://support.microsoft.com/account-billing/sign-in-to-your-accounts-using-the-microsoft-authenticator-app-582bdc07-4566-4c97-a7aa-56058122714c).
7979

8080
> [!NOTE]
8181
> Users who aren't allowed by policy to use phone sign-in are no longer able to enable it within Microsoft Authenticator.
@@ -98,7 +98,7 @@ The user is then presented with a number. The app prompts the user to authentica
9898

9999
After the user has utilized passwordless phone sign-in, the app continues to guide the user through this method. However, the user will see the option to choose another method.
100100

101-
:::image type="content" border="true" source="./media/howto-authentication-passwordless-phone/web-sign-in-microsoft-authenticator-app.png" alt-text="Example of a browser sign-in using the Microsoft Entra Authenticator app.":::
101+
:::image type="content" border="true" source="./media/howto-authentication-passwordless-phone/web-sign-in-microsoft-authenticator-app.png" alt-text="Example of a browser sign-in using Microsoft Authenticator.":::
102102

103103
## Known Issues
104104

articles/active-directory/authentication/howto-mfaserver-deploy-mobileapp.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
22
title: Azure MFA Server Mobile App Web Service - Azure Active Directory
3-
description: Configure MFA server to send push notifications to users with the Microsoft Entra Authenticator App.
3+
description: Configure MFA server to send push notifications to users with the Microsoft Authenticator App.
44

55
services: multi-factor-authentication
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: how-to
9-
ms.date: 06/09/2022
9+
ms.date: 06/23/2022
1010

1111
ms.author: justinha
1212
author: justinha
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
1717
---
1818
# Enable mobile app authentication with Azure Multi-Factor Authentication Server
1919

20-
The Microsoft Entra Authenticator app offers an additional out-of-band verification option. Instead of placing an automated phone call or SMS to the user during login, Azure Multi-Factor Authentication pushes a notification to the Authenticator app on the user's smartphone or tablet. The user simply taps **Verify** (or enters a PIN and taps "Authenticate") in the app to complete their sign-in.
20+
The Microsoft Authenticator app offers an additional out-of-band verification option. Instead of placing an automated phone call or SMS to the user during login, Azure Multi-Factor Authentication pushes a notification to the Authenticator app on the user's smartphone or tablet. The user simply taps **Verify** (or enters a PIN and taps "Authenticate") in the app to complete their sign-in.
2121

2222
Using a mobile app for two-step verification is preferred when phone reception is unreliable. If you use the app as an OATH token generator, it doesn't require any network or internet connection.
2323

0 commit comments

Comments
 (0)