Power Automate · Cloud flows: connection and authentication errors
Forbidden (403)
Short answer
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.
VerifiedLast verified
01Error text
Forbidden
40302Likely causes
- A DLP (Data Loss Prevention) policy blocks the connector or connector action in this environment
- The user lacks permissions on the target resource (for example, no write access to a SharePoint list)
- An admin restricted the connector via tenant-level settings
- The connector requires a premium license and the user is on a seeded plan
03How to fix it
- Check DLP policies: Power Platform admin center > Data policies. Look for policies that block the connector in your environment's group.
- Verify the connection user has the right permissions on the target service (SharePoint site permissions, Dataverse security roles, and similar).
- If it's a premium connector issue, verify the flow owner or caller has a Power Automate Premium license.
- Contact your admin if a DLP policy needs to be modified.
04Official documentation
→Related errors
- Unauthorized (401)Unauthorized (401) in a Power Automate cloud flow: The API rejected the request because the authentication token is invalid or expired. The most likely fix is to fix connection, rotate credentials.
- DirectApiAuthorizationRequiredDirectApiAuthorizationRequired 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.
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