Let\’s talk about Power Automate and how to use the Service Principal account to run your Power Automate jobs?
Why do we need Service Principal? Let suppose you have created a background automation which is using Common Data Service (CDS) triggers or actions, so its better to use service principal rather than to a specific user (because specific user may leave the company, his account can be disabled).
Following is the 3 steps guide with reference:-
- Register your App in Azure (Azure Application Registration)
![\"PowerAutomate-UseServicePrincipal01\"](\"http://cloudily.com.au/wp-content/uploads/2019/12/powerautomate-useserviceprincipal01.png\")
- Create New Application User in D365 (Application User Creation)
![\"PowerAutomate-UseServicePrincipal02\"](\"http://cloudily.com.au/wp-content/uploads/2019/12/powerautomate-useserviceprincipal02.png\")
- In Power Automate use ‘Connect with Service Principal’
![\"PowerAutomate-UseServicePrincipal03\"](\"http://cloudily.com.au/wp-content/uploads/2019/12/powerautomate-useserviceprincipal03.png\")
![\"PowerAutomate-UseServicePrincipal04\"](\"http://cloudily.com.au/wp-content/uploads/2019/12/powerautomate-useserviceprincipal04.png\")
In case, if you have any question feel free to ask in the comments. 🙂
Pingback: Power Automate: Use Service Principal - 365 Community
Hi folks. After creating the App User and setting as the connection for the trigger in the Flow, it doesn’t get triggered anymore. We get the error “Forbidden”. Anything we may be missing here? Or any proviledge that needs to be given to the Service Principal account?
Have you tried testing the flow with manual trigger in the flow? I never faced the ‘forbidden’ error.