updating

Author: billmath

articles/active-directory/cloud-sync/TOC.yml

@@ -55,7 +55,7 @@
     - name: Directory extensions and custom attributes
       href: custom-attribute-mapping.md
     - name: Migrate from Azure AD Connect
-      href: migrate-aadc-to-cloud-sync.md
+      href: migrate-azure-ad-connect-to-cloud-sync.md
   - name: Plan and design
     items:
     - name: Topologies and scenarios for Azure AD Connect cloud sync

articles/active-directory/cloud-sync/migrate-aadc-to-cloud-sync.md renamed to articles/active-directory/cloud-sync/migrate-azure-ad-connect-to-cloud-sync.md

@@ -1,6 +1,6 @@
 ---
 title: 'Migrate Azure AD Connect to Azure AD Connect cloud sync| Microsoft Docs'
-description: Describes stpes to migrate Azure AD Connect to Azure AD Connect cloud sync.
+description: Describes steps to migrate Azure AD Connect to Azure AD Connect cloud sync.
 services: active-directory
 author: billmath
 manager: amycolannino
@@ -26,17 +26,17 @@ Azure AD Connect cloud sync is the future for accomplishing your hybrid identity
 |-----|-----|
 |Choose the best sync tool|Before moving to cloud sync, you should verify that cloud sync is currently the best synchronization tool for you.  You can do this task by going through the wizard [here](https://setup.microsoft.com/azure/add-or-sync-users-to-microsoft-365).|
 |Verify the pre-requisites for migrating|The following guidance is only for users who have installed Azure AD Connect using the Express settings and aren't synchronizing devices.  Also you should verify the cloud sync [pre-requisites](how-to-prerequisites.md).|
-|Back-up your Azure AD Connect configuration|Before making any changes, you should back-up your Azure AD Connect configuration.  This way, you can role-back.  For more information, see [Import and export Azure AD Connect configuration settings](../hybrid/how-to-connect-import-export-config.md).|
+|Back up your Azure AD Connect configuration|Before making any changes, you should back up your Azure AD Connect configuration.  This way, you can role-back.  For more information, see [Import and export Azure AD Connect configuration settings](../hybrid/how-to-connect-import-export-config.md).|
 |Review the migration tutorial|To become familiar with the migration process, review the [Migrate to Azure AD Connect cloud sync for an existing synced AD forest](tutorial-pilot-aadc-aadccp.md) tutorial.  This tutorial guides you through the migration process in a sandbox environment.|
 |Create or identify an OU for the migration|Create a new OU or identify an existing OU that contains the users you'll test migration on.|
-|Move users into new OU (optional)|If you're using an newly created OU, move the users that are in scope for this pilot into that OU now.  Before continuing, let Azure AD Connect pick up the changes so that it's synchronizing them in the new OU.| 
-|Run PowerShell on OU|You can run the following PowerShell cmdlt to get the counts of the users that are in the pilot OU.  </br>`Get-ADUser -Filter * -SearchBase "<DN path of OU>"`</br> Example: `Get-ADUser -Filter * -SearchBase "OU=Finance,OU=UserAccounts,DC=FABRIKAM,DC=COM"`|
+|Move users into new OU (optional)|If you're using a new OU, move the users that are in scope for this pilot into that OU now.  Before continuing, let Azure AD Connect pick up the changes so that it's synchronizing them in the new OU.| 
+|Run PowerShell on OU|You can run the following PowerShell cmdlet to get the counts of the users that are in the pilot OU.  </br>`Get-ADUser -Filter * -SearchBase "<DN path of OU>"`</br> Example: `Get-ADUser -Filter * -SearchBase "OU=Finance,OU=UserAccounts,DC=FABRIKAM,DC=COM"`|
 |Stop the scheduler|Before creating new sync rules, you need to stop the Azure AD Connect scheduler.  For more information, see [how to stop the scheduler](../hybrid/how-to-connect-sync-feature-scheduler.md#stop-the-scheduler).
 |Create the custom sync rules|In the Azure AD Connect Synchronization Rules editor, you need to create an inbound sync rule that filters out users in the OU you created or identified previously.  The inbound sync rule is a join rule with a target attribute of cloudNoFlow.  You'll also need an outbound sync rule with a link type of JoinNoFlow and the scoping filter that has the cloudNoFlow attribute set to True.  For more information, see [Migrate to Azure AD Connect cloud sync for an existing synced AD forest](tutorial-pilot-aadc-aadccp.md#create-custom-user-inbound-rule) tutorial for how to create these rules.|
 |Install the provisioning agent|If you haven't done so, install the provisioning agent.  For more information, see [how to install the agent](how-to-install.md).|
 |Configure cloud sync|Once the agent is installed, you need to configure cloud sync.  In the configuration, you need to create a scope to the OU that was created or identified previously.  For more information, see [Configuring cloud sync](how-to-configure.md).|
 |Verify pilot users are synchronizing and being provisioned|Verify that the users are now being synchronized in the portal.  You can use the PowerShell script below to get a count of the number of users that have the on-premises pilot OU in their distinguished name.  This number should match the count of users in the previous step.  If you create a new user in this OU, verify that it's being provisioned.|
-|Start the scheduler|Now that you've verifed users are provisioning and synchronizing, you can go ahead and start the Azure AD Connect scheduler.   For more information, see [how to start the scheduler](../hybrid/how-to-connect-sync-feature-scheduler.md#start-the-scheduler).
+|Start the scheduler|Now that you've verified users are provisioning and synchronizing, you can go ahead and start the Azure AD Connect scheduler.   For more information, see [how to start the scheduler](../hybrid/how-to-connect-sync-feature-scheduler.md#start-the-scheduler).
 |Schedule you remaining users|Now you should come up with a plan on migrating more users.  You should use a phased approach so that you can verify that the migrations are successful.|
 |Verify all users are provisioned|As you migrate users, verify that they're provisioning and synchronizing correctly.|
 |Stop Azure AD Connect|Once you've verified that all of your users are migrated, you can turn off the Azure AD Connect synchronization service.  Microsoft recommends that you leave the server is a disabled state for a period of time, so you can verify the migration was successful

articles/active-directory/cloud-sync/tutorial-pilot-aadc-aadccp.md

@@ -19,7 +19,7 @@ ms.collection: M365-identity-device-management
 This tutorial walks you through how you would migrate to cloud sync for a test Active Directory forest that is already synced using Azure Active Directory (Azure AD) Connect sync.  
 
 > [!NOTE]
-> This article provides information for a basic migration and you should review the [Migrating to cloud sync](migrate-aadc-to-cloud-sync.md) documentation before attempting to migrate your production environment.
+> This article provides information for a basic migration and you should review the [Migrating to cloud sync](migrate-azure-ad-connect-to-cloud-sync.md) documentation before attempting to migrate your production environment.
 
 ![Diagram that shows the Azure AD Connect cloud sync flow.](media/tutorial-migrate-aadc-aadccp/diagram-2.png)
 
@@ -56,8 +56,8 @@ The following are prerequisites required for completing this tutorial
 
 As a minimum, you should have [Azure AD connect](https://www.microsoft.com/download/details.aspx?id=47594) 1.4.32.0. To update Azure AD Connect sync, complete the steps in [Azure AD Connect: Upgrade to the latest version](../hybrid/how-to-upgrade-previous-version.md).  
 
-## Backup your Azure AD Connect configuration
-Before making any changes, you should back-up your Azure AD Connect configuration.  This way, you can role-back should you need to.  See [Import and export Azure AD Connect configuration settings](../hybrid/how-to-connect-import-export-config.md) for more information.
+## Back up your Azure AD Connect configuration
+Before making any changes, you should back up your Azure AD Connect configuration.  This way, you can role-back.  See [Import and export Azure AD Connect configuration settings](../hybrid/how-to-connect-import-export-config.md) for more information.
 
 ## Stop the scheduler