Join our Newsletter — 33% off our NHI Course
Home› FAQ› Identity Beyond IAM› What breaks when Azure Entra nested groups are…
Identity Beyond IAM

What breaks when Azure Entra nested groups are synced through SCIM?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 31, 2026 Domain: Identity Beyond IAM

Inherited memberships do not survive the SCIM boundary, so users inside child groups may not be provisioned into the target application. The app receives the direct group membership Entra sends, not a recursive expansion of the directory tree. That can leave users visible in the source directory but absent from access decisions downstream.

Why nested group sync fails at the SCIM boundary

SCIM provisioning is a flat handoff, not a directory-tree replay. The target application receives the direct group memberships Entra sends at sync time, so inherited membership through parent-child nesting is not expanded into downstream access decisions. In practice, that means access that looks correct in Entra can still fail to materialise in the application if the app only evaluates the direct SCIM payload.

This is most visible when teams use nested groups to simplify administration. The hierarchy may be valid inside Entra, but the downstream application usually does not understand the full recursive context unless it has its own nested-group logic. The result is a mismatch between the source-of-truth view and the entitlement model the app actually enforces.

That is why the failure is usually not a broken sync in the narrow sense. The connector can be working as designed, while the application still receives too little information to grant the intended access. For provisioning clarity, the important distinction is between what Entra knows and what the SCIM target can consume.

Where the entitlement gap shows up operationally

The practical symptom is that a user appears correctly assigned in the directory, but never lands in the target application's access set. This often surfaces as missing roles, empty teams, or failed onboarding in SaaS tools that rely on SCIM groups for authorization. When that happens, the source directory is not wrong, but the provisioning model is incomplete for the application's expectations.

The gap is especially easy to miss when administrators test with direct group assignments first. Direct membership will usually sync as expected, which can create false confidence. The break only appears once access depends on a nested structure, at which point the downstream application has no recursive expansion to work with.

In larger environments, this can also distort troubleshooting. Operators may inspect the directory, see the user in the right parent group, and assume the access issue lies elsewhere. A better diagnostic is to compare the direct membership list delivered by SCIM with the exact entitlement rule the application uses.

For related provisioning patterns and common SCIM failure modes, the SCIM and Automated Provisioning Guide covers what SCIM does and does not carry across the boundary.

How to redesign provisioning so access stays predictable

The safest pattern is to treat SCIM as a transport for explicit entitlements, not as a mechanism for preserving directory hierarchy. If an application must receive a user's access through SCIM, send the direct group or role assignment that the application can actually evaluate. Do not assume child-group membership will be expanded unless the vendor documents that behaviour.

Where nested groups are already part of your directory design, verify which tier of membership each downstream system consumes. Some applications can interpret group membership only one level deep, while others ignore nesting entirely. The control objective is consistency, not elegance: the access path should be obvious to both the provisioning system and the application owner.

When the hierarchy is used to model business structure, it is often better to flatten the entitlement handoff at the application boundary and preserve nesting only inside Entra for administration. That keeps the source directory flexible without depending on a downstream app to perform recursive group resolution it may not support.

Risk and Threat Considerations

Nested-group sync failures create a blind spot between source-directory intent and downstream access reality. That can leave users under-provisioned, over-provisioned, or inconsistently provisioned across applications, especially when access reviews rely on the directory view rather than the entitlement actually enforced by the app.

Failure mechanism: SCIM transmits direct memberships only, so nested membership is lost at the boundary and the application never sees the inherited entitlement path.

Impact: Users may miss required access at onboarding, or auditors may wrongly assume access exists because it appears in Entra but not in the consuming application.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5, CSA Cloud Controls Matrix and NIST CSF 2.0 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementSCIM provisioning issues often require controlling lifecycle and validity of provisioning credentials.
AC-2 — Account ManagementThe question is about how accounts and memberships are provisioned across a directory boundary.
Recommendation — Protect provisioning tokens and rotate them when SCIM integrations or admin access change. Define explicit provisioning rules for which groups or roles are assigned directly to target applications.
CSA Cloud Controls MatrixIAM — Identity and Access ManagementCloud app provisioning and group-to-role mapping are core IAM control concerns.
Recommendation — Document how each cloud application consumes group membership and whether nesting is supported.
NIST CSF 2.0PR.AA-05 — Identity Management, Authentication, and Access ControlThe issue changes how access is granted and enforced across systems.
Recommendation — Validate that downstream access decisions use the same entitlement model as the source directory.
ISO/IEC 27001:2022A.5.16 — Identity managementThe answer concerns identity provisioning and how access is represented across systems.
Recommendation — Record identity and group provisioning rules so access is assigned consistently across applications.

Practitioner Guidance

What to verify: Confirm whether each SCIM target consumes direct groups only, supports nested expansion, or expects role mapping instead of group inheritance. Test with one nested parent-child path before you rely on it in production.

Decision rule: If the application cannot prove recursive resolution in its own provisioning documentation, flatten the entitlement model at the SCIM boundary and assign access explicitly to the groups the app actually reads.

Practitioner takeaway: Treat Entra nesting as an administrative convenience, not as a portable authorization model, unless the downstream application explicitly preserves the inheritance semantics.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org