Managing the same groups in multiple Entra tenants?

๐Ÿ”’ Secure Bits ๐Ÿ’ก

๐— ๐—ฎ๐—ป๐—ฎ๐—ด๐—ถ๐—ป๐—ด ๐˜๐—ต๐—ฒ ๐˜€๐—ฎ๐—บ๐—ฒ ๐—ด๐—ฟ๐—ผ๐˜‚๐—ฝ๐˜€ ๐—ถ๐—ป ๐—บ๐˜‚๐—น๐˜๐—ถ๐—ฝ๐—น๐—ฒ ๐—˜๐—ป๐˜๐—ฟ๐—ฎ ๐˜๐—ฒ๐—ป๐—ฎ๐—ป๐˜๐˜€? ๐—ง๐—ต๐—ฎ๐˜ ๐—บ๐—ฎ๐˜† ๐—ป๐—ผ ๐—น๐—ผ๐—ป๐—ด๐—ฒ๐—ฟ ๐—ฏ๐—ฒ ๐—ป๐—ฒ๐—ฐ๐—ฒ๐˜€๐˜€๐—ฎ๐—ฟ๐˜†.

๐Ÿ“† Newly added feature in May 2026

Organizations with multiple Entra tenants often end up maintaining the same access groups repeatedly across environments.

One group for employees in Tenant A.

Another group for the same employees in Tenant B.

And then someone has to keep them in sync.

Microsoft is ๐—ฒ๐˜…๐˜๐—ฒ๐—ป๐—ฑ๐—ถ๐—ป๐—ด ๐—–๐—ฟ๐—ผ๐˜€๐˜€-๐—ง๐—ฒ๐—ป๐—ฎ๐—ป๐˜ ๐—ฆ๐˜†๐—ป๐—ฐ๐—ต๐—ฟ๐—ผ๐—ป๐—ถ๐˜‡๐—ฎ๐˜๐—ถ๐—ผ๐—ป to support security group synchronization, allowing groups and their memberships to be synchronized between tenants automatically.

๐Ÿค” ๐—ช๐—ต๐˜† ๐˜๐—ต๐—ถ๐˜€ ๐—บ๐—ฎ๐˜๐˜๐—ฒ๐—ฟ๐˜€

Access management is usually driven by groups. The larger the organization, the bigger the problem becomes.

When groups are duplicated across tenants:

– Memberships drift over time

– Offboarding becomes inconsistent

– Access reviews become harder

– Administrators spend time maintaining the same identities multiple times

๐Ÿง  ๐—ช๐—ต๐—ฎ๐˜’๐˜€ ๐—ฟ๐—ฒ๐—ฎ๐—น๐—น๐˜† ๐—ต๐—ฎ๐—ฝ๐—ฝ๐—ฒ๐—ป๐—ถ๐—ป๐—ด

Instead of synchronizing only users, organizations can synchronize selected groups and their memberships. That means when you ๐—ฎ๐—ฑ๐—ฑ ๐—ผ๐—ฟ ๐—ฟ๐—ฒ๐—บ๐—ผ๐˜ƒ๐—ฒ ๐—ฎ ๐˜‚๐˜€๐—ฒ๐—ฟ from the source group, the membership ๐˜‚๐—ฝ๐—ฑ๐—ฎ๐˜๐—ฒ๐˜€ ๐—ถ๐—ป ๐˜๐—ต๐—ฒ ๐˜๐—ฎ๐—ฟ๐—ด๐—ฒ๐˜ ๐˜๐—ฒ๐—ป๐—ฎ๐—ป๐˜. Applications, SharePoint sites, Teams, and other resources can rely on synchronized groups instead of manually maintained copies. Group ๐—บ๐—ฒ๐—บ๐—ฏ๐—ฒ๐—ฟ๐˜€๐—ต๐—ถ๐—ฝ ๐—ถ๐˜€ ๐—บ๐—ฎ๐—ป๐—ฎ๐—ด๐—ฒ๐—ฑ ๐—ถ๐—ป ๐—ผ๐—ป๐—ฒ ๐—ฝ๐—น๐—ฎ๐—ฐ๐—ฒ and propagated to connected tenants.

๐Ÿ› ๏ธ ๐—ช๐—ต๐—ฒ๐—ฟ๐—ฒ ๐—ถ๐˜€ ๐˜๐—ต๐—ถ๐˜€ ๐˜‚๐˜€๐—ฒ๐—ณ๐˜‚๐—น

Even though this is a niche use for most of you, these are places where this comes handy:

– Mergers and acquisitions

– Multi-tenant enterprises

– Subsidiaries with separate tenants

– Shared services organizations

๐Ÿ›ก๏ธ ๐——๐—ผ ๐˜๐—ต๐—ถ๐˜€ ๐—ฏ๐—ฒ๐—ณ๐—ผ๐—ฟ๐—ฒ ๐˜€๐˜†๐—ป๐—ฐ๐—ต๐—ฟ๐—ผ๐—ป๐—ถ๐˜‡๐—ถ๐—ป๐—ด ๐—ด๐—ฟ๐—ผ๐˜‚๐—ฝ๐˜€

– Review which groups are truly authoritative

– Limit synchronization scope

– Monitor privileged groups carefully

– Validate access assignments in target tenants

โš ๏ธ ๐—œ๐—บ๐—ฝ๐—ผ๐—ฟ๐˜๐—ฎ๐—ป๐˜

Synchronizing groups also means ๐˜€๐˜†๐—ป๐—ฐ๐—ต๐—ฟ๐—ผ๐—ป๐—ถ๐˜‡๐—ถ๐—ป๐—ด ๐—บ๐—ถ๐˜€๐˜๐—ฎ๐—ธ๐—ฒ๐˜€. If an incorrect membership grants access in the source tenant, that access may now propagate automatically to other tenants as well.

Treat synchronized groups as a privileged identity management process, not just an administrative convenience.

โœ… This is one of those features that seems insignificant, but can reduce operational overhead in multi-tenant environments while improving consistency and governance.

๐Ÿ’ฌ Question for admins

Is Cross-Tenant Group Synchronization a feature you were waiting for or is it a nice-to-have?

๐˜ˆ๐˜ถ๐˜ต๐˜ฉ๐˜ฐ๐˜ณ ๐˜ฐ๐˜ง ๐˜ต๐˜ฉ๐˜ฆ ๐˜ฑ๐˜ฐ๐˜ด๐˜ต:

Martin Strnad