Recently we got the below error “Forbidden” for one of our flows that was using the Dataverse connection. After some analysis, we found the root cause of the error. The Dataverse connection reference was created using the Service Principal but it was not added as an Application User (with appropriate security role) in that environment. … Continue reading “Fix – Forbidden. There’s a problem…
Continue Reading Nishant Rana’s Article on their blog
Fix – Forbidden. There’s a problem with the flow’s trigger. Fix the trigger (Power Automate / Flow / Dataverse)
Recently we got the below error “Forbidden” for one of our flows that was using the Dataverse connection. After some analysis, we found the root cause of the error. The Dataverse connection reference was created using the Service Principal but it was not added as an Application User (with appropriate security role) in that environment….
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
Dyn365CE23 April 2024Portal does not load and displays “Server Error” or shows “Getting set up.. This might take a while” message -Portal Startup Issue (PowerApps Portal)
Dyn365CE22 April 2024Versioning and Drafts for Solution-based Cloud Flows – Power Automate
Dyn365CE16 April 2024What will happen on changing the password of the user account used as the Owner of Cloud Flow and for Connection – Power Automate
Dyn365CE15 April 2024Using Focused view in Dynamics 365
