# A Copilot Studio agent reaches data through the credential each tool uses, either the maker's or the signed-in user's

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

In Microsoft Copilot Studio an agent's reach depends on how each tool authenticates: agent author authentication, which Microsoft recommends for low-risk or implicit access, or user authentication, which uses the signed-in user's connection. Microsoft documents data policies in the Power Platform admin center as the admin control. Documentation read on 16 Nov 2026.

## Copilot Studio is a low-code builder, so the identity is per tool

Microsoft describes Copilot Studio as a graphical, low-code studio for building and managing AI agents and workflows, which you connect to your organization's data and systems and publish to channels such as Microsoft Teams ([Microsoft: Copilot Studio overview](https://learn.microsoft.com/en-us/microsoft-copilot-studio/fundamentals-what-is-copilot-studio), read 16 Nov 2026). Unlike a Bedrock or Foundry agent, there is no single execution role or service principal in the documentation pages read. The credential is chosen on each tool.

Microsoft also documents that some agents can be given their own account, and that for organizations that onboard Microsoft Agent 365, Copilot Studio agents can be represented as identities in Microsoft Entra and governed with Conditional Access and role-based and attribute-based access controls. The default identity before onboarding Agent 365: none found on 16 Nov 2026 in the pages read.

## The two authentication choices for a tool

| Choice | What Microsoft documents | What it reaches |
| --- | --- | --- |
| Agent author authentication | For access to the service that is implicit or for low-risk use cases, such as a weather API | Whatever the credential supplied for the agent can reach, for every user who talks to the agent (a reading of the name, not a Microsoft statement) |
| User authentication | For restricting data access to specific groups or individuals, or doing work on the user's behalf | Only what the signed-in user's connection can reach; Copilot Studio checks for a valid connection and shows a connection card if none exists |

## The default posture

Microsoft lists, among its security and governance controls, that makers can configure tools to use the user's credentials by default ([Microsoft: security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance)). It lists makers' security warnings when default configurations are modified, and an automatic security scan with real-time risk assessment while configuring knowledge, tools and actions. The exact default selection for a new tool: none found on 16 Nov 2026 in the pages read, so read it in each tool's settings.

The practical reading: an agent author tool is a shared credential. It behaves like a service account that every chat user borrows. A user authentication tool carries the user's own reach, which is the pattern in [why an agent's permissions are not its user's](/guides/why-an-agents-permissions-are-not-its-users/).

## How an administrator narrows it

- Data policies in the Power Platform admin center govern maker and user authentication, knowledge sources, actions and connectors, HTTP requests, publication to channels and triggers, per Microsoft's list.
- Environment routing gives makers a separate environment to build in.
- The tenant admin can disable the publishing of agents that use generative AI features.
- Audit logs for maker activity are available in Microsoft Purview, and activity alerts in Microsoft Sentinel.
- With Agent 365, Microsoft documents Entra network egress and ingress controls for Copilot Studio agents.

## What this page leaves out

User authentication for tools is supported on some channels only; Microsoft lists Teams, SharePoint, a custom website and Omnichannel live chat as supported, and Azure Bot Service channels, the demo website, Facebook and the mobile app as not supported ([Microsoft: user authentication for tools](https://learn.microsoft.com/en-us/microsoft-copilot-studio/configure-enduser-authentication)). On an unsupported channel a tool cannot use the user's own connection, which pushes it toward a maker credential. Copilot Studio reaches Azure resources only through connectors, so the checks in [the Azure cloud page](/clouds/azure/) apply to the identity behind each connector. Compare the Foundry model on [the Foundry Agent Service page](/agent-platforms/foundry-agent-service/).

## Related pages

- [Azure OpenAI Assistants default permissions and access](/default-permissions/azure-openai-assistants/)
- [Conversational Agents (Dialogflow CX) default permissions](/default-permissions/conversational-agents/)
- [The identity an AI agent runs as in AWS, Google Cloud and Azure](/guides/the-identity-an-agent-runs-as/)
- [All of them](/guides/)

## Sources

- Microsoft: Copilot Studio overview: https://learn.microsoft.com/en-us/microsoft-copilot-studio/fundamentals-what-is-copilot-studio (read 16 Nov 2026)
- Microsoft: Copilot Studio security and governance: https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance (read 16 Nov 2026)
- Microsoft: configure user authentication for tools: https://learn.microsoft.com/en-us/microsoft-copilot-studio/configure-enduser-authentication (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/default-permissions/copilot-studio/
