Skip to content
AI Agent Access Control

Run agents in their own account, project or subscription

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.

The whole checklist ยท The map

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)
  • "projects. Structuring your resources this way helps you centralize asset" (source)
  • "Subscriptions are a unit of management, billing, and scale within Azure." (source)

Sources

  1. docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/organizin, read 10 Nov 2026
  2. cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy, read 10 Nov 2026
  3. learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/desi, read 10 Nov 2026

Last reviewed 16 Nov 2026.