Quotas and limits for Copilot Studio
This article contains quotas and limits for Copilot Studio.
Quotas
Quotas are default constraints applied to agents that limit how often messages can be sent to the agent. Quotas exist primarily to protect against unexpected usage surges that otherwise might impact the functionality of the application.
Quotas are applied to your agents alongside the capacity constraints you gained by purchasing a Microsoft Copilot Studio plan. Also see Assign user licenses and manage access. Copilot Studio default quotas are configurable and can be adjusted for your custom agents on a case-by-case basis.
The following quotas, defined as requests per minute (RPM), apply to Copilot Studio agents' Dataverse environment.
| Action | Quota with the paid plan |
|---|---|
| Messages to an agent (Includes any message from a user or integrations, such as Azure Bot Framework skills, to a single agent.) |
8,000 RPM per Dataverse environment |
If the quota for messages to an agent is met, the user chatting with the agent sees a failure notice when they try to send a message.
Limits
These limits apply to the Copilot Studio web app and the Copilot Studio app in Microsoft Teams. These limits are configurable and can be adjusted for your agents on a case-by-case basis. Please open a support ticket with business justification to adjust your agent's limits.
Copilot Studio web app limits
| Feature | Limits |
|---|---|
| Agent Builder instructions | 8,000 characters |
| File upload (size) | 512 MB |
| Files uploaded (number of files) | 5001 |
| Image upload (size) | Only supported in PDF files |
| Skills | 100 per agent |
| Topics | 1,000 per agent in Dataverse environments |
| Trigger phrases | 200 per topic |
1 The 500-file limit does not apply to SharePoint as a knowledge source.
Copiot Studio Teams app limits
| Feature | Limits |
|---|---|
| Agents | 50 per team |
| Skills | 100 per agent1 |
| Topics | 250 per agent in Dataverse for Teams environments2 1000 per agent in Dataverse environments (after upgrade) |
| Trigger phrases | 200 per topic |
1 You must have a Copilot Studio standalone subscription to use skills in a Teams app created agent. Skills aren't available in the Teams plan.
2 If you're approaching limits in Dataverse for Teams environments, you can upgrade Dataverse for Teams to continue adding topics.
Copilot Studio subscription limits
| Feature | Standard subscription | Teams (select Microsoft 365 subscriptions) |
|---|---|---|
| Sessions | N/A | Chat sessions are unlimited per tenant every month, but a service limit of 10 sessions per user every 24 hours across all agents in a tenant are enforced.1 |
| Power Platform requests2 | 250,000 every 24 hours3 | 6,000 every 24 hours |
1 Copilot Studio sessions that are included with Microsoft 365 subscriptions aren't pooled.
2 These requests are consumed by Power Automate flows that are triggered by Copilot Studio agents. Learn more about Power Automate limits.
3 You can contact your admin to increase the Copilot Studio Power Platform requests limits by purchasing the Copilot Studio Chat Session add-on. For more information, see the Microsoft Power Platform Licensing Guide.
Required services
The following table lists the services to which Copilot Studio connects. Ensure none of these services are blocked on your network.
Configure all required services for Power Automate, in addition to Copilot Studio, to use both together.
| Domains | Required | Protocols | Uses |
|---|---|---|---|
| *.directline.botframework.com | Yes | HTTPS | Access to Bot Framework Web Chat |
| *.directline.botframework.com | Yes | WS | Web socket connection to support Chat |
| pipe.aria.microsoft.com | No | HTTPS | Telemetry data gathered by Microsoft (strongly recommended ensuring the Microsoft team can adequately respond to client-side agent editing issues) |
| *.powerva.microsoft.com | Yes | HTTPS | Copilot Studio authoring experience and APIs |
| *.analysis.windows.net | Yes | HTTPS | Analytics reports shown in Copilot Studio (through Power BI) |
| bot-framework.azureedge.net | Yes | HTTPS | Bot framework resources |
| pa-guided.azureedge.net | No | HTTPS | In-product guidance (recommended) |
| cci-prod-botdesigner.azureedge.net | Yes | HTTPS | Copilot Studio authoring experience |
Maximum channel data message size limits when using Copilot Studio in Omnichannel
Copilot Studio in Omnichannel uses the ACS channel, and the same channel data message size limit of 28 kb applies.
This limit can affect scenarios such as transferring to Omnichannel, where all the variables (both local to the topic and agent variables available in the conversation) are passed as context to the agent. If the size of all the variables passed exceeds the limit, the ACS channel fails with error MessageSizeExceeded, and the transfer is completed without the variables being passed. If you encounter scenarios in which the context isn't being passed, check for a large number of variables, and clear them before making the transfer to avoid going over the limit.