Skip to content

Commit 86ef3e3

Browse files
authored
Merge pull request #197304 from MicrosoftDocs/main
5/05 PM Publish
2 parents 83c0080 + 5e94691 commit 86ef3e3

File tree

160 files changed

+2228
-634
lines changed

Some content is hidden

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

160 files changed

+2228
-634
lines changed

articles/active-directory/authentication/how-to-mfa-registration-campaign.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: 03/22/2022
9+
ms.date: 05/05/2022
1010

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

6464
![Installation complete](./media/how-to-nudge-authenticator-app/finish.png)
6565

66-
1. If a user wishes to not install the Authenticator app, they can tap **Not now** to snooze the prompt for a number of days, which can be defined by an admin.
66+
1. If a user wishes to not install Microsoft Authenticator, they can tap **Not now** to snooze the prompt for up to 14 days, which can be set by an admin.
6767

6868
![Snooze installation](./media/how-to-nudge-authenticator-app/snooze.png)
6969

articles/active-directory/authentication/howto-sspr-deployment.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: 02/02/2022
9+
ms.date: 05/05/2022
1010

1111
ms.author: justinha
1212
author: gargi-sinha
@@ -257,7 +257,7 @@ To enable your support team's success, you can create a FAQ based on questions y
257257
| User isn't receiving a text or call on their office or cell phone| A user is trying to verify their identity via text or call but isn't receiving a text/call. |
258258
| User can't access the password reset portal| A user wants to reset their password but isn't enabled for password reset and can't access the page to update passwords. |
259259
| User can't set a new password| A user completes verification during the password reset flow but can't set a new password. |
260-
| User doesn't see a Reset Password link on a Windows 10 device| A user is trying to reset password from the Windows 10 lock screen, but the device is either not joined to Azure AD, or the Intune device policy isn't enabled |
260+
| User doesn't see a Reset Password link on a Windows 10 device| A user is trying to reset password from the Windows 10 lock screen, but the device is either not joined to Azure AD, or the Microsoft Endpoint Manager device policy isn't enabled |
261261

262262
### Plan rollback
263263

articles/active-directory/authentication/howto-sspr-windows.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -71,13 +71,13 @@ To configure a Windows 10 device for SSPR at the sign-in screen, review the foll
7171
- Azure AD joined
7272
- Hybrid Azure AD joined
7373

74-
### Enable for Windows 10 using Intune
74+
### Enable for Windows 10 using Microsoft Endpoint Manager
7575

76-
Deploying the configuration change to enable SSPR from the login screen using Intune is the most flexible method. Intune allows you to deploy the configuration change to a specific group of machines you define. This method requires Intune enrollment of the device.
76+
Deploying the configuration change to enable SSPR from the login screen using Microsoft Endpoint Manager is the most flexible method. Microsoft Endpoint Manager allows you to deploy the configuration change to a specific group of machines you define. This method requires Microsoft Endpoint Manager enrollment of the device.
7777

78-
#### Create a device configuration policy in Intune
78+
#### Create a device configuration policy in Microsoft Endpoint Manager
7979

80-
1. Sign in to the [Azure portal](https://portal.azure.com) and select **Intune**.
80+
1. Sign in to the [Azure portal](https://portal.azure.com) and select **Endpoint Manager**.
8181
1. Create a new device configuration profile by going to **Device configuration** > **Profiles**, then select **+ Create Profile**
8282
- For **Platform** choose *Windows 10 and later*
8383
- For **Profile type**, choose *Custom*
@@ -94,7 +94,7 @@ Deploying the configuration change to enable SSPR from the login screen using In
9494
Select **Add**, then **Next**.
9595
1. The policy can be assigned to specific users, devices, or groups. Assign the profile as desired for your environment, ideally to a test group of devices first, then select **Next**.
9696

97-
For more information, see [Assign user and device profiles in Microsoft Intune](/mem/intune/configuration/device-profile-assign).
97+
For more information, see [Assign user and device profiles in Microsoft Microsoft Endpoint Manager](/mem/intune/configuration/device-profile-assign).
9898

9999
1. Configure applicability rules as desired for your environment, such as to *Assign profile if OS edition is Windows 10 Enterprise*, then select **Next**.
100100
1. Review your profile, then select **Create**.
Loading

articles/active-directory/reports-monitoring/reference-basic-info-sign-in-logs.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.topic: reference
1313
ms.tgt_pltfrm: na
1414
ms.workload: identity
1515
ms.subservice: report-monitor
16-
ms.date: 05/02/2022
16+
ms.date: 05/05/2022
1717
ms.author: markvi
1818
ms.reviewer: besiler
1919

@@ -35,7 +35,7 @@ In Azure AD, a resource access has three relevant components:
3535
- **What** – The target (Resource) accessed by the identity.
3636

3737

38-
Each component has an associated unique identifier (ID). Below is an example of user using the Windows Azure classic deployment model to access the Azure portal.
38+
Each component has an associated unique identifier (ID). Below is an example of user using the Microsoft Azure classic deployment model to access the Azure portal.
3939

4040
![Open audit logs](./media/reference-basic-info-sign-in-logs/sign-in-details-basic-info.png)
4141

@@ -47,6 +47,7 @@ The sign-in log tracks two tenant identifiers:
4747
- **Resource tenant** – The tenant that owns the (target) resource.
4848

4949
These identifiers are relevant in cross-tenant scenarios. For example, to find out how users outside your tenant are accessing your resources, select all entries where the home tenant doesn’t match the resource tenant.
50+
For the home tenant, Azure AD tracks the ID and the name.
5051

5152
### Request ID
5253

articles/active-directory/saas-apps/cyberark-saml-authentication-tutorial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -115,11 +115,11 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
115115

116116
## Configure CyberArk SAML Authentication SSO
117117

118-
To configure single sign-on on **CyberArk SAML Authentication** side, you need to send the downloaded **Certificate (Base64)** and appropriate copied URLs from Azure portal to [CyberArk SAML Authentication support team](mailto:bizdevtech@cyberark.com). They set this setting to have the SAML SSO connection set properly on both sides.
118+
To configure single sign-on on **CyberArk SAML Authentication** side, you need to send the downloaded **Certificate (Base64)** and appropriate copied URLs from Azure portal to [CyberArk SAML Authentication support team](mailto:support@cyberark.com). They set this setting to have the SAML SSO connection set properly on both sides.
119119

120120
### Create CyberArk SAML Authentication test user
121121

122-
In this section, you create a user called B.Simon in CyberArk SAML Authentication. Work with [CyberArk SAML Authentication support team](mailto:bizdevtech@cyberark.com) to add the users in the CyberArk SAML Authentication platform. Users must be created and activated before you use single sign-on.
122+
In this section, you create a user called B.Simon in CyberArk SAML Authentication. Work with [CyberArk SAML Authentication support team](mailto:support@cyberark.com) to add the users in the CyberArk SAML Authentication platform. Users must be created and activated before you use single sign-on.
123123

124124
## Test SSO
125125

46.1 KB
Loading
44.9 KB
Loading

0 commit comments

Comments
 (0)