You’re offline. This is a read only version of the page.
254
I'm currently using an Azure pipelines and Power Platform build tools to automate the ALM of my solutions. However, when the solution is imported into the other environments (UAT & PROD), the solution components are owned by the service application account (using a service principal).
I know that power apps ownership can be changed with PowerShell commands but how can this process be better integrated into the build->export->import workflow of Power Platform ALM?
O I see, it makes sense!
He's likely following this: https://docs.microsoft.com/en-us/power-platform/alm/devops-build-tools
That sets up a Service Principal as an application user... he's already done what your talking about.
What I think he's asking is how to add an additional owner of the apps/flow that is a real AD user. Service principals are not AD accounts.
You'd want this so you could log into the environments as that user and manage the apps/flows if needed. Something you can't do with a Service Principal.
To answer his questions, this is as close as I've gotten. Haven't tried it yet... YMMV.
https://github.com/dylanberry/PowerPlatformDevops/blob/main/scripts/Set-CanvasAppOwnerAndSharing.ps1
Good question!
I'll reply with another question 😛
Why don't you use the credentials of the user you want to make the owner of the solution components in your Azure Pipelines?
Alternatively, you can register an Application User in your Dataverse environment and run your pipelines with it.
Steps to create an Application User below:
https://readyxrm.blog/2020/10/30/how-to-setup-a-common-data-service-application-user-and-why/
I hope it helps!
#1
Michael E. Gernaey
11
Super User 2025 Season 1
#2
bscarlavai33
5
Super User 2025 Season 1
#3
getsplash
2
Share
Report
All responses (
Answers (
