Skip to content
Cloud Governance Tools

Organization Policy Service (managed and legacy constraints): what it can block and where it stops

Organization Policy Service (managed and legacy constraints) is a Google Cloud mechanism. Organization policies set restrictions on Google Cloud resources by enforcing a constraint on an organization, folder or project. It applies to resources in the organization, folder or project where the policy is set and its descendants; Google says application of new policies is usually not retroactive.

All mechanisms ยท Google Cloud guardrails

Organization policies set restrictions on Google Cloud resources by enforcing a constraint on an organization, folder or project. Descendants inherit the policy by default and can override it, subject to the constraint type.

Organization policies set restrictions on Google Cloud resources by enforcing a constraint on an organization, folder or project. Descendants inherit the policy by default and can override it, subject to the constraint type. The policy applies to resources in the node where it is set and its descendants.

Limits: new organization policies are usually not retroactive, so existing violations are not stopped; managed constraints inherited from a parent are not merged; and dry-run mode is limited to custom constraints, managed constraints and a short list of legacy managed constraints. Policy Simulator cannot test changes to legacy managed constraints. 25 library entries use organization policy constraints.

Documented limits

  • New organization policies are usually not retroactive: existing violations are not stopped. (source)
  • Dry-run mode is limited to custom constraints, managed constraints and a short list of legacy managed constraints. (source)
  • Managed constraints inherited from a parent are not merged to evaluate the effective policy. (source)
  • Policy Simulator cannot test changes to legacy managed constraints. (source)

Testing before enforcement

Google documents organization policies in dry-run mode (violations are audit logged, not denied) and Policy Simulator for Organization Policy; legacy managed constraints are mostly excluded from both. (source)

The 25 library entries written in it

Where Act is behind

Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.

Sources

  1. Organization Policy Service (managed and legacy constraints), read 10 Nov 2026
  2. Limit, read 10 Nov 2026
  3. Limit, read 10 Nov 2026

Last reviewed 16 Nov 2026.