Merge pull request #78729 from SanDeo-MSFT/patch-9

Update hybrid-azuread-join-control.md

Author: PRMerger16

articles/active-directory/devices/hybrid-azuread-join-control.md

@@ -29,14 +29,9 @@ To do a controlled validation of hybrid Azure AD join on Windows current devices
 
 1. Clear the Service Connection Point (SCP) entry from Active Directory (AD) if it exists
 1. Configure client-side registry setting for SCP on your domain-joined computers using a Group Policy Object (GPO)
-1. If you are using AD FS, you must also:
-   1. Configure the client-side registry setting for SCP on your AD FS server using a GPO  
-   1. Uncheck “Automatically remove unused devices” under Services > Device Registration > Properties  
+1. If you are using AD FS, you must also configure the client-side registry setting for SCP on your AD FS server using a GPO  
 
-> [!NOTE]
-> Ensure default configuration remains unchanged for “Register domain-joined computers as devices” GPO set to “Not Configured” and “Automatically register new Windows 10 domain joined devices with Azure Active Directory” set to “Yes” when using Configuration Manager.
 
-After you verify that everything works as expected, you can automatically register the rest of your Windows current devices with Azure AD by [configuring SCP using Azure AD Connect](hybrid-azuread-join-managed-domains.md#configure-hybrid-azure-ad-join).
 
 ### Clear the SCP from AD
 
@@ -50,8 +45,6 @@ Use the Active Directory Services Interfaces Editor (ADSI Edit) to modify the SC
    1. Select the values of **azureADId** and **azureADName** (one at a time) and click **Remove**
 1. Close **ADSI Edit**
 
-> [!NOTE]
-> If a SCP is not configured in AD, then you should follow the same approach as described to [Configure client-side registry setting for SCP](#configure-client-side-registry-setting-for-scp)) on your domain-joined computers using a Group Policy Object (GPO).
 
 ### Configure client-side registry setting for SCP
 
@@ -96,9 +89,10 @@ The installer creates a scheduled task on the system that runs in the user conte
 To control the device registration, you should deploy the Windows Installer package to your selected group of Windows down-level devices.
 
 > [!NOTE]
-> If SCP is not configured in AD, then you should follow the same approach as described above to configure the client-side registry setting for SCP on your domain-joined computers using a Group Policy Object (GPO).
+> If a SCP is not configured in AD, then you should follow the same approach as described to [Configure client-side registry setting for SCP](#configure-client-side-registry-setting-for-scp)) on your domain-joined computers using a Group Policy Object (GPO).
+
 
-After you verify that everything works as expected, you can automatically register the rest of your Windows down-level devices with Azure AD by deploying the package to all down-level devices and [configuring SCP using Azure AD Connect](hybrid-azuread-join-managed-domains.md#configure-hybrid-azure-ad-join).
+After you verify that everything works as expected, you can automatically register the rest of your Windows current and down-level devices with Azure AD by [configuring SCP using Azure AD Connect](hybrid-azuread-join-managed-domains.md#configure-hybrid-azure-ad-join).
 
 ## Next steps