Power Platform Pipelines delegated deployments, part 1 - application account

Подписаться 4,2 тыс.

Просмотров 1,4 тыс.

50% 1

This video is demonstrating how to set up Power Platform Pipelines to benefit from using delegated deployments. In this video I am showing you how to use application account set up in Azure Entra ID.
Chapters:
0:00 Intro, what are PP Pipelines
4:29 Set up app in Azure
5:39 Set up app under S2S in PP Admin Center
7:33 Configure pipeline to use Delegated Deployment
9:04 Set pipeline stage owner as app owner (!!!)
11:00 Set up Power Automate process
12:01 Create connection using app for all unbound actions
16:04 Share pipeline with users that will use it (!!!)
17:12 Deployment using app account
22:10 Deployment details inside PP Pipelines app
23:50 Deployed solution in target environment
24:12 Wrap up!

Опубликовано:

2 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 22

@hash4162 4 месяца назад

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

@TomaszPoszytek 4 месяца назад

Glad it was helpful! 🥰

@denisskorikov6234 2 месяца назад

Good job!

@TomaszPoszytek 2 месяца назад

Thank you! Cheers!

@DanielWesterdale 4 месяца назад

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 4 месяца назад

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

@kannank7313 2 месяца назад

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.

@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 27 дней назад

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 18 дней назад

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

@juansepowerplatform 3 месяца назад

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 3 месяца назад

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 4 месяца назад

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 4 месяца назад

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 4 месяца назад

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