Merge pull request #48187 from MicrosoftDocs/master

8/3 AM Publish

Author: huypub

.openpublishing.redirection.json

@@ -15275,6 +15275,46 @@
             "redirect_url": "/azure/active-directory/develop/azure-ad-developers-guide",
             "redirect_document_id": false
         },
+        {
+            "source_path": "articles/active-directory/develop/GuidedSetups/active-directory-aspnetwebapp-v1.md",
+            "redirect_url": "/azure/active-directory/develop/quickstart-v1-aspnet-webapp",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/GuidedSetups/active-directory-ios.md",
+            "redirect_url": "/azure/active-directory/develop/tutorial-v2-ios",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/GuidedSetups/active-directory-android.md",
+            "redirect_url": "/azure/active-directory/develop/tutorial-v2-android",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/GuidedSetups/active-directory-windesktop.md",
+            "redirect_url": "/azure/active-directory/develop/tutorial-v2-windows-desktop",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/GuidedSetups/active-directory-uwp-v2.md",
+            "redirect_url": "/azure/active-directory/develop/tutorial-v2-windows-uwp",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/GuidedSetups/active-directory-aspnetwebapp.md",
+            "redirect_url": "/azure/active-directory/develop/tutorial-v2-asp-webapp",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/GuidedSetups/active-directory-javascriptspa.md",
+            "redirect_url": "/azure/active-directory/develop/tutorial-v2-javascript-spa",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-authentication-scenarios.md",
+            "redirect_url": "/azure/active-directory/develop/authentication-scenarios",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/virtual-machines/virtual-machines-linux-expand-disks.md",
             "redirect_url": "/azure/virtual-machines/linux/expand-disks",
@@ -26481,34 +26521,34 @@
             "redirect_document_id": false
         },
         {
-        "source_path": "articles/cognitive-services/LUIS/traffic-manager.md",
-        "redirect_url": "/azure/cognitive-services/LUIS/luis-traffic-manager",
-        "redirect_document_id": true
+            "source_path": "articles/cognitive-services/LUIS/traffic-manager.md",
+            "redirect_url": "/azure/cognitive-services/LUIS/luis-traffic-manager",
+            "redirect_document_id": true
         },
         {
-        "source_path": "articles/cognitive-services/LUIS/find-region-csharp.md",
-        "redirect_url": "/azure/cognitive-services/LUIS/luis-find-region-csharp",
-        "redirect_document_id": true
+            "source_path": "articles/cognitive-services/LUIS/find-region-csharp.md",
+            "redirect_url": "/azure/cognitive-services/LUIS/luis-find-region-csharp",
+            "redirect_document_id": true
         },
         {
-        "source_path": "articles/cognitive-services/LUIS/find-region-nodejs.md",
-        "redirect_url": "/azure/cognitive-services/LUIS/luis-find-region-nodejs",
-        "redirect_document_id": true
+            "source_path": "articles/cognitive-services/LUIS/find-region-nodejs.md",
+            "redirect_url": "/azure/cognitive-services/LUIS/luis-find-region-nodejs",
+            "redirect_document_id": true
         },
         {
-        "source_path": "articles/cognitive-services/LUIS/migration-v1-to-v2.md",
-        "redirect_url": "/azure/cognitive-services/LUIS/luis-migration-api-v1-to-v2",
-        "redirect_document_id": true
+            "source_path": "articles/cognitive-services/LUIS/migration-v1-to-v2.md",
+            "redirect_url": "/azure/cognitive-services/LUIS/luis-migration-api-v1-to-v2",
+            "redirect_document_id": true
         },
         {
-        "source_path": "articles/cognitive-services/LUIS/interactive-test.md",
-        "redirect_url": "/azure/cognitive-services/LUIS/luis-interactive-test",
-        "redirect_document_id": true
+            "source_path": "articles/cognitive-services/LUIS/interactive-test.md",
+            "redirect_url": "/azure/cognitive-services/LUIS/luis-interactive-test",
+            "redirect_document_id": true
         },
         {
-        "source_path": "articles/china/china-get-started-service-availability.md",
-        "redirect_url": "https://www.azure.cn/home/features/products-by-region",
-        "redirect_document_id": true
+            "source_path": "articles/china/china-get-started-service-availability.md",
+            "redirect_url": "https://www.azure.cn/home/features/products-by-region",
+            "redirect_document_id": true
         },
         {
             "source_path": "articles/powerbi-embedded/create-capacity.md",

articles/active-directory-b2c/active-directory-b2c-devquickstarts-graph-dotnet.md

@@ -23,7 +23,7 @@ Azure Active Directory (Azure AD) B2C tenants tend to be very large. This means
 For B2C tenants, there are two primary modes of communicating with the Graph API.
 
 * For interactive, run-once tasks, you should act as an administrator account in the B2C tenant when you perform the tasks. This mode requires an administrator to sign in with credentials before that admin can perform any calls to the Graph API.
-* For automated, continuous tasks, you should use some type of service account that you provide with the necessary privileges to perform management tasks. In Azure AD, you can do this by registering an application and authenticating to Azure AD. This is done by using an **Application ID** that uses the [OAuth 2.0 client credentials grant](../active-directory/develop/active-directory-authentication-scenarios.md#daemon-or-server-application-to-web-api). In this case, the application acts as itself, not as a user, to call the Graph API.
+* For automated, continuous tasks, you should use some type of service account that you provide with the necessary privileges to perform management tasks. In Azure AD, you can do this by registering an application and authenticating to Azure AD. This is done by using an **Application ID** that uses the [OAuth 2.0 client credentials grant](../active-directory/develop/authentication-scenarios.md#daemon-or-server-application-to-web-api). In this case, the application acts as itself, not as a user, to call the Graph API.
 
 In this article, you learn how to perform the automated-use case. You'll build a .NET 4.5 `B2CGraphClient` that performs user create, read, update, and delete (CRUD) operations. The client will have a Windows command-line interface (CLI) that allows you to invoke various methods. However, the code is written to behave in a noninteractive, automated fashion.
 

articles/active-directory/active-directory-saas-custom-apps.md

@@ -20,7 +20,7 @@ ms.custom: H1Hack27Feb2017
 
 # Configure single sign-on to applications that are not in the Azure Active Directory application gallery
 
-This article is about a feature that enables administrators to configure single sign-on to applications not present in the Azure Active Directory app gallery *without writing code*. This feature was released from technical preview on November 18, 2015 and is included in [Azure Active Directory Premium](fundamentals/active-directory-whatis.md). If you are instead looking for developer guidance on how to integrate custom apps with Azure AD through code, see [Authentication Scenarios for Azure AD](active-directory-authentication-scenarios.md).
+This article is about a feature that enables administrators to configure single sign-on to applications not present in the Azure Active Directory app gallery *without writing code*. This feature was released from technical preview on November 18, 2015 and is included in [Azure Active Directory Premium](fundamentals/active-directory-whatis.md). If you are instead looking for developer guidance on how to integrate custom apps with Azure AD through code, see [Authentication Scenarios for Azure AD](develop/authentication-scenarios.md).
 
 The Azure Active Directory application gallery provides a listing of applications that are known to support a form of single sign-on with Azure Active Directory, as described in [this article](manage-apps/what-is-single-sign-on.md). Once you (as an IT specialist or system integrator in your organization) have found the application you want to connect, you can get started by following the step-by-step instructions presented in the Azure portal to enable single sign-on.
 

articles/active-directory/authentication/concept-registration-mfa-sspr-converged.md

@@ -68,10 +68,12 @@ Audit logs for this new experience exist under the Authentication Methods catego
 ## Known issues
 
 **Default MFA method is set to phone call when user registers phone using text message**
-   * Some users may notice that their default MFA method is set to phone call after they register their phone number using text message. Users can resolve this issue by changing their default method by following these instructions. 
+
+   * Some users may notice that their default MFA method is set to phone call after they register their phone number using text message. Users can resolve this issue by changing their default method by following the instructions found in the article [Manage your security info (preview)](../user-help/security-info-manage-settings.md#change-your-info).
 
 **User unable to access the new registration experience after admin disables their default method**
-   * Some users may not be able to access the new registration experience if their previously registered default MFA method has been disabled by their administrator. Here is an example scenario: 
+
+   * Some users may not be able to access the new registration experience if their previously registered default MFA method has been disabled by their administrator. Here is an example scenario:
       1. User previously registered their phone number and set their default method to phone call.
       2. Admin disables phone call as an MFA method for the tenant.
       3. User is prompted to register during sign-in because they need to register an additional method to meet the tenant SSPR policy.

articles/active-directory/connect-health/active-directory-aadconnect-health-version-history.md

@@ -19,17 +19,23 @@ ms.author: billmath
 ---
 # Azure AD Connect Health: Version Release History
 The Azure Active Directory team regularly updates Azure AD Connect Health with new features and functionality. This article lists the versions and features that have been released.
+Azure AD Connect Health for Sync is integrated with Azure AD Connect installation. Read more about [Azure AD Connect release history](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect-version-history)
+
+
+## August 2018 
+*  Azure AD Connect Health agent for Sync (version 3.1.7.0) released with Azure AD Connect version 1.1.880.0    
+   1. Hotfix for [high CPU issue of monitoring agent with .NET Framework KB releases](https://support.microsoft.com/help/4346822/high-cpu-issue-in-azure-active-directory-connect-health-for-sync)
 
 ## June 2018 
 **New preview features:** 
 * Azure AD Connect Health for Sync - Diagnose and remediate duplicated attribute sync errors from the portal 
 
 **Agent Update:** 
 *  Azure AD Connect Health agent for AD DS (version 3.1.7.0)    
-   1. Hotfix for high CPU issue of monitoring agent with .NET Framework KB releases
-
+   1. Hotfix for [high CPU issue of monitoring agent with .NET Framework KB releases](https://support.microsoft.com/help/4346822/high-cpu-issue-in-azure-active-directory-connect-health-for-sync)
+   
 *	Azure AD Connect Health agent for AD FS (version 3.1.7.0)  
-   1. Hotfix for high CPU issue of monitoring agent with .NET Framework KB releases  
+   1. Hotfix for [high CPU issue of monitoring agent with .NET Framework KB releases](https://support.microsoft.com/help/4346822/high-cpu-issue-in-azure-active-directory-connect-health-for-sync)
    2. Test results fixes on ADFS Server 2016 secondary server
 
 *	Azure AD Connect Health agent for AD FS (version 3.1.2.0)  
@@ -47,7 +53,7 @@ The Azure Active Directory team regularly updates Azure AD Connect Health with n
  2. Agent privacy improvement  
  3. Bug fixes and general improvements
 
-* Azure AD Connect Health agent for Sync (version 3.0.164.0) released with Azure AD Connect version 1.1.819.0
+* Azure AD Connect Health agent for Sync (version 3.0.164.0) released with Azure AD Connect version 1.1.819.0 
  1. Agent privacy improvement  
  2. Bug fixes and general improvements
 
@@ -64,7 +70,7 @@ The Azure Active Directory team regularly updates Azure AD Connect Health with n
 *	Azure AD Connect Health agent for AD FS (version 3.0.176.0)
   1. Agent availability improvements 
   2. Bug fixes and general improvements
-* Azure AD Connect Health agent for Sync (version 3.0.176.0)
+* Azure AD Connect Health agent for Sync (version 3.0.129.0) released with Azure AD Connect version 1.1.750.0  
   1. Agent availability improvements 
   2. Bug fixes and general improvements
 

articles/active-directory/connect/active-directory-aadconnect-version-history.md

@@ -36,7 +36,7 @@ Download| [Download Azure AD Connect](http://go.microsoft.com/fwlink/?LinkId=615
 
 ### Release status
 
-7/20/2018: Released for auto upgrade. Release for download will follow shortly.
+7/20/2018: Released for download and auto upgrade. The auto upgrade process is still in progress.
 
 ### New features and improvements
 

articles/active-directory/connect/active-directory-aadconnectsync-implement-password-hash-synchronization.md

@@ -13,7 +13,7 @@ ms.workload: identity
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 07/20/2018
+ms.date: 07/30/2018
 ms.component: hybrid
 ms.author: billmath
 
@@ -22,9 +22,9 @@ ms.author: billmath
 This article provides information that you need to synchronize your user passwords from an on-premises Active Directory instance to a cloud-based Azure Active Directory (Azure AD) instance.
 
 ## What is password hash synchronization
-The probability that you're blocked from getting your work done due to a forgotten password is related to the number of different passwords you need to remember. The more passwords you need to remember, the higher the probability to forget one. Questions and calls about password resets and other password-related issues demand the most helpdesk resources.
+The likelihood that you're blocked from getting your work done due to a forgotten password is related to the number of different passwords you need to remember. The more passwords you need to remember, the higher the probability to forget one. Questions and calls about password resets and other password-related issues demand the most help desk resources.
 
-Password hash synchronization is a feature used to synchronize user passwords from an on-premises Active Directory instance to a cloud-based Azure AD instance.
+Password hash synchronization is a feature used to synchronize a hash of the hash of a users password from an on-premises Active Directory instance to a cloud-based Azure AD instance.
 Use this feature to sign in to Azure AD services like Office 365, Microsoft Intune, CRM Online, and Azure Active Directory Domain Services (Azure AD DS). You sign in to the service by using the same password you use to sign in to your on-premises Active Directory instance.
 
 ![What is Azure AD Connect](./media/active-directory-aadconnectsync-implement-password-hash-synchronization/arch1.png)

articles/active-directory/connect/active-directory-azure-ad-connect-azure-ad-trust.md

@@ -4,18 +4,18 @@ description: Operational details of Azure AD trust handling by Azure AD connect.
 keywords: AD FS, ADFS, AD FS management, AAD Connect, Connect, Azure AD, trust, AAD, claim, claim, claim rules, issuance, transform, rules, backup, restore
 services: active-directory
 documentationcenter: ''
-author: anandyadavmsft
-manager: samueld
-editor: ''
-
+ms.reviewer: anandyadavmsft
+manager: mtillman
+ms.component: hybrid
 ms.assetid: 2593b6c6-dc3f-46ef-8e02-a8e2dc4e9fb9
 ms.service: active-directory    
 ms.workload: identity
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 07/11/2018
-ms.author: anandy
+ms.date: 07/28/2018
+ms.author: billmath
+author: billmath
 ms.custom: 
 ---
 # Manage AD FS trust with Azure AD using Azure AD Connect