Daily.Entra.News
Aboutmerill.net
Microsoft Entra ID

Tutorial Pilot Aadc Aadccp

26 June 2026Updated+61 / −36 lines

In brief

Before you try this tutorial, consider the following items:

What Entra admins need to know

Review the documentation change to determine whether it affects tenant configuration, security posture, or rollout plans.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

Open on Microsoft Learn ↗

The comparison below is an extract of the Microsoft Learn article showing only the changed content. Open the full article for complete context.

Before you try this tutorial, consider the following items:

  • Ensure that you're familiar with the basics of Microsoft Entra Cloud Sync.

  • Ensure that you're running Microsoft Entra Connect Sync version 1.4.32.0 or later and that you configured the sync rules as documented.

  • Ensure that for aDuring the pilot that youor coexistence phase, don't remove a testthe pilot organizational unit (OU), group, domain, or groupany related referenced objects from Microsoft Entra Connect Sync scope. Moving objects out of scope leads to deletion of thoseKeep the objects in Microsoft Entra ID.

    • User objectsscope and use the custom cloudNoFlow inbound rule and JoinNoFlow outbound rule described in Microsoft Entra ID are soft-deleted, so you can restore them.
    • Group objects in Microsoft Entra ID are hard-deleted, so you can't restore them.

    this tutorial to prevent Microsoft Entra Connect Sync introduces a new link type, which preventsfrom exporting object adds, object deletes, and non-reference attribute updates.

    Removing objects from Microsoft Entra Connect Sync scope removes them from the deletionActive Directory connector space, metaverse, and Microsoft Entra connector space. This removal can remove references in a piloting scenario.the connector space and cause reference deletes, such as group membership removals, to be exported to Microsoft Entra ID.

  • Ensure that the objects in the pilot scope have ms-ds-consistencyGUID populated so that Microsoft Entra Cloud Sync hard matches the objects.

    Microsoft Entra Connect Sync doesn't populate ms-ds-consistencyGUID by default for group objects.

  • Follow the steps in this tutorial precisely. This configuration is for advanced scenarios.

Plan scope removal from Microsoft Entra Connect Sync

Don't remove OUs, groups, or domains from Microsoft Entra Connect Sync scope during the coexistence or pilot phase. Do this only after migration for that scope is complete and you've verified that Cloud Sync is authoritative for the objects and their references.

Before you remove a scope from Microsoft Entra Connect Sync, verify that:

  • All objects in that scope are included in the appropriate Cloud Sync configuration.
  • Related referenced objects, such as group members and managers, are also migrated or no longer depend on Microsoft Entra Connect Sync for reference maintenance.
  • There are no remaining cross-scope or cross-domain references that Microsoft Entra Connect Sync might delete from its connector space and export as reference removals.

Remove a domain from Microsoft Entra Connect Sync only after migration for that domain is complete and you're certain there are no remaining cross-domain references.

Prerequisites

The following are prerequisites required for completing this tutorial

Create a custom user inbound rule

In the Microsoft Entra Connect Synchronization Rules Editor, you need to create an inbound sync rule that filters outsets the cloudNoFlow attribute to True for users in the OU or group that you identified previously. The inbound syncfor the pilot. This attribute is used with the JoinNoFlow outbound rule is a join rule with a target attribute of cloudNoFlow. This rule tellslater in this tutorial to prevent Microsoft Entra Connect not to synchronize attributesSync from exporting object adds, object deletes, and non-reference attribute updates for these users. For more information, see Migrate to Microsoft Entra Cloud Sync before you attempt to migrate your production environment.

  1. Open the Synchronization Rules Editor from the application menu on the desktop.

    Screenshot that shows the Synchronization Rules Editor menu.

  2. Under Direction, select Inbound from the dropdown list. Then select Add new rule.

    Screenshot that shows the View and manage your synchronization rules window with Inbound and the Add new rule button selected.

  3. On the Description page, enter the following values and select Next:

    • Name: Give the rule a meaningful name.
    • Description: Add a meaningful description.
      • Connected System: Choose the Microsoft Entra connector for which you're writing the custom sync rule.
      • Connected System Object Type: Select user.
      • Metaverse Object Type: Select person.
      • Link Type: Select Join.
      • Precedence: Provide a value that's unique in the system.
      • Tag: Leave this field empty.

    Screenshot that shows the Create inbound synchronization rule - Description page with values entered.

  4. On the Scoping filter page, enter the OU or security group on which you want to base the pilot. To filter on OU, add the OU portion of the distinguished name. This rule applies to all users who are in that OU. So, if the distinguished name (DN) ends withReference attribute updates, such as OU=CPUsers,DC=contoso,DC=com, you add this filter. Then select Next.

    |Rule|Attribute|Operator|Value| |Scoping OU|DN|ENDSWITH|Distinguished name of the OU.| |Scoping group||ISMEMBEROF|Distinguished name of the security group.|

    Screenshot that shows the sync rule scoping filters.

  5. On the Join rules page, select Next.

  6. On the Transformations page, add a Constant transformation: Source value of True for the cloudNoFlow attribute. Select Add.

    Screenshot that shows the sync rule transformations.

Follow the same steps for all object types (user, group, and contact). Repeat the steps according to the configured Active Directory connector or Active Directory forest.

Create a custom user outbound rule

You need an outbound sync rule with a link type of JoinNoFlowmember and the scoping filter that has the cloudNoFlowmanager attribute set to True. This rule tells Microsoft Entra Connect not to synchronize attributes, can still flow for these users. For more information, see Migrate to Microsoft Entra Cloud Sync before you attempt to migrate your production environment.reference resolution.

  1. Under Direction, select Outbound from the dropdown list. Then select Add rule.

    Screenshot that shows the Outbound sync rules.

  2. On the Description page, enter the following values and select Next:

    • Name: Give the rule a meaningful name.
    • Description: Add a meaningful description.
      • Connected System: Choose the Microsoft Entra connector for which you're writing the custom sync rule.
      • Connected System Object Type: Select user.
      • Metaverse Object Type: Select person.
      • Link Type: Select JoinNoFlow.
      • Precedence: Provide a value that's unique in the system.
      • Tag: Leave this field empty.

    Screenshot that shows the sync rule description.

  3. On the Scoping filter page, for the Attribute, select cloudNoFlow. For Value, select True. Then select Next.

    Screenshot that shows a custom rule.

  4. On the Join rules page, select Next.

  5. On the Transformations page, select Add.

  6. Select New configuration.

    :::image type="content" source="media/how-to-configure/new-ux-configure-1.png" alt-text="Screenshot that shows adding a configuration." lightbox="media/how-to-configure/new-ux-configure-1.png":::

  7. On the configuration screen, select your domain and whether to enable password hash sync. Then select Create.

  8. Select the scoping filter. For this tutorial, select Selected organizational units. This filter scopes the configuration to apply to specific OUs.

  9. In the box, enter OU=CPUsers,DC=contoso,DC=com. :::image type="content" source="media/tutorial-migrate-aadc-aadccp/configure-1.png" alt-text="Screenshot that shows the scoping filter." lightbox="media/tutorial-migrate-aadc-aadccp/configure-1.png":::

  10. Select Add > Save.

  1. Open the Synchronization Rules Editor from the application menu on the desktop.

    Screenshot that shows the Synchronization Rules Editor menu.

  2. Under Direction, select Inbound from the dropdown list. Then select Add new rule.

    Screenshot that shows the View and manage your synchronization rules window with Inbound and the Add new rule button selected.

  3. On the Description page, enter the following values and select Next:

    • Name: Give the rule a meaningful name.
    • Description: Add a meaningful description.
    • Connected System: Choose the Microsoft Entra connector for which you're writing the custom sync rule.
    • Connected System Object Type: Select user.
    • Metaverse Object Type: Select person.
    • Link Type: Select Join.
    • Precedence: Provide a value that's unique in the system.
    • Tag: Leave this field empty.

    Screenshot that shows the Create inbound synchronization rule - Description page with values entered.

  4. On the Scoping filter page, enter the OU or security group on which you want to base the pilot. To filter on OU, add the OU portion of the distinguished name. This rule applies to all users who are in that OU. So, if the distinguished name (DN) ends with OU=CPUsers,DC=contoso,DC=com, you add this filter. Then select Next.

    |Rule|Attribute|Operator|Value| |Scoping OU|DN|ENDSWITH|Distinguished name of the OU.| |Scoping group||ISMEMBEROF|Distinguished name of the security group.|

    Screenshot that shows the sync rule scoping filters.

  5. On the Join rules page, select Next.

  6. On the Transformations page, add a Constant transformation: Source value of True for the cloudNoFlow attribute. Select Add.

    Screenshot that shows the sync rule transformations.

Follow the same steps for all object types (user, group, and contact). Repeat the steps according to the configured Active Directory connector or Active Directory forest.

Create a custom user outbound rule

You need an outbound sync rule with a link type of JoinNoFlow and the scoping filter that has the cloudNoFlow attribute set to True. This rule tells Microsoft Entra Connect Sync not to export object adds, object deletes, or non-reference attribute updates for these users. Reference attribute updates, such as member and manager, can still flow for reference resolution.

  1. Under Direction, select Outbound from the dropdown list. Then select Add rule.

    Screenshot that shows the Outbound sync rules.

  2. On the Description page, enter the following values and select Next:

    • Name: Give the rule a meaningful name.
    • Description: Add a meaningful description.
    • Connected System: Choose the Microsoft Entra connector for which you're writing the custom sync rule.
    • Connected System Object Type: Select user.
    • Metaverse Object Type: Select person.
    • Link Type: Select JoinNoFlow.
    • Precedence: Provide a value that's unique in the system.
    • Tag: Leave this field empty.

    Screenshot that shows the sync rule description.

  3. On the Scoping filter page, for the Attribute, select cloudNoFlow. For Value, select True. Then select Next.

    Screenshot that shows a custom rule.

  4. On the Join rules page, select Next.

  5. On the Transformations page, select Add.

  6. Select New configuration.

    :::image type="content" source="media/how-to-configure/new-ux-configure-1.png" alt-text="Screenshot that shows adding a configuration." lightbox="media/how-to-configure/new-ux-configure-1.png":::

  7. On the configuration screen, select your domain and whether to enable password hash sync. Then select Create.

  8. Select the scoping filter. For this tutorial, select Selected organizational units. This filter scopes the configuration to apply to specific OUs.

  9. In the box, enter OU=CPUsers,DC=contoso,DC=com.

    :::image type="content" source="media/tutorial-migrate-aadc-aadccp/configure-1.png" alt-text="Screenshot that shows the scoping filter." lightbox="media/tutorial-migrate-aadc-aadccp/configure-1.png":::

  10. Select Add > Save.

After the scheduler is enabled, Microsoft Entra Connect Sync stops exporting object adds, object deletes, and non-reference attribute updates for objects where cloudNoFlow=true in the metaverse and the outbound rule uses JoinNoFlow. Reference attributes are handled differently. Updates to reference attributes, such as member and manager, can still be exported for reference resolution.

If an object is removed from Microsoft Entra Connect Sync scope, its connector space and metaverse objects are removed. Any references to or from that object can be dropped in the Microsoft Entra connector space and exported as reference deletes. This behavior can cause group membership removals or other reference changes in Microsoft Entra ID.

Troubleshooting

  1. Disable provisioning configuration in the portal.
  2. Use the Sync Rule Editor tool to disable all the custom sync rules that you created for cloud provisioning. Disabling causes a full sync on all the connectors.

Removed group memberships or manager references

This issue can happen if objects are removed from Microsoft Entra Connect Sync scope while related groups, users, contacts, or other referenced objects are still in coexistence. When objects are removed from scope, Microsoft Entra Connect Sync removes the corresponding connector space and metaverse objects. This removal can drop references in the Microsoft Entra connector space and export reference deletes to Microsoft Entra ID.

To recover, readd the affected objects to Microsoft Entra Connect Sync scope and run a full synchronization to rebuild the connector space and metaverse references. Before you attempt to remove the scope again, verify that Microsoft Entra Cloud Sync is provisioning all affected objects and that references, such as group memberships and manager relationships, remain intact after a Cloud Sync provisioning cycle.

Related content