Merge pull request #105613 from billmath/cloudfix

updating

Author: v-albemi

articles/active-directory/cloud-provisioning/how-to-configure.md

@@ -7,13 +7,13 @@ manager: daveba
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 12/05/2019
+ms.date: 02/26/2020
 ms.subservice: hybrid
 ms.author: billmath
 ms.collection: M365-identity-device-management
 ---
 
-# Azure AD Connect cloud provisioning new agent configuration
+# Create a new configuration for Azure AD Connect cloud-based provisioning
 
 After you've installed the agent, you need to sign in to the Azure portal and configure Azure Active Directory (Azure AD) Connect cloud provisioning. Follow these steps to enable the agent.
 
@@ -51,7 +51,8 @@ You can scope the agent to synchronize specific users and groups by using on-pre
 
     ![Selected security groups option](media/how-to-configure/scope3.png)
 
-1.  Or you can change the scope to include only specific organizational units. Select **Done** and **Save**.
+1.  Or you can change the scope to include only specific organizational units. Select **Done** and **Save**.  
+2.  Once you have changed the scope, you should [restart provisioning](#restart-provisioning) to initiate an immediate synchronization of the changes.
 
     ![Selected organizational units option](media/how-to-configure/scope4.png)
 

articles/active-directory/cloud-provisioning/how-to-install.md

@@ -7,7 +7,7 @@ manager: daveba
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 02/26/2020
 ms.subservice: hybrid
 ms.author: billmath
 ms.collection: M365-identity-device-management
@@ -91,7 +91,7 @@ To verify that the agent is running, follow these steps.
     ![Services screen](media/how-to-troubleshoot/troubleshoot1.png)
 
 >[!IMPORTANT]
->The agent has been installed but it must be configured and enabled before it will start synchronizing users. To configure a new agent, see [Azure AD Connect cloud provisioning new agent configuration](how-to-configure.md).
+>The agent has been installed but it must be configured and enabled before it will start synchronizing users. To configure a new agent, see [Create a new configuration for Azure AD Connect cloud-based provisioning](how-to-configure.md).
 
 
 

articles/active-directory/cloud-provisioning/index.yml

@@ -1,7 +1,7 @@
 ### YamlMime:Landing
 
 title: Azure AD Connect cloud provisioning documentation
-summary:  Cloud provisioning helps simplify and automate the management of on-premises users by keeping everything in the cloud.
+summary:  Cloud provisioning helps simplify and automate the management of Azure AD users, through cloud-managed rules for synchronizing those users from existing AD forests.
 
 
 

articles/active-directory/cloud-provisioning/plan-cloud-provisioning-topologies.md

@@ -7,7 +7,7 @@ manager: daveba
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: 02/26/2020
 ms.subservice: hybrid
 ms.author: billmath
 ms.collection: M365-identity-device-management
@@ -29,12 +29,16 @@ The following is a list of information to keep in mind when selecting a solution
 - The source anchor for objects is chosen automatically.  It uses ms-DS-ConsistencyGuid if present, otherwise ObjectGUID is used.
 - You cannot change the attribute that is used for source anchor.
 
+## Single forest, single Azure AD tenant
+![Topology for a single forest and a single tenant](media/plan-cloud-provisioning-topologies/single-forest.png)
+
+The simplest topology is a single on-premises forest, with one or multiple domains, and a single Azure AD tenant.  For an example of this scenario see [Tutorial: A single forest with a single Azure AD tenant](tutorial-single-forest.md)
 
 
 ## Multi-forest, single Azure AD tenant
 ![Topology for a multi-forest and a single tenant](media/plan-cloud-provisioning-topologies/multi-forest.png)
 
-The most common topology is a multiple AD forests, with one or multiple domains, and a single Azure AD tenant.  
+A common topology is a multiple AD forests, with one or multiple domains, and a single Azure AD tenant.  
 
 ## Existing forest with Azure AD Connect, new forest with cloud Provisioning
 ![Topology for a single forest and a single tenant](media/plan-cloud-provisioning-topologies/existing-forest-new-forest.png)
@@ -47,10 +51,7 @@ The piloting scenario involves the existence of both Azure AD Connect and Azure
 
 For an example of this scenario see [Tutorial: Pilot Azure AD Connect cloud provisioning in an existing synced AD forest](tutorial-pilot-aadc-aadccp.md)
 
-## Single forest, single Azure AD tenant
-![Topology for a single forest and a single tenant](media/plan-cloud-provisioning-topologies/single-forest.png)
 
-The simplest topology is a single on-premises forest, with one or multiple domains, and a single Azure AD tenant.  For an example of this scenario see [Tutorial: A single forest with a single Azure AD tenant](tutorial-single-forest.md)
 
 ## Next steps