Quotas, limits, app registration, certificates, and configuration values for Copilot Studio


Power Virtual Agents capabilities and features are now part of Microsoft Copilot Studio following significant investments in generative AI and enhanced integrations across Microsoft Copilot.

Some articles and screenshots may refer to Power Virtual Agents while we update documentation and training content.

This article contains quotas, limits, app registration usage, certificate rotation, and configuration values for Copilot Studio.


Quotas are default constraints applied to copilots that limit how often messages can be sent to the copilot. Quotas exist primarily to protect against unexpected usage surges that otherwise might impact the functionality of the application.

Quotas are applied to your copilots alongside the capacity constraints you gained by purchasing a Microsoft Copilot Studio plan. Also see Licensing and capacity considerations. Copilot Studio default quotas are configurable and can be adjusted for your custom copilots on a case-by-case basis. Please open a support ticket with business justification to adjust your copilot's quota.

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

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

If the quota for messages to a copilot is met, the user chatting with the copilot sees a failure notice when they try to send a message. They're prompted to retry.

Error message in the copilot window that says 'Send failed. Retry.'.


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 copilots on a case-by-case basis. Please open a support ticket with business justification to adjust your copilot's limits.

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

Copilot Studio web and Teams apps limits

Feature Web app Teams app
Copilots N/A 50 per team
Topics 1000 per copilot in Dataverse environments 250 per copilot in Dataverse for Teams environments1
1000 per copilot in Dataverse environments (after upgrade)
Trigger phrases 200 per topic 200 per topic
Skills 100 per copilot 100 per copilot2

1 If you're approaching limits in Dataverse for Teams environments, you can upgrade Dataverse for Teams to continue adding topics.

2 You must have a Copilot Studio standalone subscription to use skills in a Teams app created copilot. Skills aren't available in the Teams plan.

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 copilots 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 copilots. 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 copilot 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

How Copilot Studio automatically creates app registration

What is app registration?

App registration is a process that assigns a unique identifier and a secret key to a copilot, allowing it to communicate with different channels and services. App registration is a mandatory component of Copilot Studio copilots, as it enables the copilot to identify itself to Omnichannel for Customer Service, in Microsoft Teams, and to authenticate with other channels. App registration also allows the copilot to connect with skills.

How does Copilot Studio manage app registration?

Copilot Studio simplifies the app registration process by automatically creating and managing the app registration for each copilot. There's no action required from the customer to set up or configure the app registration. Copilot Studio handles the app registration behind the scenes, ensuring that the copilot has the necessary credentials and permissions to interact with Omnichannel, selected channels, and skills. The customer can focus on designing and publishing the copilot, without worrying about the technical details of app registration.

Is app registration secure?

App registration doesn't pose a security issue to customers or their data. The app registration is only used to identify the copilot and to enable secure communication with the channels and skills. The app registration doesn't grant access to any customer data or resources, nor does it expose any sensitive information about the copilot. The app registration is stored and managed by Copilot Studio, which follows the highest standards of security and compliance.

How Copilot Studio automatically creates and rotates certificates


To let copilots communicate with your data sources and services, Copilot Studio creates an application in your Microsoft Entra ID tenant, along with an associated service principal. A service principal is an identity that represents an application and allows it to access resources in your tenant. Copilot Studio controls the credentials to the service principal, which is an encrypted certificate.

Certificate rotation

For security and compliance reasons, Copilot Studio rotates the certificates on a regular cadence. This certificate rotation means that the service principal gets a new certificate and the old one is revoked. This process is automatic and doesn't require any action from you. Certificate rotation doesn't affect the functionality of your copilots or the security of your data. It's a standard practice that ensures that the certificates are always valid and up to date.


Certificate rotation applies to both Copilot Studio classic and production (unified authoring canvas) versions. Both versions create and rotate certificates in the same manner, and don't require any action from you.

IP addresses

Requests from Copilot Studio to Bot Framework skills use the following IP addresses in their respective regions. If you're using an Azure service, we recommend you use the PowerPlatformInfra and PowerPlatformPlex service tags, which automatically implements the proper IP addresses. You can also manually enter IP addresses in your traffic configuration rules.

Configure all connectors for IP addresses for Power Automate in addition to Copilot Studio to use both together.

For general information on using service tags, refer to Virtual network service tags.

Region Outbound IP
United States,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
South America1,,,,,,,,,,,,,,,,,,,,,,,,,
United Kingdom,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Asia Pacific,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

1 Customer data in South America is replicated in United States for disaster recovery purposes, so requests from Copilot Studio to Bot Framework skills are using United States IP addresses.