Using Pipelines to Simplify Power Platform Deployments
Вставка
- Опубліковано 7 лют 2025
- 👉 On-Demand Learning - Start With The FREE Community Plan: prag.works/odl...
In this video, we explore how pipelines can simplify your Power Platform deployments. Pipelines are a useful tool that allow you to automate and standardize the deployment process, ensuring that your solutions are deployed consistently and efficiently across environments. We'll cover the key concepts of pipelines, demonstrate how to create a simple pipeline, and show how to use pipelines to deploy a Power Apps solution. Whether you're new to pipelines or an experienced user, this video has something for you. Join us and learn how to streamline your Power Platform deployments today!
👍 If you enjoy this video and are interested in formal training on Microsoft Teams, Power BI, Power Apps, Azure, or other Microsoft products you can visit prag.works/BRI... for 40% off On-Demand Learning!
-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - -
Next step on your journey:
🔗Pragmatic Works On-Demand Learning Packages: pragmaticworks...
🔗Pragmatic Works Boot Camps: pragmaticworks...
🔗Pragmatic Works Hackathons: pragmaticworks...
🔗Pragmatic Works Virtual Mentoring: pragmaticworks...
🔗Pragmatic Works Enterprise Private Training: pragmaticworks...
🔗Pragmatic Works Blog: blog.pragmaticw...
Let's connect:
✔️Twitter: / pragmaticworks
✔️Facebook: / pragmaticworks
✔️Instagram: / pragmatic.works
✔️LinkedIn: / pragmaticworks
✔️UA-cam: / pragmaticworks
Pragmatic Works
7175 Hwy 17, Suite 2 Fleming Island, FL 32003
Phone: (904) 638-5743
Email: training@pragmaticworks.com
#PragmaticWorks
Great explanatory video! Thanks
That's a great introduction video! Thank you, Brian.
Thanks Brian nicely explained
Glad it was helpful!
Great video Brian! Thank you!
Nice to learn about. Thank you 😊 👌🏽.
This is great. Thank you, Brian, 😇
@Brian - thanks for the video... We have customized the process to include approval workflows - but when it comes to Power Automate and Power Apps - this whole pipeline tool has some shortcomings. Trying to share connections and/or connection references, even when using a SPN doesn't seem to work correctly. At what point should someone abandon this and go with Azure DevOps instead?
You made my day... super awesome
Thank you so much 😀
Hi Brian, thanks for your clear explanation. You made a remark regarding licenses to use pipelines and you mentioned enterprise license. Is this the license type for people involved in pipeline deployment for example the admin or funtional application manager? I have a system with a combination with sales enterprise and team member licenses and I wonder if impelemting pipelines would affect the teammembers (I think not). Thanks in advance! Best Regards Martijn
could you please cover delegated deployments and the Approval flows required?
Heard about, but never understood pipelines, and now at last the mystery is being cleared up. Thx! So here’s my related follow up question: Let’s say I have a big customer like Ford and they need an accounting app. Would I want to create a new dedicated developer environment called FordAccountingDev and then continue your pipeline steps from there? And if they needed a marketing app would I make an environment called FordMarketingDev within which to build out the pipeline for that marketing app? Or is there a third/simpler way structured around one environment for Ford with perhaps multiple pipelines/solutions etc?
Great video! Unfortunately, it sounds like the biggest drawback is that all users need premium to use any of the apps in these environments. If this is accurate, then there's no way this will ever be used with actual businesses. It is rare to find a business that will have all their users licensed with premium as it costs too much. I can understand requiring the account doing the deployment needing premium, but that is about it.
This is incorrect. All users do not need a premium licence, just the makers.
Great video Brian - But I do have a question. In this video after setting up the pipeline in a new env you created a managed solution in the dev environment which then got picked up to be moved to QA and then subsequently Prod via pipeline stages you have setup. My question is if I have 5 Managed solutions in a dev environment and i want only one specific solution to be picked up from dev can i do that? How do i do that? In this video i missed the part where there should have been an exclusive way for pieplines to know which solution needs to be picked up ?
How did the pipeline handle different variables?
One thing missing is the dependencies. every time a new change is made in the source. make sure to include objects from the solution element before deploying. it really took a while to figure than out.
Do we have apis for these pipelines to automate the deployments
Great video Brian!! What happens to the existing solution in production (update / upgrade), Thank you.
Once you have you app in the specific Environment do you then have to Publish manually?
No, you can continue to publish using pipelines for updates if you wish.
mines not ding that its a the gen error of 0x0 reference error lol x.x
Thank you :) question, is it possible create pipelines for unmanaged environments but managed solutions?
I watched the video and proceeded without using Managed Environments or having a Premium License, and it still worked successfully. Could you clarify why you recommended using Managed Environments?
I just retried and it now looks like there's been a slight alteration. The message now states "Target environments must be managed". So it might have let you work this on the source system but when it comes to the targets, they'll all need to be managed. Hope that clarifies . --Brian
@@PragmaticWorks Yeah it was right on the top about the "Target environments must be managed", but even Target worked without making to Managed.
Does solution checker run automatically in the pipeline? Or do I need to do something? I have managed environments so feature itself is there.
Thanks for the overview! Very useful. I'm curious how would this work if I want to sell my PowerApp. How do I publish it to my clients environment and/or to the windows apps store (What would you recommend?)
The pipeline feature is isolated to a given tenant so you'd have to do the traditional export / import option for your client. Depending on your customer relationship, you could import unmanaged into their dev and let pipelies take over from there. - Brian
Great Video! You mentioned the ability to configure approvals on the pipeline. I currently have a Dev --> Test --> Prod pipeline running which is great for source control and deployments. The major downfall I am running into is having to hunt down my test users to verify changes and publish to Prod. Would it be possible to get a video showing how to implement the approvals? something like Dev publish to Test, approvals assigned to the user group of the app, once approval is completed a task is assigned to publish to Prod.
Great idea! 💡I added it to my queue - Brian
Hello :) thank you for this content.I have two questions, and I’m hoping you might be able to assist. First, I noticed a new security role called "Deployment Pipeline Default" when I was trying to add roles. I haven’t seen any mention of this in the documentation. Does anyone know more about it or could provide some guidance?
Secondly, regarding solution artifacts, I’m curious about the zip file-is it stored permanently, or will it be deleted at some point?
Thanks in advance for any insights you can offer!
Since making this video, the interface app will now give you the option to specify who is allowed to use the pipelines you created. These are using the Pipeline security roles like what you mentioned, so much easier to config.
In addition, the solution artifacts are stored forever until you purge them. You can create a Dataverse purge process to remove old artifacts if you wish though.
@@PragmaticWorks thank you for the quick response :)
I couldn't find any documentaiton comparing the three security roles (admin, user, default). any idea where to find that?
I also thought that Deployment Pipeline User Security Role defines who is allowed to use the pipeliens I created. for Deplyoment Pipeline Default I only found: Can I enable makers to create personal pipelines in a custom host?
Yes. As an administrator, you can assign the Deployment Pipeline Default role to anyone you want to grant lightweight pipeline creation permissions to. Administrators can also add users to the Deployment Pipeline Maker team via the Security Teams page in the Deployment Pipeline Configuration app.
This Deployment Pipelines Default role isn't assigned to anyone by default in the case of custom host, so the lightweight personal pipeline creation experience is only visible by default in environments that aren't already associated with a custom host.
@@PragmaticWorks
I have another question. I want to share a pipeline with a group rather than an individual user. I added an O365 group to the host pipeline under Settings -> Teams in admin.powerplatform, but it doesn't appear as an option for sharing in the pipeline application. However, if I add the security group in the application under Settings -> Security Teams -> + New, then I can share it with the group. Why is it necessary to set the group in the application and not in admin.powerplatform for the environment?
There are lots of shortcomings. It just didn't demand the premium license however it also demands Maker access on target environment for the user who is running the pipeline. I can still digest that organization can somehow provide the premium license to users however providing maker right to business is difficult.
❤
Hello, I am new to powerapps, How dev env deployed first before deployed test ?
I am really struggling with Environment Variables in the new Pipeline. For each target environment I'd like to specify the value of each env. variable (that's kind of the idea behind them after all). I can get this to work by a) not setting a default value and b) removing all "current values" from the DEV environment. Success: During Deployment I get asked to specify the values! However each subsequent deployment, I get an error: "Cannot insert duplicate key in object 'dbo.EnvironmentVariableValueBase'. ". Weird! I'm not trying to insert a duplicate key, I'm trying to overwrite it... Other people have recommended deleting the EV from DEV and recreating it, but that seems like a hack to me.
Great video, but as @KyleSchroeder says, its unfortunate that it requires all users to be premium. It would be better either if Microsoft changed that so all users/apps didn't have to be premium, or if the last target in the pipeline didn't have to be a managed environment (even if all interim sources and targets did). We are really struggling with how to best manage our licensing vs. feature sets and Microsoft is not making it easy for those of us who have a combination of premium connected Apps and standard Apps.
I build my pipeline using the following: Dev (Developer and Managed=yes) to Test (Developer and Managed=yes to Prod (Developer and Managed=yes). I installed the Power Platform Pipeline App in my 'Host' Environment which is a Trial Environment and not Managed. This works fine for learning and testing. My question is this: Is there currently a way to use this kind of pipeline to rollback a solution to a lesser version (other than doing a manual export/import). None of this costs me anything while testing. Thanks.
Are you AI and learning from videos lol. From the discussion I had with Microsoft, once you have deployed a solution, you can only increase the version, or you may have to totally delete the solution. So, effectively, you could increase the version number in solution.xml of the older solution(CurrentdeployedSolutionVersion+1) and use upgrade option to deploy it.
Hi Brian, Thanks for the video. I tried to set up pipeline as per your instructions, but when I create the Dev, UAT, Production environments using the environment Id, I am getting this error "Environment 9e9a7697-9cc9-47d7-8d6c-8655f36404a7 is already configured with Pipelines in host environment 9f0e98b9-addb-e45c-b8a5-921e649f6cc6. Please delete the environment from the other host to add the environment to this host environment 9e9a7697-9cc9-47d7-8d6c-8655f36404a7 or perform a Force Link." I could not find the environment with guid "9f..." would it be OK to use Force link. Another question is our UAT is an Un-managed environment - can we use this pipeline to deploy to Un-managed environment. Though I read everywhere that Pipelines can only be implemented for managed environments.
Everyday, there's less and less you can do with a regular license :/