Platform Choice
Part of No-code performance and scale
Checking platform limits before a wider rollout
Build a plan-specific register for records, queries, requests, workload and data delivery before inviting more users.
Before inviting more users, build a limit register for the actual plan, data source, connectors and identities. Compare forecast use with each recorded boundary and its outcome. Mark every essential task within scope, needs a change or unresolved; go only when blockers are resolved, otherwise hold or narrow the rollout.
Identify the configuration
Record the builder, subscription, source of each important table, connected APIs, automations and the identities that run them. Add the intended user count, the records each person needs and the essential tasks.
Match each task to its resources. A search may depend on query delegation; a scheduled import may depend on automation and API allowances. Decide which failures or partial results would block wider use.
Keep a limit register
| Item | What to establish |
|---|---|
| Records and files | What counts, at which scope, and what happens at the limit? |
| Query completeness | Does the configured formula search the whole intended source? |
| Requests and automation | Which identity consumes the allowance, and over what period? |
| Workload | Does extra use create an overage, take the app offline or have another documented outcome? |
| Data delivery | How much reaches each device, and is the task still usable? |
For every relevant item, record the exact plan, published rule, source title and date checked, present use, forecast and required action. Obtain account-specific entitlements or administrator settings from the account owner. Keep daily request usage separate from monthly workload and query completeness.
Read vendor limits in scope
Microsoft Learn’s “Query limitations: Delegation and query limits” says Power Apps canvas queries are delegated only when the full formula can be translated for that data source. A nondelegable query processes the first 500 records by default, configurable up to 2,000. This is a query-completeness boundary, not source storage capacity.
If a source exceeds the app’s 500-record default or its configured limit, up to 2,000, a nondelegable formula can return incorrect results. Delegation varies by formula and source: Dataverse supports the “in” operator, while Excel does not; if any part is nondelegable, Power Apps delegates none of the query.
Microsoft Learn’s “Requests limits and allocations” says requests are limited each day across Power Apps, Power Automate, Microsoft Copilot Studio and Dynamics 365. Successful and failed actions count; retries and pagination also count. Power Apps connector and Dataverse API requests count, and allocations depend on the assigned licence.
Per 24 hours, the table gives 40,000 requests per paid licence for paid Power Platform users, excluding Power Apps per app, Power Automate per flow and Microsoft Copilot Studio, and for Dynamics 365 except Team Member. It gives 6,000 for Power Apps pay-as-you-go, Power Apps per app, Microsoft 365 apps with Power Platform access, and Dynamics 365 Team Member.
The table also lists 250,000 requests per 24 hours for Power Automate per flow and Microsoft Copilot Studio base offer or add-on pack, and 200 for a paid Power Apps Portals login. Record the assigned licence and forecast requests against its applicable daily allocation.
Bubble Docs’ “FAQ: Pricing and Workload” defines workload as a monthly measure that includes database operations, workflows and web requests. Starter, Growth and Team plans include workload, with workload tiers or overages available; Free and Agency plans cannot use either option.
If overages are disabled, a Starter, Growth or Team app that reaches its workload allowance is taken offline. It can return online if overages are enabled or a workload tier is purchased; with overages still disabled, it returns at the start of the next billing period.
Power Platform Daily Request Limits by Licence Type (Australia)
- Paid Power Platform User (excl. per app, Copilot Studio, Dynamics 365 Team Member)40,000 requests per 24 hours
- Power Apps Pay-as-you-go / Per App / M365 with Power Platform Access / Dynamics 365 Team Member6,000 requests per 24 hours
- Paid Power Apps Portals login200 requests per 24 hours
Key Query and Data Limits in Power Apps (Australia)
- Default nondelegable query limit
- 500 records
- Maximum configurable nondelegable query limit
- 2,000 records
- Delegation failure outcome
- Incorrect results if source exceeds limit
Decide the rollout scope
Mark each register item within scope, needs a change or unresolved. Go only when every essential task has a verified boundary, its forecast fits that boundary and required changes are complete. Hold or narrow the rollout if an essential task remains unresolved or exceeds an unaddressed limit.
A larger subscription helps only when it addresses the specific constraint. Revisit the register when user numbers, data source, workflow frequency or plan terms change.
