Merge pull request #48555 from MicrosoftDocs/master

8/8 PM Publish

Author: huypub

.openpublishing.redirection.json

@@ -102,7 +102,7 @@ The following steps describe how you can manage terms of use:
 You can capture terms of use acceptance under the following scenarios:
 
 - A new user is signing up. The terms of use are displayed, and the acceptance result is stored.
-- A user is signing in who has previously accepted the latest or active terms of agreement. The terms of use are not displayed.
+- A user is signing in who has previously accepted the latest or active terms of use. The terms of use are not displayed.
 - A user is signing in who has not already accepted the latest or active terms of use. The terms of use are displayed, and the acceptance result is stored.
 - A user is signing in who has already accepted an older version of the terms of use, which are now updated to the latest version. The terms of use are displayed, and the acceptance result is stored.
 

articles/active-directory-b2c/manage-user-access.md

@@ -435,7 +435,8 @@
 #### [iOS](active-directory-certificate-based-authentication-ios.md)
 #### [Get started](active-directory-certificate-based-authentication-get-started.md)
 
-### [Azure AD Identity Protection](active-directory-identityprotection.md)
+### Azure AD Identity Protection
+#### [Overview](identity-protection/overview.md)
 #### [Enable](identity-protection/enable.md)
 #### [Detect vulnerabilities](identity-protection/vulnerabilities.md)
 #### [Risk events](active-directory-identity-protection-risk-events.md)

articles/active-directory/TOC.md

@@ -27,7 +27,7 @@ Before you start, make sure you have the following prerequisites:
 
 **Enabled by conditional access policy** - This method is discussed in this article. It is the most flexible means to enable two-step verification for your users. Enabling using conditional access policy only works for Azure MFA in the cloud and is a premium feature of Azure AD.
 
-Enabled by Azure AD Identity Protection - This method uses the Azure AD Identity Protection risk policy to require two-step verification based only on sign-in risk for all cloud applications. This method requires Azure Active Directory P2 licensing. More information on this method can be found in [Azure Active Directory Identity Protection](../active-directory-identityprotection.md#risky-sign-ins)
+Enabled by Azure AD Identity Protection - This method uses the Azure AD Identity Protection risk policy to require two-step verification based only on sign-in risk for all cloud applications. This method requires Azure Active Directory P2 licensing. More information on this method can be found in [Azure Active Directory Identity Protection](../identity-protection/overview.md#risky-sign-ins).
 
 Enabled by changing user state - This is the traditional method for requiring two-step verification. It works with both Azure MFA in the cloud and Azure MFA Server. Using this method requires users to perform two-step verification **every time** they sign in and overrides conditional access policies. More information on this method can be found in [How to require two-step verification for a user](howto-mfa-userstates.md)
 

articles/active-directory/authentication/howto-mfa-getstarted.md

@@ -27,7 +27,7 @@ You can take one of two approaches for requiring two-step verification. The firs
 
 Enabled by conditional access policy - This is the most flexible means to enable two-step verification for your users. Enabling using conditional access policy only works for Azure MFA in the cloud and is a premium feature of Azure AD. More information on this method can be found in [Deploy cloud-based Azure Multi-Factor Authentication](howto-mfa-getstarted.md).
 
-Enabled by Azure AD Identity Protection - This method uses the Azure AD Identity Protection risk policy to require two-step verification based only on sign-in risk for all cloud applications. This method requires Azure Active Directory P2 licensing. More information on this method can be found in [Azure Active Directory Identity Protection](../active-directory-identityprotection.md#risky-sign-ins)
+Enabled by Azure AD Identity Protection - This method uses the Azure AD Identity Protection risk policy to require two-step verification based only on sign-in risk for all cloud applications. This method requires Azure Active Directory P2 licensing. More information on this method can be found in [Azure Active Directory Identity Protection](../identity-protection/overview.md#risky-sign-ins)
 
 > [!Note]
 > More information about licenses and pricing can be found on the [Azure AD](https://azure.microsoft.com/pricing/details/active-directory/

articles/active-directory/authentication/howto-mfa-userstates.md

@@ -14,7 +14,7 @@ ms.workload: identity
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 07/31/2018
+ms.date: 08/08/2018
 ms.author: markvi
 ms.reviewer: sandeo
 
@@ -155,8 +155,6 @@ To successfully complete hybrid Azure AD join of your Windows down-level devices
 
 - `https://device.login.microsoftonline.com`
 
-- `https://device.login.microsoftonline.com`
-
 - `https://autologon.microsoftazuread-sso.com`.
 
 Additionally, you need to enable **Allow updates to status bar via script** in the user’s local intranet zone.

articles/active-directory/devices/hybrid-azuread-join-managed-domains.md

@@ -48,8 +48,8 @@ To unblock a suspicious sign-in, you have the following options:
 ## Unblocking accounts at risk
 To unblock an account at risk, you have the following options:
 
-1. **Reset password** - You can reset the user's password. For more information, see [manual secure password reset](../active-directory-identityprotection.md#manual-secure-password-reset).
-2. **Dismiss all risk events** - The user risk policy blocks a user if the configured user risk level for blocking access has been reached. You can reduce a user's risk level by manually closing reported risk events. For more information, see [closing risk events manually](../active-directory-identityprotection.md#closing-risk-events-manually).
+1. **Reset password** - You can reset the user's password. For more information, see [manual secure password reset](overview.md#manual-secure-password-reset).
+2. **Dismiss all risk events** - The user risk policy blocks a user if the configured user risk level for blocking access has been reached. You can reduce a user's risk level by manually closing reported risk events. For more information, see [closing risk events manually](overview.md#closing-risk-events-manually).
 3. **Exclude from policy** - If you think that the current configuration of your sign-in policy is causing issues for specific users, you can exclude the users from it. For more information, see [Azure Active Directory Identity Protection](../active-directory-identityprotection.md).
 4. **Disable policy** - If you think that your policy configuration is causing issues for all your users, you can disable the policy. For more information, see [Azure Active Directory Identity Protection](../active-directory-identityprotection.md).