# Only Azure documents an exception object with an expiry date; AWS and Google Cloud exceptions need an expiry built around them

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

Azure Policy exemptions carry a category, an optional expiresOn date and free-form metadata. AWS exceptions are conditions inside the policy, such as a principal tag in an SCP. Google Cloud exceptions are overrides at a folder or project. An expiry field for the last two: none found on 16 Nov 2026.

## AWS exceptions are conditions inside the policy, so ending one means editing the policy

The AWS sample service control policy [Deny critical IAM user actions](/guardrails/aws-scp-deny-critical-iam-user-actions/) denies IAM user creation, access keys and login profiles unless the caller is a named role or carries a principal tag. The exception is the Condition block below, copied from the aws-samples repository (MIT-0 license), with indentation removed.

- `"Condition": {`
- `"ArnNotLike": { "aws:PrincipalArn": "arn:aws:iam::*:role/[PRIVILEGED_ROLE]" },`
- `"StringNotLike": { "aws:PrincipalTag/IAMUserManagementException": "true" }`
- `}`

## AWS Control Tower adds exemption parameters per OU, with no expiry field found

AWS Control Tower documentation shows configurable controls that accept ExemptedPrincipalArns and ExemptedActions parameters, set when the control is enabled on an OU. The pages read list no expiry or approval field for either parameter: none found on 10 Nov 2026. An exception through the tag route lasts as long as the tag stays on the principal. The [Control Tower controls page](/aws-control-tower-guardrails/) covers the catalog.

## Azure exemptions are separate objects with a category, an expiry and a record

Microsoft documents a policy exemption as a child object on the resource hierarchy or resource it covers. Its fields include a policy assignment ID, optional policy definition reference IDs (to exempt only some definitions in an initiative), an exemption category, an optional expiresOn date and a free-form metadata block. Microsoft gives requestedBy, approvedBy, approvedOn and ticketRef as example metadata keys.

The two categories are Mitigated (the policy intent is met another way) and Waiver (non-compliance is temporarily accepted). When expiresOn passes, the exemption object is kept for record-keeping but is no longer honored. Microsoft says exempt resources count toward overall compliance but are not evaluated, or hold a temporary waiver. See [Azure Policy as a guardrail](/guides/azure-policy-as-a-guardrail/) and the [policy exemption](/glossary/policy-exemption/) entry.

## Google Cloud exceptions are overrides at a lower node or tag conditions, with a delay

Google documents that a project can override an inherited boolean organization policy by setting a policy that disables enforcement for that project. The YAML Google gives for that override is shown below, with indentation removed.

- `name: projects/PROJECT_ID/policies/CONSTRAINT_NAME`
- `spec:`
- `rules:`
- `- enforce: false`

| Cloud | Exception object | Scope | Expiry field | Record of the reason |
| --- | --- | --- | --- | --- |
| AWS SCP | Condition on principal ARN or tag | The attached OU, account or root | None found in the SCP samples read | Kept outside the policy |
| AWS Control Tower | ExemptedPrincipalArns and ExemptedActions | The OU | None found on 10 Nov 2026 | None found on 10 Nov 2026 |
| Azure Policy | policyExemptions child object | Resource hierarchy or one resource | expiresOn, optional | metadata block and exemptionCategory |
| Google Cloud | Override at folder or project; tag-conditional enforcement | The folder or project | None found on 16 Nov 2026 | None found on 16 Nov 2026 |

## Expiry for AWS and Google Cloud has to be built, and timing matters

Google states that changes to organization policies can take up to 15 minutes to be fully enforced, so an exception that is lifted is not lifted at once. Google also documents tag-based conditions, which allow or deny a policy depending on whether a resource has a specific tag. Tags on organization, folder or project resources work with any constraint type, and tags on service resources such as Compute Engine instances work with managed or custom constraints.

A review job that lists tagged principals or project-level overrides and removes stale ones is the usual stand-in for an expiry field. For how to stage exceptions during a rollout, read [rolling out guardrails without breaking production](/guides/rolling-out-guardrails-without-breaking-production/), and see the [library](/library/) for the breakage each guardrail records.

## Related pages

- [Landing zone guardrails for AWS: the Control Tower baseline](/landing-zone-guardrails-aws/)
- [Azure landing zone guardrails: policy by management group](/landing-zone-guardrails-azure/)
- [What is policy as code? Definition and where it runs](/what-is-policy-as-code/)
- [All of them](/guides/)

## Sources

- AWS samples: Deny-critical-IAM-user-actions.json (MIT-0): https://raw.githubusercontent.com/aws-samples/service-control-policy-examples/main/Privileged-access-controls/Deny-critical-IAM-user-actions.json (read 10 Nov 2026)
- AWS Control Tower: enable controls with CloudFormation: https://docs.aws.amazon.com/controltower/latest/userguide/enable-controls.html (read 10 Nov 2026)
- Microsoft: Azure Policy exemption structure: https://learn.microsoft.com/en-us/azure/governance/policy/concepts/exemption-structure (read 16 Nov 2026)
- Google Cloud: using constraints: https://cloud.google.com/resource-manager/docs/organization-policy/using-constraints (read 16 Nov 2026)
- Google Cloud: scope organization policies with tags: https://cloud.google.com/resource-manager/docs/organization-policy/tags-organization-policy (read 16 Nov 2026)
- Google Cloud: hierarchy evaluation: https://cloud.google.com/resource-manager/docs/organization-policy/understanding-hierarchy (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/guardrail-exceptions-and-waivers/
