Guides for the agent approval meeting
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Guides on putting an AI agent into production in AWS, Azure and Google Cloud, written from the same provider pages as the map. Each guide lists its sources with the date it was read and ends with the checklist items it closes.
- The identity an AI agent runs as in AWS, Google Cloud and AzureWhich identity the agent presents on each platform, and the three checks to run before reading any permissions.
- Why an AI agent's permissions are not its user's permissionsAgent authority against user authority: where each platform documents the choice, and the question to put to the builder.
- Network reachability for AI agents on AWS, Google Cloud and AzurePrivate endpoints, VPC attachment and outbound filtering for agents, with each provider's documented defaults.
- Logging what an AI agent did: audit, data and model logsControl-plane, data and agent-trace logs on each cloud: what is on by default, what is not, and what names the agent.
- AI agent permissions: how to cut an agent's accessWrite the policy from real tool calls, set a ceiling, trim with usage data, and test before enforcing.
- Amazon Bedrock agent permissions: roles, trust and what the console createsService role, execution role, trust policy and what the console creates for Agents Classic and AgentCore.
- Vertex AI agent service account: Agent Runtime identities in Google CloudAgent Runtime formerly Vertex AI Agent Engine: agent identity, service agent and service account compared.
- What can an AI agent access in AWS: the four layers to readThe four layers to read to answer what an agent can reach in AWS, in the order to read them.
- Approving an AI agent for production: running the review meetingHow to run the review meeting with the Agent Boundary Checklist: pre-read, agenda, scoring and the decisions to record.
- AI agent permissions in Azure: Foundry Agent Service, identities and RBACFoundry Agent Service identities, managed identities and the RBAC roles that decide what an Azure agent can reach.
- AI agent authorization in AWS, Azure and Google CloudThe three inputs to an authorization decision for an agent, in each cloud, with the provider's own wording.
- AI agent guardrails: SCPs, Azure Policy and org policyThe access-layer guardrails for an agent in each cloud, and the one layer this site leaves out.
- AI access control in cloud accounts: roles, policy, networkAccess control for AI workloads in cloud accounts, layer by layer, without the model-side controls.
- Agent authorization patterns: five ways to scope an agentFive patterns, each with the mechanism and the provider page that documents it.
- Amazon Q Business default permissions: roles it createsThe roles the Amazon Q Business console creates, what each reaches, and how to narrow them.
- Copilot Studio default permissions: tool authenticationWhich credential a Copilot Studio agent's tools use, what that reaches, and the admin controls that narrow it.
- Azure OpenAI Assistants default permissions and accessWhat an Azure OpenAI assistant can reach by default, who can call it, and how to narrow it before migrating.
- Conversational Agents (Dialogflow CX) default permissionsWho can reach a Dialogflow CX agent by default, and which identity its tools and webhooks use.
Related pages
Last reviewed 16 Nov 2026.