Power Automate · Cloud flows: licensing errors
DirectApiAuthorizationRequired
Short answer
DirectApiAuthorizationRequired in a Power Automate cloud flow: The flow uses a premium connector but the caller doesn't have a premium license. The most likely fix is to assign premium license to caller.
VerifiedLast verified
01Error text
DirectApiAuthorizationRequired02Likely causes
- A flow with premium connectors (HTTP, SQL Server, Dataverse, custom connectors) is run by a user on a seeded Microsoft 365 license
- The flow owner has premium but the triggering user doesn't (the caller's license matters, not the owner's)
- A scheduled flow's owner lost their premium license
- An in-context flow was disassociated from its Power App, making it out-of-context
03How to fix it
- Identify which connector requires premium. The error message usually names it.
- Assign a Power Automate Premium license to the user who triggers or runs the flow.
- For scheduled or automated flows, ensure the flow owner has a premium license.
- Consider whether a Process license (per-flow) is more cost-effective for high-volume shared flows.
04Official documentation
→Related errors
- Forbidden (403)Forbidden (403) in a Power Automate cloud flow: The authenticated user or app doesn't have permission to perform the requested operation. The most likely fix is to check DLP policies, permissions.
- FlowRunQuotaExceededFlowRunQuotaExceeded in a Power Automate cloud flow: The flow or tenant exceeded its daily action execution limit. The most likely fix is to optimize action count, upgrade license.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Power Automate work:Open Power Automate jobs