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

Power Automate error
Forbidden
403

02Likely 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

  1. Check DLP policies: Power Platform admin center > Data policies. Look for policies that block the connector in your environment's group.
  2. Verify the connection user has the right permissions on the target service (SharePoint site permissions, Dataverse security roles, and similar).
  3. If it's a premium connector issue, verify the flow owner or caller has a Power Automate Premium license.
  4. Contact your admin if a DLP policy needs to be modified.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.