Copilot Studio governance controls
If a company lets staff build agents in Microsoft Copilot Studio, administrators need to know what they can switch off, watch and cap. This guide summarises Microsoft's Security and governance article (the search index dates it 7 August 2026). It describes what Microsoft says exists, not how well it works. We have not used Copilot Studio.
Controls Microsoft lists
| Control | What Microsoft says it does |
|---|---|
| Data policies | Admins use Power Platform admin center data policies to govern maker and user authentication, knowledge sources, actions, connectors and skills, HTTP requests, channel publication, Application Insights and triggers. |
| Credit governance | Admins can monitor usage and set monthly agent limits for prepaid or pay-as-you-go billing. Notifications and a hard stop are separate choices; see the limits below. |
| Connector dependency insights | Admins can review which connectors agents use before deployment. |
| Audit logs | Maker audit logs in Microsoft Purview, and activity monitoring and alerts in Microsoft Sentinel. |
| Run tools with user credentials | Makers can configure tools to use the signed-in user's credentials by default. |
| Security scan | Makers see security alerts and real-time risk findings, aimed at data exfiltration, before publishing when default security settings change. |
| Environment routing | Admins route makers to a safe environment and can show a welcome message about privacy and compliance. |
| Customer-managed keys | Admins can enable customer-managed encryption keys for environments. |
| Source-control audit trail | GitHub-backed source control and deploy-from-Git with auditable deployment history. |
| Sensitivity labels | For SharePoint knowledge, makers and users can see the highest sensitivity label used in a response. |
Authentication and approval are separate controls
Operational sources checked 12 October 2026. These are documented configuration controls, not a guarantee of safe output.
- Channel and user authentication: No authentication lets anyone with the link interact. Microsoft authentication supports Teams and Microsoft 365; other authenticated channels need manual setup. Authentication changes take effect after publishing. User authentication source.
- Maker-account exposure: Event triggers use maker credentials. Authenticated autonomous actions also need working maker authentication; users of a published agent may access data or actions under that authorisation. Review whose account is used before adding triggers. Event trigger source.
- Confirmation: Makers can require user confirmation for tools that modify data. Publication is not evidence that every change asks first. Orchestration and confirmation source.
Check the intended channel, connector policy groups, account used by each tool and risky-tool confirmation in a test environment. Admin data policies can restrict knowledge, connectors, HTTP, channels and triggers. See the updated Copilot Studio evidence record and licensing guide; unattended trigger work can still consume credits.
Agent 365
Microsoft describes Agent 365 as a central control plane to observe, govern and secure Copilot Studio agents. For organisations that onboard it, agents can be represented as Microsoft Entra identities, governed with Conditional Access, role-based and attribute-based access controls and access governance workflows. Microsoft also lists Entra network egress and ingress controls through Agent 365 and says that capability is generally available. These features apply only to organisations that onboard Agent 365.
Generative AI switches and a Lockbox caveat
- Admins can turn off publishing of agents that use generative AI features for the tenant, and can disable data movement across geographic locations for generative AI features outside the United States.
- Customer Lockbox is supported, but Microsoft says it does not cover everything. Two categories are excluded: security audit logging telemetry (agent invocation, tool and action calls, policy decisions, runtime activity), which goes through the Purview pipeline, and certain Agent 365 governance and audit events.
Can a monthly credit limit stop Copilot Studio overspending?
A monthly agent limit is useful, but it is not an instant, tenant-wide spending ceiling. Microsoft's capacity-management documentation, read 9 November 2026, separates the agent limit from environment capacity and the agent flows it calls. These are documented controls, not a test of enforcement or a promise of a maximum invoice.
Set the agent limit and choose what happens
In Power Platform admin center, go to Licensing โ Copilot Studio โ Summary โ Manage Agents. Microsoft says admins can set monthly consumption limits for agents in both prepaid and pay-as-you-go environments. Configure notifications for approaching the limit and a hard stop if the agent should be turned off at the limit; an alert alone is not a shutdown setting.
Leave margin. Microsoft says limits are not applied instantly, so an agent can keep responding for some time after reaching its limit. Do not set the threshold equal to the last credit you can afford and assume there can be no further consumption.
Check the environment's overage sources
Environment allocation is a different control. After allocated credits run out, the environment may draw from unallocated tenant capacity or bill a linked pay-as-you-go plan. Eligible environments without an allocation configuration draw from the tenant pool by default. If no overage source is enabled, credit-dependent experiences can stop after the allocation is exhausted. Review the actual environment settings rather than treating an allocation as an isolated budget.
An agent limit does not stop its agent flows
Microsoft explicitly says an agent's monthly limit does not stop the agent flows it calls. Agent flows are billed and checked for capacity separately. New agent flow runs are blocked when the environment has no available Copilot Credits; runs already in progress complete, and the parent agent can still handle non-flow interactions. Environment allocation, access to the tenant pool and the pay-as-you-go plan therefore matter alongside the agent limit.
This distinction concerns Copilot Studio agent flows, not every automation called a flow. Microsoft's billing article says Power Automate cloud flows use Power Automate licensing rather than Copilot Credits. Check the actual flow type before deciding which control applies.
Sources checked 9 November 2026: Manage Copilot Credits and capacity and Billing rates and management. This dated spend-control check does not refresh every older governance claim on this page.
Questions to ask before rollout
- Which data policies will block connectors, HTTP requests and triggers by default?
- Are notifications and a hard stop configured for each agent, with margin for enforcement delay, and are environment overage sources and agent flows controlled separately?
- Do tools run as the user or as the maker, and what can each reach?
- Where do audit logs go, and does your compliance team accept the Lockbox exclusions above?
- Is Agent 365 onboarded, since some identity controls depend on it?
Pricing context is in Copilot Studio vs Agentforce. For general questions to ask any vendor, see the privacy and approval checklist and the ChatGPT workspace agents guide.
Source: Microsoft Learn, Security and governance in Copilot Studio. Spot a change? Tell us.