udpating

Author: billmath

articles/active-directory/cloud-sync/how-to-manage-registry-options.md

@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.topic: how-to
 ms.tgt_pltfrm: na
 ms.workload: identity
-ms.date: 01/11/2023
+ms.date: 04/03/2023
 ms.subservice: hybrid
 ms.reviewer: chmutali
 ms.author: billmath
@@ -62,29 +62,6 @@ Use the following steps to turn on referral chasing:
 1. Restart the Azure AD Connect Provisioning Service from the *Services* console.
 1. If you have deployed multiple provisioning agents, apply this registry change to all agents for consistency.
 
-## Skip GMSA configuration
-With agent version 1.1.281.0+, by default, when you run the agent configuration wizard, you are prompted to setup [Group Managed Service Account (GMSA)](/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview). The GMSA setup by the wizard is used at runtime for all sync and provisioning operations. 
-
-If you are upgrading from a prior version of the agent and have setup a custom service account with delegated OU-level permissions specific to your Active Directory topology, you may want to skip/postpone GMSA configuration and plan for this change. 
-
-> [!NOTE]
-> This guidance specifically applies to customers who have configured HR (Workday/SuccessFactors) inbound provisioning with agent versions prior to 1.1.281.0 and have setup a custom service account for agent operations. In the long run, we recommend switching to GMSA as a best practice.  
-
-In this scenario, you can still upgrade the agent binaries and skip the GMSA configuration using the following steps: 
-
-1. Log on as Administrator on the Windows server running the Azure AD Connect Provisioning Agent.
-1. Run the agent installer to install the new agent binaries. Close the agent configuration wizard which opens up automatically after the installation is successful. 
-1. Use the *Run* menu item to open the registry editor (regedit.exe) 
-1. Locate the key folder **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Azure AD Connect Agents\Azure AD Connect Provisioning Agent**
-1. Right-click and select "New -> DWORD Value"
-1. Provide the name: 
-  `UseCredentials`
-1. Double-click on the **Value Name** and enter the value data as `1`.  
-    > [!div class="mx-imgBorder"]
-    > ![Use Credentials](media/how-to-manage-registry-options/use-credentials.png)
-1. Restart the Azure AD Connect Provisioning Service from the *Services* console.
-1. If you have deployed multiple provisioning agents, apply this registry change to all agents for consistency.
-1. From the desktop short cut, run the agent configuration wizard. The wizard will skip the GMSA configuration. 
 
 
 > [!NOTE]