# Run agents in their own account, project or subscription

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

Check 23 of 30: Run agents in their own account, project or subscription. Agents placed beside production workloads share their blast radius, quotas and admin rights. A dedicated container lets you apply stricter policy and limits and remove it cleanly.

## Why it matters

Agents placed beside production workloads share their blast radius, quotas and admin rights. A dedicated container lets you apply stricter policy and limits and remove it cleanly.

## How, in each cloud

- **AWS:** Use separate AWS accounts to isolate workloads.
- **Google Cloud:** Use a separate project, grouped under folders in the resource hierarchy.
- **Azure:** Use a separate subscription, grouped under management groups.

## What the documentation says

- "Using multiple AWS accounts to help isolate and manage your business" ([source](https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/organizing-your-aws-environment.html))
- "projects. Structuring your resources this way helps you centralize asset" ([source](https://cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy))
- "Subscriptions are a unit of management, billing, and scale within Azure." ([source](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/design-area/resource-org-subscriptions))

- [Previous: Decide for each tool whether the action runs with the agent's authority or the signed-in user's](/checklist/decide-user-or-agent-authority/)
- [Next: Tag every agent resource with an owner and environment, and enforce the tags](/checklist/tag-agent-resources/)

## Related pages

- [Tag every agent resource with an owner and environment, and enforce the tags: the check, and how in AWS, Google Cloud and Azure](/checklist/tag-agent-resources/)
- [Test permission and policy changes in a dry run before enforcing them: the check, and how in AWS, Google Cloud and Azure](/checklist/test-before-enforcing/)
- [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/)

## Sources

- docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/organizin: https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/organizing-your-aws-environment.html (read 10 Nov 2026)
- cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy: https://cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/desi: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/design-area/resource-org-subscriptions (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/checklist/dedicated-account-project-subscription/
