M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Source of authority (SOA)

Concept

In hybrid identity, the source of authority is the directory that has final say over an object's identity attributes. Microsoft Entra ID can take over the source of authority for synced groups and users from on-premises Active Directory.

✦ CONCEPTSource of authority(SOA)M365.FM
Title graphic: Source of authority (SOA) (Concept)

Also discussed

Episodes about Source of authority (SOA) also cover Group writeback, Access reviews, Microsoft Entra Connect, Active Directory, Microsoft Entra and Microsoft Entra ID.

Description

Source of authority (SOA) is a concept in hybrid identity. It describes which directory holds final say over an object's identity attributes. In a hybrid setup, an object such as a user or a group may appear in both on-premises Active Directory and Microsoft Entra ID, but only one of the two is the place where it is authoritatively created, changed and deleted. Microsoft Entra ID can take over the source of authority for synced groups and users from on-premises Active Directory, which moves day-to-day management of those objects to the cloud.

The topic matters because objects that are synced to Entra ID but still ruled by on-premises Active Directory can be limited in what the cloud can do with them. The episode "Use Entra ID Group Writeback for Legacy File Servers" describes such objects as "zombies": visible in Entra but governed on-premises, which it says blocks modern governance such as dynamic membership, access reviews and APIs, and slows HR-driven provisioning. The episode's recommendation is to decide the source of authority per object rather than treating the whole directory the same way. Groups that matter to cloud workloads should be cloud-managed, while Group Writeback is used only where legacy systems still need on-premises visibility.

The Microsoft Entra documentation on group source of authority describes the mechanism for groups. Converting the source of authority of a group allows its management to move from Active Directory Domain Services to the cloud. The stated aims are more flexibility, modern governance and simpler administration. After conversion, security groups are managed in the Microsoft Entra admin center and through Microsoft Graph. The episode refers to this state as cloud-managed, using the isCloudManaged property.

Cloud-managed groups do not have to disappear from on-premises Active Directory. According to the documentation, they can be provisioned back to AD DS using Microsoft Entra Cloud Sync. This requires steps such as setting the group scope to universal and mapping the distinguished name through a directory extension. This pattern fits legacy file servers and other on-premises applications that still read group membership from Active Directory while administrators manage the group in the cloud. Typical uses listed in the documentation include cleaning up groups in AD that are no longer needed, moving distribution lists and mail-enabled security groups to Microsoft 365 groups, and writing Microsoft 365 groups back to AD for on-premises apps.

The documentation also names several limits that affect planning. The change applies only to the named group and is not recursive, so nested groups stay on-premises unless each one is converted individually. Local edits made to a cloud-managed group in Active Directory are overwritten at the next provisioning run. Dynamic membership rules are not carried over, and a custom LDAP connector is not supported. Security-enabled Microsoft 365 groups cannot be used to grant Exchange shared mailbox permissions. Rollback is only possible when the object's original authority was Active Directory.

The path outlined in the episode begins with an inventory: identify which groups exist, purge the "zombie" groups that are no longer needed, and classify what should stay on-premises and what should move. Together with the documentation, this gives a practical sequence for decisions around SOA: choose the authoritative directory per object, convert where cloud governance is needed, write back only for legacy dependencies, and account for the non-recursive scope and overwrite behavior before changing nested or heavily used groups.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept
DocumentationSource of authority (SOA) – Microsoft Learn learn.microsoft.com

Key points about Source of authority (SOA)

Key points about Source of authority (SOA) from the episodes, each with its source episode:

Episodes about Source of authority (SOA)

Episodes in which Source of authority (SOA) is discussed:

Timeline of episodes about Source of authority (SOA)

Articles about Source of authority (SOA) (2)

Articles in which Source of authority (SOA) is a topic:

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What does source of authority mean in hybrid identity? (AI)

It is the directory that has final say over an object's identity attributes. Microsoft Entra ID can take over the source of authority for synced groups and users from on-premises Active Directory.

Is a source of authority change applied to nested groups automatically? (AI)

No. According to the documentation, the change applies only to the named group and is not recursive, so nested groups stay on-premises unless each is converted individually.

Can a cloud-managed group still be used by on-premises applications? (AI)

Yes. Cloud-managed groups can be provisioned back to AD DS with Microsoft Entra Cloud Sync, which requires steps such as universal group scope and a directory extension mapping for the distinguished name.

What is Source of Authority in AD and Entra ID?

It defines which directory actually owns your users and groups. The episode explains it because dual ownership causes mismatched policies and sync drift. · From the episode: Move Active Directory Groups to Microsoft Entra ID

What is Source of Authority for Entra ID groups?

It states where an object is managed. Groups that matter for cloud workloads should be cloud-managed, so that modern governance such as dynamic rules and access reviews can apply. · From the episode: Use Entra ID Group Writeback for Legacy File Servers

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: