Skip to content
Cloud Governance Tools

Organization integrity guardrails protect the structure of the account tree, and apply to everyone

9 guardrails in the library address organization integrity: 3 AWS, 3 Azure, 3 Google Cloud. The first in the list, "Deny member accounts leaving the organization", denies organizations:LeaveOrganization so users and roles in affected member accounts cannot remove their account from the AWS organization.

All risk classes ยท Download the library

Guardrails in this class protect accounts, billing and the resource tree: leaving the organization, closing accounts, changing contacts, deleting resources and locking them. The library holds 9. Several apply to every principal. The leave-organization SCP has no exception condition, so it applies to every user, role and the root user in affected member accounts. Azure's ReadOnly lock on a resource group with a virtual machine prevents starting or restarting it, because those operations use POST. The denyAction effect does not stop removal of child and extension resources when a delete targets the parent.

"Tested first" says whether the provider documents a way to see the guardrail's effect before enforcing it. Read 10 Nov 2026.
GuardrailCloudMechanismRisk classTested first
Deny member accounts leaving the organizationAWSService control policies (SCPs)Organization integritydocumented
Deny billing, tax and account contact changesAWSService control policies (SCPs)Organization integritydocumented
Restrict access to resources in a suspended OUAWSResource control policies (RCPs)Organization integritydocumented
Do not allow deletion of resource typesAzureAzure Policy (built-in definitions)Organization integritydocumented
Deployment stack deny settings (Azure RBAC deny assignment)AzureAzure RBAC deny assignments (created by deployment stacks)Organization integritynone found
Resource locks (CanNotDelete and ReadOnly)AzureAzure resource locksOrganization integritynone found
Restrict resource service usageGoogle CloudOrganization Policy Service (managed and legacy constraints)Organization integritydocumented
Restrict Shared VPC host project lien removalGoogle CloudOrganization Policy Service (managed and legacy constraints)Organization integritynone found
Deny deleting projects tagged prodGoogle CloudIAM deny policiesOrganization integritydocumented

What these guardrails break

  • Deny member accounts leaving the organization (AWS): The policy has no exception condition, so it applies to every IAM user, role and the root user in the affected member accounts; AWS documents that SCPs do not affect the management account.
  • Deny billing, tax and account contact changes (AWS): Finance or account teams working outside the privileged role cannot change the payment method, tax preferences or contact information; account:CloseAccount is also denied for other roles.
  • Restrict access to resources in a suspended OU (AWS): AWS service principals are exempt by default; the README says to remove the aws:PrincipalIsAWSService condition if you also want to restrict security or logging services.
  • Do not allow deletion of resource types (Azure): The denyAction effect does not stop removal of child and extension resources when a delete targets the parent, and only supports the DELETE action.
  • Deployment stack deny settings (Azure RBAC deny assignment) (Azure): The deny setting applies only to resources the stack defines explicitly, not to resources created implicitly, and you can exclude at most five principals.
  • Resource locks (CanNotDelete and ReadOnly) (Azure): A read-only lock on a resource group that contains a virtual machine prevents all users from starting or restarting it, because those operations use POST requests.
  • Restrict resource service usage (Google Cloud): Google documents that services with a direct dependency on a restricted service are restricted too, for example GKE when Compute Engine is restricted.
  • Restrict Shared VPC host project lien removal (Google Cloud): Google documents that the permission to remove the lien must be granted at the organization level once enforced.
  • Deny deleting projects tagged prod (Google Cloud): Google documents that the denial condition must use the CEL functions for evaluating resource tags, and other functions and operators are not supported.

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. Deny member accounts leaving the organization, read 10 Nov 2026
  2. Deny billing, tax and account contact changes, read 10 Nov 2026
  3. Restrict access to resources in a suspended OU, read 10 Nov 2026
  4. Do not allow deletion of resource types, read 10 Nov 2026
  5. Deployment stack deny settings (Azure RBAC deny assignment), read 10 Nov 2026
  6. Resource locks (CanNotDelete and ReadOnly), read 10 Nov 2026
  7. Restrict resource service usage, read 10 Nov 2026
  8. Restrict Shared VPC host project lien removal, read 10 Nov 2026

Last reviewed 16 Nov 2026.