Merge pull request #98318 from JasonWHowell/patch-5

Update how-to-connect-sync-change-the-configuration.md

Author: PRMerger12

articles/active-directory/hybrid/how-to-connect-sync-change-the-configuration.md

@@ -1,16 +1,12 @@
 ---
-title: 'Azure AD Connect sync: Make a configuration change in Azure AD Connect sync | Microsoft Docs'
+title: 'Azure AD Connect sync: Make a configuration change in Azure AD Connect sync'
 description: Walks you through how to make a change to the configuration in Azure AD Connect sync.
 services: active-directory
-documentationcenter: ''
 author: billmath
 manager: daveba
-editor: ''
 ms.assetid: 7b9df836-e8a5-4228-97da-2faec9238b31
 ms.service: active-directory
 ms.workload: identity
-ms.tgt_pltfrm: na
-ms.devlang: na
 ms.topic: conceptual
 ms.date: 08/30/2018
 ms.subservice: hybrid
@@ -199,7 +195,7 @@ By default, the UserType attribute is not enabled for synchronization because th
 
 - Azure AD only accepts two values for the UserType attribute: **Member** and **Guest**.
 - If the UserType attribute is not enabled for synchronization in Azure AD Connect, Azure AD users created through directory synchronization would have the UserType attribute set to **Member**.
-- Azure AD does not permit the UserType attribute on existing Azure AD users to be changed by Azure AD Connect. It can only be set during the creation of the Azure AD users and [changed via Powershell](https://docs.microsoft.com/en-us/powershell/module/azuread/set-azureaduser?view=azureadps-2.0).
+- Azure AD does not permit the UserType attribute on existing Azure AD users to be changed by Azure AD Connect. It can only be set during the creation of the Azure AD users and [changed via Powershell](/powershell/module/azuread/set-azureaduser?view=azureadps-2.0).
 
 Before enabling synchronization of the UserType attribute, you must first decide how the attribute is derived from on-premises Active Directory. The following are the most common approaches: