web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Power Automate flow: r...
Power Automate
Unanswered

Power Automate flow: request denied error when running the flow

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

Hi everyone

we are developing a PowerApp connected to a dataverse to allow a check during shipments outbound processing. The main requirement from our client is to give access to a specific set of users only to the PowerApp, and not to Dynamics 365 Finance and Operation. A second requirement is to let the PowerApp user print a label, using ZPL code, on a Zebra printer triggering the printing from PowerApp.

To implement this function, we have adopted the following solution:

Data-entities/WHSDocumentRoutingPrinterEntity_IM.xml at master · Ievgenm/Data-entities · GitHub

To let a PowerApp user that is not a D365 user to trigger the flow, we setup a connection using service principal.

With these settings the flow have been working for months.

Now, after a restore of the d365 enviroment, we are experiencing some failures during test.

The flow doesn't work when a user that is not the owner trigger it and the error displayed is the following: "An error has occurred. User is not authorized to read view WHSDocumentRoutingPrinterEntity_IM. Request denied."

We would like to understand how can we deal with this issue.

Thanks,
Flavia

image.png
Categories:
I have the same question (0)
  • Pstork1 Profile Picture
    69,543 Most Valuable Professional on at

    Is the flow a solution aware flow? In other words was it originally built inside a solution?  If it was it should be using connection references.  If not then its using direct connections. This kind of problem is common when importing flows into a new environment if they are not solution aware and using connection references.  Try adding it to a solution, replacing the connections with connection references that point at the original connection.

  • Skenny Profile Picture
    4 on at

    1) Remove the PowerApps V1 connector and use the V2 connector for PowerApps instead, update the variables to match in the header.
    2) Save the Flow, go to the details pane, in the bottom right you should see a 'Run Only Users' dialog box. Open it, and update the connectors to use the relevant connection reference. Hit Save.

    You should be good to run and test.

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Thanks Skenny! This solved the issue!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 411

#2
David_MA Profile Picture

David_MA 300 Super User 2026 Season 1

#3
Vish WR Profile Picture

Vish WR 291

Last 30 days Overall leaderboard