Org Hierarchy & Folders

Management Groups · OUs · Folders — Azure · AWS · GCP

Concept

The organizational hierarchy divides your cloud footprint into logical units for billing, IAM inheritance, and policy enforcement. All three clouds use a tree structure where policies flow top-down.

○ Azure — Management Groups

Tree: Root MG → Department MGs → Subscriptions. Subscriptions contain Resource Groups. Azure Policy and RBAC inherit downward. Up to 6 levels of MGs.

CLI: az account management-group create --name Dev-MG

○ AWS — Organizations / OUs

Tree: Organization Root → OUs → Accounts. SCPs inherit top-down. Up to 5 levels of OUs. Each account is a billing+security boundary.

CLI: aws organizations create-organizational-unit --parent-id r-xxxx --name Dev

○ GCP — Organization / Folders

Tree: Organization → Folders → Projects. Org Policies and IAM inherit downward. Each project is a namespace+billing boundary.

CLI: gcloud resource-manager folders create --organization=ORG_ID --display-name=dev

Hierarchy Mapping

LayerAzureAWSGCP
Top NodeRoot Management GroupOrganization RootOrganization
Mid TierManagement Group (up to 6)Organizational Unit (up to 5)Folder (up to 10 levels)
Leaf NodeSubscriptionAccountProject
Resource GroupingResource Group(tag-based, flat)(label-based, flat)
Policy InheritanceTop-down (Azure Policy)Top-down (SCPs)Top-down (Org Policies)
IAM InheritanceInherits downwardDoes NOT cross accountsInherits downward
Billing BoundarySubscriptionAccountProject + Billing Account
Max Depth6 MG + Sub + RG5 OU + Account10 Folders + Project

CLI Quick Reference

○ Azure — List hierarchy

az account management-group list
az account list

○ AWS — List hierarchy

aws organizations list-roots
aws organizations list-accounts

○ GCP — List hierarchy

gcloud organizations list
gcloud resource-manager folders list --organization=ORG_ID