Power Platform Pipelines delegated deployments, part 1 - application account

[@DanielWesterdale]

Great video! I am using pipelines atm . The process for locating missing depdencies is truly painful: for each failed deployment, go to PP Host , find run history record, then copy the validation error json into VS Code + format document. Next look for those missing depencies. If the solution you are trying to deploy shares dataverse tables with another solution, well this will be a higher order of magnitude in pain!

[@TomaszPoszytek]

Yeah, I agree. Or go an click every object in solution to check/ add required objects :)

[@hash4162]

Thanks for sharing, great video your explanation is very clear ❤

[@TomaszPoszytek]

Glad it was helpful! 🥰

[@josephlim2064]

Hi Tomasz, does the PP Pipelines support/work for multi-geo or single tenant-multiple regions scenario? Does it require any special configuration or development? Thanks

[@TomaszPoszytek]

Hey, it is supporting multi region, but single tenant.

[@nickthoman2280]

What environment does the approval workflow need to be in? I am assuming the same environment that Pipeline Orchestrator is deployed in or should it be the environment that you want the approval on?

[@TomaszPoszytek]

The one where the orchestrator is deployed to, you’re right.

[@kannankarmegam-bne]

Hi Tomas, at 20:28 you mentioned about sharing user connection references with service principal. In this example, if jack researcher (user) deploys the solution the app deployed as service principal in PROD and I noticed in this case the flow connection references it uses deploying users connection reference and service principal is co-owner. The problem here is if the flow has an dataverse action "Add a new record" and when a record is created, the "created by" column it updates Jack Researcher which is wrong. I would expect it should be updated by the service principal. Bit confusing ?

[@TomaszPoszytek]

Hmmm this may be due to fact this is a premium connector and service principal can’t be assigned a license.

[@denisskorikov6234]

Good job!

[@TomaszPoszytek]

Thank you! Cheers!

[@juansepowerplatform]

Great video thanks for your hard work. my question is can a service principal account own power apps or model driven apps. will this delegated approach work with apps?

[@TomaszPoszytek]

Hey, thank you! Yes, service principal can be an owner. This is why if an app or process uses premium connectors it must be granted a per process or per app license, in order to run, because SPN can’t be granted a license.

[@devizion5767]

I've tried out Power platform pipelines in my demo environment, and it is quite slick in how it is integrated, but i've got a hard time understanding MS when it comes to the licensing. We've got a lot of customer where this would be a good ALM solution, if it wasn't for the premium license requirements per user. As it is now, azure devops can do this (and alot more) for a fraction of the cost long term, so it is a hard sell for us.

[@TomaszPoszytek]

The point is, you don’t buy licenses just for the ALM. It’s an addition only. You buy them to build solution, use solutions, benefit from all premium features. That’s my point of view.

[@devizion5767]

I think this is a clash in the size of customer MS aims at versus which our company usually work with. We got a lot of customer were we are starting up their first canvas app(with no premium connectors) and need to implement a ALM solution, aswell as educate the customer in it. So I firsts saw it as a good middle-ground instead of azure devops for the smaller projects/customers. @@TomaszPoszytek

[@IvanUsma]

I was interested in the video but the text is too small to read, thanks

[@TomaszPoszytek]

Hey, sorry to hear :( Which text? Have you tried opening it in a full screen mode?

[@kannankarmegam-bne]

agree font is bit small

[@jotpol]

poor sound quality. Buy a better microphone

[@TomaszPoszytek]

Well, I find it pretty good… Do you find sound in any particular moment poor?