Multi cloud governance for security means running three hierarchies and three policy mechanisms side by side
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
AWS, Azure and Google Cloud each organize accounts in a hierarchy and attach guardrails to it: AWS Organizations with SCPs and RCPs, Azure management groups with Azure Policy, Google Cloud folders with organization policy. The vocabulary, the dry-run options and the exception models differ in each, as read on 16 Nov 2026.
Each cloud attaches guardrails to a different container
AWS documentation says Organizations lets you group accounts and apply policies for governance, and it calls accounts natural boundaries for permission, security, costs and workloads. Microsoft says management groups give a governance scope above subscriptions, and that a policy applied to a management group reaches all nested groups, subscriptions and resources. Google says its hierarchy of organizations, folders and projects carries inherited access control and organization policies.
| Question | AWS | Azure | Google Cloud |
|---|---|---|---|
| Container that carries the guardrail | Root, OU or account | Management group or subscription | Organization, folder or project |
| Main preventive mechanisms | SCP, RCP, declarative policy | Azure Policy, deny assignments | Organization policy, IAM deny, VPC Service Controls |
| Library entries on this site | 40 | 30 | 30 |
| Documented way to try before enforcing | Test in a separate OU; IAM policy simulator for SCPs | enforcementMode DoNotEnforce | Organization policy in dry-run mode |
| Depth limit documented | None found in the pages read | Six levels, excluding root and subscription | None found in the pages read |
The same intent needs a different object in each cloud
Restricting locations shows the gap. AWS uses a service control policy with an aws:RequestedRegion condition, as in Deny access outside approved Regions. Azure uses a policy definition, as in Allowed locations for new resources. Google uses a constraint, as in Resource location restriction.
The failure modes differ too. The AWS example breaks global services missing from its exemption list. The Azure definition excludes resource groups and resources in the global region. The Google constraint treats a multi-region deny as separate from its sub-locations, so a deny of the us multi-region still allows us-east1.
Inheritance works downward in all three, with different merge rules
AWS documentation shows that when SCPs are stacked, the more restrictive root policy takes precedence, so the effective permission is the intersection of every level. Microsoft recommends limiting the number of Azure Policy assignments at the root management group, because inherited policies are harder to debug in lower groups. Google lets a child policy merge with its parent or replace it, depending on the inheritFromParent setting.
The practical result is that a guardrail written high in one cloud can be loosened lower in another. In Google Cloud and Azure a lower scope can override or exempt. In AWS an SCP can only narrow what is allowed, so loosening needs an exception condition in the policy itself or a change higher up.
Dry-run support is the least even feature across the three
Microsoft documents DoNotEnforce as a way to evaluate an assignment before enforcement. Google documents dry-run mode, where violations are audit logged but not blocked, and limits it to certain constraint types. For SCPs, AWS documents the IAM policy simulator and recommends a small OU first. A dry-run mode for SCPs: none found in the AWS pages read on 10 Nov 2026.
This is the gap the Simulation Coverage Matrix records for the platforms that sit on top of the three clouds. The multi-cloud situation ranking weights it, and the method lists the weights.
A cross-cloud rulebook is a table of equivalents, not one policy
No page read on 16 Nov 2026 describes a single policy file that all three clouds enforce natively. Teams that want one rulebook keep a list of intents (no public storage, approved Regions, no long-lived keys) and map each to the native object per cloud, or add an external engine; see policy as code tools for the engines.
Related pages
Sources
- AWS Organizations: what is AWS Organizations, read 16 Nov 2026
- Microsoft: management groups overview, read 16 Nov 2026
- Google Cloud: resource hierarchy, read 16 Nov 2026
- Microsoft: management groups in Azure landing zones, read 16 Nov 2026
- Microsoft: Azure Policy assignment structure, read 16 Nov 2026
- Google Cloud: test organization policies in dry-run mode, read 16 Nov 2026
- AWS Organizations: SCP strategies, read 16 Nov 2026
- Google Cloud: hierarchy evaluation, read 16 Nov 2026
Last reviewed 16 Nov 2026.