CRM Crate

User API Requests: Overview, allocation, & limits in Power Platform

In this blog post, we’ll cover the overview, allocation, and limits of API requests per user in Power Platform. Before we begin, ensure you subscribe to CRM Crate to remain informed about the latest developments in the Power Platform field.

User API Requests: Overview, allocation, & limits in Power Platform

Microsoft Power Platform is a suite of applications—Power BI, Power Apps, Power Automate, and Power Virtual Agents—that allows users to analyze data, build apps, automate processes, and create chatbots. It empowers both developers and non-developers to create solutions that drive business efficiency. Licensing for Power Platform is flexible, with options ranging from pay-as-you-go plans for individual app use to more comprehensive subscriptions like Power Apps per user or per app plans. The licensing can also be tied to Microsoft 365 or Dynamics 365 subscriptions, providing seamless integration across Microsoft’s ecosystem.


What is a user request in Microsoft Power Platform?

In Microsoft Power Platform, a user request encompasses various actions performed across different products. At a high level, an API request includes the following:

User API Requests: Overview, allocation, & limits in Power Platform

API request allocations and limits based on user product license

API request allocations and limits can vary significantly depending on the type of user license you have. Higher-tier licenses generally offer more generous limits to accommodate increased usage needs, while basic or standard licenses might have more restrictive thresholds. These allocations help ensure fair usage across all users and maintain system performance. If you’re dealing with a high volume of API requests, it’s crucial to understand your specific license’s limitations to manage your integration effectively and avoid hitting those limits unexpectedly.

Users of Microsoft Power Platform have limits on the number of requests they can make, depending on their license type. The table below shows the number of requests allowed per user within a 24-hour period:

User API Requests: Overview, allocation, & limits in Power Platform

Power Platform request limits apply only to paid base licenses within the Dynamics 365 ‘base + attach’ licensing model. Attach licenses do not come with separate limits. For instance, if a user holds a Dynamics 365 Sales Enterprise base license and a Dynamics 365 Field Service Enterprise attach license, the request limit is determined solely by the base license (Dynamics 365 Sales Enterprise).

When a user has multiple paid licenses, the total request limit is the sum of the limits for each license. For example, a user with both a Dynamics 365 Customer Service Enterprise base license and a Power Apps per user license will have a combined total of 80,000 requests per 24 hours (40,000 requests per license).

Requests from Microsoft Copilot Studio are counted based on Power Automate flows triggered by a Microsoft Copilot Studio chatbot. Both the Microsoft Copilot Studio initial sessions pack and the additional sessions pack have the same daily Power Platform request limits.


API request allocations and limits based on non-licensed user

Some activities, like background processes that migrate data between databases, have their own limits and don’t need user interaction. These limits are set at the tenant level and are pooled together. In Dataverse, you can create identities that don’t involve direct user interaction, including:

  • Application users
  • Non-interactive users
  • Administrative users
  • SYSTEM users

The table below shows the number of requests allowed per non-licensed user within a 24-hour period:

User API Requests: Overview, allocation, & limits in Power Platform

In summary, understanding user API requests in Power Platform is crucial for optimizing application performance and ensuring compliance with usage policies. By carefully managing API request allocation and adhering to established limits, organizations can effectively balance user needs with system capabilities. Monitoring and adjusting API usage helps prevent performance bottlenecks and avoids potential service disruptions, ensuring a smooth and efficient experience for end-users. Effective management of API requests is essential for maintaining the reliability and scalability of applications within the Power Platform ecosystem.

We will learn to open a Canvas App on a ribbon button click in Dynamics 365. Before we start, make sure to subscribe to CRM Crate so that you stay up-to-date in the field of Dynamics 365 CRM.

error: CRM Crate Security Engine - Disabled Right Click & Selection!

Congratulations!

Well Done,
Welcome to CRM Crate

Stay tuned with us and get all latest updates and learning in Microsoft CRM and related techonologes.