Quotas, limits, and configuration values for Power Virtual Agents

This topic contains quotas, limits, and configuration values for Power Virtual Agents.


Quotas are default constraints applied to chatbots that limit how often messages can be sent to the chatbot. The purpose of quotas is to throttle the client's service load, which protects a service from being overloaded and the client from unexpected resource usage.

Quotas are applied to your chatbots alongside the capacity constraints you gained by purchasing a Power Virtual Agents plan. Also see Licensing and capacity considerations.

The following quotas, defined as requests per minute (RPM), apply to Power Virtual Agents chatbots' Dataverse environment.

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

If the quota for messages to a chatbot is met, the user chatting with the chatbot will see a failure notice when they try to send a message. They'll be prompted to retry.

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


These limits apply to the Power Virtual Agents web app and the Power Virtual Agents app in Microsoft Teams.

Power Virtual Agents web and Teams apps limits

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

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 Power Virtual Agents standalone subscription to use skills in a bot you've created in the Teams app. Skills are not available in the Teams plan.

Power Virtual Agents 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 bots in a tenant will be enforced.1
Power Platform requests2 250,000 every 24 hours3 6,000 every 24 hours

1 Power Virtual Agents sessions that are included with Microsoft 365 subscriptions aren't pooled.
2 These requests are consumed by Power Automate flows that are triggering by Power Virtual Agents chatbots. Learn more about Power Automate limits.
3 You can contact your admin to increase the Power Virtual Agents Power Platform requests limits by purchasing the Power Virtual Agents Chat Session add-on. For more information, see the Microsoft Power Platform Licensing Guide.

Required services

The following table lists the services to which Power Virtual Agents connects. Ensure none of these services are blocked on your network.

Configure all required services for Power Automate, in addition to Power Virtual Agents, 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 to ensure Microsoft team can adequately respond to client-side bot editing issues)
*.powerva.microsoft.com Yes HTTPS Power Virtual Agents authoring experience and APIs
*.analysis.windows.net Yes HTTPS Analytics reports shown in Power Virtual Agents (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 Power Virtual Agents authoring experience

IP addresses

Requests from Power Virtual Agents to Microsoft Bot Framework skills use the following IP addresses in their respective regions.

Configure all connectors for IP addresses for Power Automate, in addition to Power Virtual Agents, to use both together.

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 Power Virtual Agents to Microsoft Bot Framework skills will be using United States IP addresses.