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

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

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.

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.

| Guardrail | Cloud | Mechanism | Risk class | Tested first |
| --- | --- | --- | --- | --- |
| [Deny member accounts leaving the organization](/guardrails/aws-scp-deny-leave-org/) | AWS | [Service control policies (SCPs)](/mechanisms/scp/) | Organization integrity | documented |
| [Deny billing, tax and account contact changes](/guardrails/aws-scp-deny-billing-and-contact-changes/) | AWS | [Service control policies (SCPs)](/mechanisms/scp/) | Organization integrity | documented |
| [Restrict access to resources in a suspended OU](/guardrails/aws-rcp-restrict-suspended-ou-resources/) | AWS | [Resource control policies (RCPs)](/mechanisms/rcp/) | Organization integrity | documented |
| [Do not allow deletion of resource types](/guardrails/azure-policy-deny-action-delete/) | Azure | [Azure Policy (built-in definitions)](/mechanisms/azure-policy/) | Organization integrity | documented |
| [Deployment stack deny settings (Azure RBAC deny assignment)](/guardrails/azure-deny-assignment-deployment-stack/) | Azure | [Azure RBAC deny assignments (created by deployment stacks)](/mechanisms/rbac-deny-assignment/) | Organization integrity | none found |
| [Resource locks (CanNotDelete and ReadOnly)](/guardrails/azure-lock-cannotdelete-readonly/) | Azure | [Azure resource locks](/mechanisms/resource-lock/) | Organization integrity | none found |
| [Restrict resource service usage](/guardrails/gcp-orgpolicy-restrict-service-usage/) | Google Cloud | [Organization Policy Service (managed and legacy constraints)](/mechanisms/org-policy/) | Organization integrity | documented |
| [Restrict Shared VPC host project lien removal](/guardrails/gcp-orgpolicy-restrict-xpn-lien-removal/) | Google Cloud | [Organization Policy Service (managed and legacy constraints)](/mechanisms/org-policy/) | Organization integrity | none found |
| [Deny deleting projects tagged prod](/guardrails/gcp-deny-project-delete-prod/) | Google Cloud | [IAM deny policies](/mechanisms/iam-deny/) | Organization integrity | documented |

"Tested first" says whether the provider documents a way to see the guardrail's effect before enforcing it. Read 10 Nov 2026.

## 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.

## Related pages

- [AI services: 19 preventive guardrails across three clouds](/risk/ai-services/)
- [Resource and cost: 7 preventive guardrails across three clouds](/risk/resource-and-cost/)
- [Identity and privilege: 14 preventive guardrails across three clouds](/risk/identity-and-privilege/)

## Sources

- Deny member accounts leaving the organization: https://raw.githubusercontent.com/aws-samples/service-control-policy-examples/main/Privileged-access-controls/Deny-member-accounts-from-leaving-your-AWS-organization.json (read 10 Nov 2026)
- Deny billing, tax and account contact changes: https://raw.githubusercontent.com/aws-samples/service-control-policy-examples/main/Privileged-access-controls/Deny-billing-modification-action.json (read 10 Nov 2026)
- Restrict access to resources in a suspended OU: https://raw.githubusercontent.com/aws-samples/resource-control-policy-examples/main/Establish-intra-organization-boundaries/Deny-resource-access-if-the-resource-belongs-to-a-specific-organizational-unit.json (read 10 Nov 2026)
- Do not allow deletion of resource types: https://raw.githubusercontent.com/Azure/azure-policy/master/built-in-policies/policyDefinitions/General/ResourceType_denyActionDelete.json (read 10 Nov 2026)
- Deployment stack deny settings (Azure RBAC deny assignment): https://learn.microsoft.com/en-us/azure/role-based-access-control/deny-assignments (read 10 Nov 2026)
- Resource locks (CanNotDelete and ReadOnly): https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources (read 10 Nov 2026)
- Restrict resource service usage: https://cloud.google.com/resource-manager/docs/organization-policy/restricting-resources (read 10 Nov 2026)
- Restrict Shared VPC host project lien removal: https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/risk/organization-integrity/
