# Test permission and policy changes in a dry run before enforcing them

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

Check 25 of 30: Test permission and policy changes in a dry run before enforcing them. A new deny or boundary can break an agent's tools in ways nobody saw coming, and a mistaken allow can open access without anyone noticing. Testing first shows the effect before it reaches production.

## Why it matters

A new deny or boundary can break an agent's tools in ways nobody saw coming, and a mistaken allow can open access without anyone noticing. Testing first shows the effect before it reaches production.

## How, in each cloud

- **AWS:** Use the IAM policy simulator to test identity-based policies.
- **Google Cloud:** Use organization policies in dry-run mode to monitor how a policy would behave.
- **Azure:** Assign Azure Policy with enforcementMode DoNotEnforce.

## What the documentation says

- "With the IAM policy simulator, you can test identity-based policies," ([source](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_testing-policies.html))
- "This page shows how to use an organization policy in dry-run mode to monitor how" ([source](https://cloud.google.com/resource-manager/docs/organization-policy/dry-run-policy))
- "The enforcementMode property provides customers the ability to control the outcome of a policy on existing resources without initiating the policy effect" ([source](https://learn.microsoft.com/en-us/azure/governance/policy/concepts/assignment-structure))

- [Previous: Tag every agent resource with an owner and environment, and enforce the tags](/checklist/tag-agent-resources/)
- [Next: Remove the agent's identity and access when the agent is retired](/checklist/retire-identity-with-agent/)

## Related pages

- [Remove the agent's identity and access when the agent is retired: the check, and how in AWS, Google Cloud and Azure](/checklist/retire-identity-with-agent/)
- [Turn on organization-wide audit logging of control-plane actions: the check, and how in AWS, Google Cloud and Azure](/checklist/control-plane-audit-logs/)
- [Log reads and writes to the data the agent touches: the check, and how in AWS, Google Cloud and Azure](/checklist/log-data-access/)

## Sources

- docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_testing-policies.html: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_testing-policies.html (read 10 Nov 2026)
- cloud.google.com/resource-manager/docs/organization-policy/dry-run-policy: https://cloud.google.com/resource-manager/docs/organization-policy/dry-run-policy (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/governance/policy/concepts/assignment-structure: https://learn.microsoft.com/en-us/azure/governance/policy/concepts/assignment-structure (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/checklist/test-before-enforcing/
