Back to latest version
You're viewing a historical snapshot from Jan 7, 2026. This is not the latest version.

Metadata at Jan 7, 2026

Last Updated

Jan 7, 2026

Published Dec 16, 2025

Service

Microsoft Entra

Tag

Updated message
New feature
User impact
Admin impact

Platforms

Web

MC1198077 - Microsoft Entra: Cross-tenant security group synchronization

Message Center

What changed since this version

removed textadded text

Updated January 7,April 22, 2026: We have updated the content.timeline. Thank you for your patience. 

We’re introducing cross-tenant group synchronization, a new capability that enables organizations to synchronize security groups across Microsoft Entra tenants. This feature simplifies collaboration scenarios by allowing shared access to resources across tenants while maintaining centralized group management. It also streamlines administration of multiple tenants by centralizing group membership control, reducing duplication and manual overhead. The new group sync functionality will be part of the Microsoft Entra ID Governance / Microsoft Entra Suite license

This message is associated with Microsoft 365 Roadmap ID 518221.

When this will happen
  • Public Preview: Rollout begins in late January 2026 and completes by late January 2026.
  • General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins in late April 2026 and completes by end of May 2026 (previously late April 2026April).
How this affects your organization
  • Who is affected: Admins managing Microsoft Entra tenants who want to enable cross-tenant group synchronization.
  • What will happen:
    • No impact unless you opt in during Public Preview.
    • Admins can enable synchronization by updating attribute mappings.
    • Cross-tenant access policies in the target tenant must allow group synchronization.
What you can do to prepare
  • Identify groups that require synchronization into other tenants.
  • Collaborate with admins of other tenants to align on supported scenarios and business processes.
  • Review and update attribute mappings and cross-tenant access policies as needed.

Learn more: Configure cross-tenant synchronization - Microsoft Entra ID | Microsoft Learn

Compliance considerations

No compliance considerations identified. Review as appropriate for your organization.

Snapshot from Jan 7, 2026

Updated January 7, 2026: We have updated the content. Thank you for your patience. 

We’re introducing cross-tenant group synchronization, a new capability that enables organizations to synchronize security groups across Microsoft Entra tenants. This feature simplifies collaboration scenarios by allowing shared access to resources across tenants while maintaining centralized group management. It also streamlines administration of multiple tenants by centralizing group membership control, reducing duplication and manual overhead. The new group sync functionality will be part of the Microsoft Entra ID Governance / Microsoft Entra Suite license

This message is associated with Microsoft 365 Roadmap ID 518221.

When this will happen
  • Public Preview: Rollout begins in late January 2026 and completes by late January 2026.
  • General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins in late April 2026 and completes by late April 2026.
How this affects your organization
  • Who is affected: Admins managing Microsoft Entra tenants who want to enable cross-tenant group synchronization.
  • What will happen:
    • No impact unless you opt in during Public Preview.
    • Admins can enable synchronization by updating attribute mappings.
    • Cross-tenant access policies in the target tenant must allow group synchronization.
What you can do to prepare
  • Identify groups that require synchronization into other tenants.
  • Collaborate with admins of other tenants to align on supported scenarios and business processes.
  • Review and update attribute mappings and cross-tenant access policies as needed.

Learn more: Configure cross-tenant synchronization - Microsoft Entra ID | Microsoft Learn

Compliance considerations

No compliance considerations identified. Review as appropriate for your organization.