Microsoft Entra ID
ProvisioningMicrosoft Entra Cloud Sync migration decision guide
In brief
The guide now distinguishes platform capability comparisons from what the guided migration tool can transfer. It identifies device synchronization as a current guided-tool blocker and adds separate guidance for guided, manual, or deferred migration paths.
What Entra admins need to know
Administrators should review the tool prerequisites and limits before selecting a migration path; supported capabilities alone do not confirm guided-tool eligibility.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
Migrate from Microsoft Entra Connect Sync to Cloud Sync: Decision Guidedecision guide
Microsoft Entra Cloud Sync represents Microsoft's strategic direction for hybrid identity synchronization. It provides cloud-managed synchronization of users, groups, and contacts between Active Directory and Microsoft Entra ID. When device sync is enabled, Cloud Sync can synchronize Active Directory computer objects to Microsoft Entra ID for hybrid join.
This decision guide helps IT architects and decision makers evaluate migration from Microsoft Entra Connect Sync to Cloud Sync by comparing technical capabilities, identifying architectural advantages, and providing migration readiness assessments. For basic overview information, see What is Microsoft Entra Cloud Sync?. For step-by-step migration procedures, see Migrating from Microsoft Entra Connect to Microsoft Entra Cloud Sync.
New identity and synchronization features are being developed primarily on the Cloud Sync platform, making it the recommended path forward for most organizations.
The following table provides a detailed comparison of technical capabilities between Microsoft Entra Connect and Cloud Sync:
| Feature/Capability | Connect Sync | Cloud Sync | Technical Notes |
|---|---|---|---|
| Users, Groups, Contacts Sync | ✓ | ✓ | Full parity for basic directory object synchronization |
| Single Connected Forest | ✓ | ✓ | Both support standard single-forest topologies |
| Multiple Connected Forests | ✓ | ✓ | Both support multiple connected forest scenarios |
| Disconnected Forest Support | ✗ | ✓ | Cloud Sync enables M&A scenarios without forest consolidation |
| Device Synchronization | ✓ | ✓ | Both support device synchronization for Microsoft Entra hybrid join; enable device sync separately in Cloud |
| Multiple Active Sync Instances | ✗ | ✓ | Cloud Sync agents provide automatic failover and load distribution |
| Scale Limits per Domain | Unlimited | 150K objects | Cloud Sync currently supports up to 150,000 objects per domain |
| Large Group Support | 250K members | 50K members | Connect supports larger groups; Cloud Sync limited to 50,000 members |
Ready for immediate migration
Your organization can migrate immediately if you meet allUse these criteria:criteria to assess platform readiness. They don't establish guided-tool eligibility or replace a documented migration procedure:
- Object Scale: Fewer than 150,000 objects per Active Directory domain
- Group Size: Groups with fewer than 50,000 members
- Plan Migration Timing: Monitor feature announcements, consider business cycles, and assess resource availability
- Validate Prerequisites: Ensure your environment meets Cloud Sync prerequisites
- Test Migration Process: Use the pilot migration tutorial to validate the migration process
Choose an outcome based on both platform support and the available migration path:
- Use the guided migration tool: Your organization and active Connect Sync installation meet the current tool requirements, and the readiness review confirms eligibility.
- Use documented manual guidance: Cloud Sync supports your required scenario and Microsoft provides a documented manual migration procedure. Review the migration overview and manual pilot tutorial.
- Continue using Connect Sync: A required capability or documented migration path isn't available. Review the feature comparison. If a confirmed blocker prevents you from meeting a notified migration deadline, request more time.
@@ -2,20 +2,20 @@ title: Microsoft Entra Cloud Sync migration decision guide description: Compare Microsoft Entra Connect and Cloud Sync capabilities, including device synchronization, to assess migration readiness and plan next steps. ms.topic: concept-article-ms.date: 10/06/2026+ms.date: 10/21/2026 ms.subservice: hybrid-cloud-sync-ms.custom: customer-intent, msecd-doc-authoring-1023+ms.custom: customer-intent, msecd-doc-authoring-1028 #customer intent: As an IT architect or administrator, I want to evaluate migrating from Microsoft Entra Connect to Cloud Sync so that I can make informed decisions about modernizing my hybrid identity infrastructure. ai-usage: ai-assisted --- -# Migrate from Microsoft Entra Connect to Cloud Sync: Decision Guide+# Migrate from Microsoft Entra Connect Sync to Cloud Sync: decision guide Microsoft Entra Cloud Sync represents Microsoft's strategic direction for hybrid identity synchronization. It provides cloud-managed synchronization of users, groups, and contacts between Active Directory and Microsoft Entra ID. When device sync is enabled, Cloud Sync can synchronize Active Directory computer objects to Microsoft Entra ID for hybrid join. -This decision guide helps IT architects and decision makers evaluate migration from Microsoft Entra Connect to Cloud Sync by comparing technical capabilities, identifying architectural advantages, and providing migration readiness assessments. For basic overview information, see [What is Microsoft Entra Cloud Sync?](what-is-cloud-sync.md). For step-by-step migration procedures, see [Migrating from Microsoft Entra Connect to Microsoft Entra Cloud Sync](migrate-azure-ad-connect-to-cloud-sync.md).+This decision guide helps IT architects and decision makers evaluate migration from Microsoft Entra Connect Sync to Cloud Sync by comparing technical capabilities, identifying architectural advantages, and providing migration readiness assessments. For basic overview information, see [What is Microsoft Entra Cloud Sync?](what-is-cloud-sync.md). For step-by-step migration procedures, see [Migrating from Microsoft Entra Connect to Microsoft Entra Cloud Sync](migrate-azure-ad-connect-to-cloud-sync.md). New identity and synchronization features are being developed primarily on the Cloud Sync platform, making it the recommended path forward for most organizations. @@ -55,13 +55,16 @@ Microsoft's development focus for new synchronization and provisioning capabilit The following table provides a detailed comparison of technical capabilities between Microsoft Entra Connect and Cloud Sync: +> [!NOTE]+> This table describes capabilities available in Connect Sync and Cloud Sync. It doesn't indicate whether the guided migration tool can transfer each capability. Review the [guided migration-tool prerequisites and limits](migrate-connect-sync-cloud-sync-tool.md#prerequisites) before starting migration.+ | Feature/Capability | Connect Sync | Cloud Sync | Technical Notes | |:--- |:---:|:---:|:---| | **Users, Groups, Contacts Sync** | ✓ | ✓ | Full parity for basic directory object synchronization | | **Single Connected Forest** | ✓ | ✓ | Both support standard single-forest topologies | | **Multiple Connected Forests** | ✓ | ✓ | Both support multiple connected forest scenarios | | **Disconnected Forest Support** | ✗ | ✓ | Cloud Sync enables M&A scenarios without forest consolidation |-| **Device Synchronization** | ✓ | ✓ | Both support device synchronization for Microsoft Entra hybrid join; enable device sync separately in Cloud Sync |+| **Device Synchronization** | ✓ | ✓ | Both support device synchronization for Microsoft Entra hybrid join; enable device sync separately in Cloud Sync. The current guided migration tool lists device synchronization as a migration blocker. Review the [migration-tool requirements](migrate-connect-sync-cloud-sync-tool.md#prerequisites) separately. | | **Multiple Active Sync Instances** | ✗ | ✓ | Cloud Sync agents provide automatic failover and load distribution | | **Scale Limits per Domain** | Unlimited | 150K objects | Cloud Sync currently supports up to 150,000 objects per domain | | **Large Group Support** | 250K members | 50K members | Connect supports larger groups; Cloud Sync limited to 50,000 members |@@ -97,7 +100,7 @@ Based on your current requirements and the feature comparison in the table above ### Ready for immediate migration -Your organization can migrate immediately if you meet all these criteria:+Use these criteria to assess platform readiness. They don't establish guided-tool eligibility or replace a documented migration procedure: - **Object Scale**: Fewer than 150,000 objects per Active Directory domain - **Group Size**: Groups with fewer than 50,000 members @@ -138,3 +141,9 @@ Use this framework to make your migration decision: - **Plan Migration Timing**: Monitor feature announcements, consider business cycles, and assess resource availability - **Validate Prerequisites**: Ensure your environment meets [Cloud Sync prerequisites](how-to-prerequisites.md) - **Test Migration Process**: Use the [pilot migration tutorial](tutorial-pilot-aadc-aadccp.md) to validate the migration process++Choose an outcome based on both platform support and the available migration path:++- **Use the guided migration tool:** Your organization and active Connect Sync installation meet the [current tool requirements](migrate-connect-sync-cloud-sync-tool.md#prerequisites), and the readiness review confirms eligibility.+- **Use documented manual guidance:** Cloud Sync supports your required scenario and Microsoft provides a documented manual migration procedure. Review the [migration overview](migrate-azure-ad-connect-to-cloud-sync.md#choose-a-migration-path) and [manual pilot tutorial](tutorial-pilot-aadc-aadccp.md#considerations).+- **Continue using Connect Sync:** A required capability or documented migration path isn't available. Review the [feature comparison](#comparison-between-microsoft-entra-connect-and-cloud-sync). If a confirmed blocker prevents you from meeting a notified migration deadline, [request more time](migrate-connect-sync-cloud-sync-tool.md#request-more-time-to-migrate).