Microsoft Entra ID Governance
FundamentalsCross Tenant Synchronization Overview
In brief
The documentation now states that direct cross-tenant user synchronization requires Microsoft Entra ID P1, while synchronizing a group and its members requires Microsoft Entra ID Governance or Microsoft Entra Suite for each synchronized user in the source tenant.
What Entra admins need to know
Admins planning group synchronization should verify that synchronized users have the required licenses.
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.
| Cross-tenant synchronization for groups (same cloud) | Microsoft Entra ID Governance or Microsoft Entra Suite licenses | Not applicable | | Cross-cloud synchronization | Microsoft Entra ID Governance or Microsoft Entra Suite licenses | Not applicable |
Source tenant: Each user who's synchronized with cross-tenant synchronization must have a Microsoft Entra ID P1 license in their home/source tenant. Synchronizing a group and its members requires a Microsoft Entra ID Governance or Microsoft Entra Suite license for each synchronized user in the source tenant. Using groups only to determine which users are synchronized, without synchronizing the groups themselves, requires Microsoft Entra ID P1 licenses. Each user who's synchronized with cross-cloud synchronization must have a Microsoft Entra ID Governance or Microsoft Entra Suite license in their home/source tenant. For more information, see Microsoft Entra plans and pricing and Microsoft Entra ID Governance licensing fundamentals.
Target tenant: Licenses aren't required for cross-tenant synchronization or cross-cloud synchronization in the target tenant. However, depending on the features you're using in the target tenant, you might need additional licensing. For example, customers who enabled External ID billing and are provisioning external guests might be charged according to the billing model for Microsoft Entra External ID.
@@ -128,7 +128,7 @@ The following table lists the required licenses, depending on your scenario. | Cross-tenant synchronization for groups (same cloud) | Microsoft Entra ID Governance or Microsoft Entra Suite licenses | Not applicable | | [Cross-cloud synchronization](cross-tenant-synchronization-configure.md?pivots=cross-cloud-synchronization) | Microsoft Entra ID Governance or Microsoft Entra Suite licenses | Not applicable | -**Source tenant**: Each user who's synchronized with cross-tenant synchronization must have a Microsoft Entra ID P1 license in their home/source tenant. Each user who's synchronized with cross-cloud synchronization must have a Microsoft Entra ID Governance or Microsoft Entra Suite license in their home/source tenant. For more information, see [Microsoft Entra plans and pricing](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing) and [Microsoft Entra ID Governance licensing fundamentals](../../id-governance/licensing-fundamentals.md).+**Source tenant**: Each user who's synchronized with cross-tenant synchronization must have a Microsoft Entra ID P1 license in their home/source tenant. Synchronizing a group and its members requires a Microsoft Entra ID Governance or Microsoft Entra Suite license for each synchronized user in the source tenant. Using groups only to determine which users are synchronized, without synchronizing the groups themselves, requires Microsoft Entra ID P1 licenses. Each user who's synchronized with cross-cloud synchronization must have a Microsoft Entra ID Governance or Microsoft Entra Suite license in their home/source tenant. For more information, see [Microsoft Entra plans and pricing](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing) and [Microsoft Entra ID Governance licensing fundamentals](../../id-governance/licensing-fundamentals.md). **Target tenant**: Licenses aren't required for cross-tenant synchronization or cross-cloud synchronization in the target tenant. However, depending on the features you're using in the target tenant, you might need additional licensing. For example, customers who enabled External ID billing and are provisioning external guests might be charged according to [the billing model for Microsoft Entra External ID](../../external-id/external-identities-pricing.md).