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.

Quota with the paid plan (per Dataverse environment)	Action
8,000 RPM	Messages to an agent (Includes any message from a user or integrations, such as Azure Bot Framework skills, to a single agent.)

Generative AI messages to an agent

Includes any message generated through features like generative orchestration, agent action, AI Tools, agent flow actions, and generative answers.

The following quotas, defined as requests per minute (RPM) or requests per hour (RPH), apply to Copilot Studio agents' Dataverse environment.

Quota per Dataverse environment	Tenant billing capability
50 RPM / 1,000 RPH	1-10 prepaid message packs
80 RPM / 1,600 RPH	11-50 prepaid message packs
100 RPM / 2,000 RPH	51 - 150 prepaid message packs
+1 RPM / +20 RPH	Each extra 10 prepaid message packs above 150
10 RPM / 200 RPH	Trial or developer environments
100 RPM / 2,000 RPH	Pay-as-you-go environments
100 RPM / 2,000 RPH	Microsoft 365 Copilot users

Note

Once the quota 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. To adjust your agent's limits, open a support ticket with business justification.

Copilot Studio web app limits

Feature	Limits
Agent Builder instructions	8,000 characters
Connector payload	450 KB
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

¹ The 500-file limit doesn't apply to SharePoint as a knowledge source. For better search results from SharePoint and support of files up to 200 MB in size, use a Microsoft 365 Copilot license in the same tenant as your agent, and turn on Enhanced search results.

Copilot Studio web app SharePoint limits

• Only modern SharePoint pages are supported. However, modern pages containing SPFx components aren't supported.

• Content from classic ASPX pages on SharePoint aren't used to generate answers.

• SharePoint sites containing the following file types can be used as knowledge sources:

  • Word documents (DOC/DOCX)
  • PowerPoint (PPT/PPTX)
  • PDF files

• For better search results from SharePoint and support of files up to 200 MB in size, use a Microsoft 365 Copilot license in the same tenant as your agent, and turn on Enhanced search results.

• You can also load individual files and folders. When using this option, there is support for files up to 512 MB in size. For more information, go to Unstructured data as a knowledge source.

• While you can add structured files, such as .XLSX from SharePoint, agents currently lack the ability to write and run code. Currently, the responses to analytical questions might not be optimal.

• For makers without the Microsoft 365 Copilot license in the same tenant as their agent, due to memory limitations, generative answers can only use SharePoint files that are under 7 MB. If a file is larger than 7 MB, consider splitting it into multiple smaller files. For more information, see File size support.

• We recommend omitting https:// from the URL. Recognized SharePoint URLs are from the sharepoint.com domain.

• SharePoint sites with an accordion navigation menu or a custom CSS aren't used to generate answers.

• If you want to use a dynamic SharePoint URL using a Power Fx formula, you must use the Classic data option, which is available from the generative answers node properties. For more information on how to use SharePoint content with a generative answers node in a topic, see Use SharePoint content for generative answers.

• Queries to a SharePoint knowledge source that reference a file or document name can't be answered. For example, if a user asks, "What is the mitigation provided in file-name.pdf?" Or, "Tell me the file name that contains information on bug 2020213?"

• Currently, access to SharePoint documents and Enhanced search results don't support manual authentication.

• Document libraries aren't supported as lists.

• SharePoint list queries only return data from the first 2048 rows of data.

• Currently the Attachments column doesn't provide the ability to index and reason over provided attachments. However, no error occurs and the list is indexed, but no responses are provided based on the contents of the attachment.

• Up to 15 lists can be selected during each session of using the Add knowledge dialog. To add more lists, complete the first set of 15 and then Add knowledge again.

• List views can't be selected as a knowledge source.

• Glossary and Synonyms aren't supported for lists.

Copilot 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

¹ 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.

² 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

¹ Copilot Studio sessions that are included with Microsoft 365 subscriptions aren't pooled.
² These requests are consumed by Power Automate flows that are triggered by Copilot Studio agents. Learn more about Power Automate limits.
³ 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.

Copilot Studio unstructured data knowledge source limits

OneDrive limits

• Number of files and folders
  • Total of 200 files, 50 folders, and 10 layers of subfolders can be included for each source.
  • Folders are represented as a single knowledge source, which contains all of their content.
• 32 MB per file
• Synchronization frequency is four to six hours (based on the time of ingestion completion)
• Supported file types: doc, docx, xls, xlsx, ppt, pptx, pdf

Note

• Documents that were protected using sensitivity labels, or were password protected, can't be indexed. If added, these types of documents show as ready for use but don't provide responses.
• After you add files or folders, the status might indicate "Ready" immediately after they were added, but then change to "In Progress." Once the status changes from "In Progress" back to "Ready," the content is ready for use.
• There's currently no support for glossaries or synonyms.
• At this time, Application Lifecycle Management (ALM) isn't supported for this feature. Importing agents won't result in automated knowledge source processing.

SharePoint limits

• Number of files and folders
  • Total of 200 files, 50 folders, and 10 layers of subfolders can be included for each source.
  • Folders are represented as a single knowledge source, which contains all of their content.
• 32 MB per file
• Synchronization frequency is four to six hours (based on the time of ingestion completion)
• Supported file types: doc, docx, xls, xlsx, ppt, pptx, pdf

Note

• Files containing the characters ', #, or & can't be indexed.
• A maximum of 15 files or folders can be selected at once when creating a knowledge source.
• Documents that were protected using sensitivity labels, or were password protected, can't be indexed. If added, these types of documents show as ready for use but don't provide responses.
• After you add files or folders, the status might indicate "Ready" immediately after they were added, but then change to "In Progress." Once the status changes from "In Progress" back to "Ready," the content is ready for use.
• There's currently no support for glossaries or synonyms.
• At this time, Application Lifecycle Management (ALM) isn't supported for this feature. Importing agents won't result in automated knowledge source processing.
• Currently, document libraries are not supported.

Salesforce and Confluence limits

• No limit on the number of articles
• No limit on size of articles
• Synchronization frequency is four to six hours

Note

• After you add files or folders, the status might indicate "Ready" immediately after they were added, but then change to "In Progress." Once the status changes from "In Progress" back to "Ready," the content is ready for use.
• There's currently no support for glossaries or synonyms.
• At this time, Application Lifecycle Management (ALM) isn't supported for this feature. Importing agents won't result in automated knowledge source processing.

ServiceNow and ZenDesk limits

• No limit on the number of articles
• No limit on size of articles
• Synchronization frequency is four to six hours

Note

After you add files or folders, the status might indicate "Ready" immediately after they were added, but then change to "In Progress." Once the status changes from "In Progress" back to "Ready," the content is ready for use.

At this time, Application Lifecycle Management (ALM) isn't supported for this feature. Importing agents won't result in automated knowledge source processing.

Dataverse limits

• Maximum of two Dataverse sources per agent
• Maximum of 15 Dataverse tables per knowledge source
• Dataverse tables:
  • Standard or Activity tables types are supported
    • EXCEPTION: Tables with type = Virtual when dataproviderid = 2ac667f5-31d6-e911-a95e-000d3a110bbd
  • All supported tables require that the maker has READ permissions
• Synonyms and glossaries are supported for Dataverse tables:
  • Maximum synonym name character length is 100
  • Maximum synonym description character length is 1000
  • Maximum glossary name character length is 100
  • Maximum glossary description character length is 1000

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. Then clear them before making the transfer to avoid going over the limit.