Introduction to Pipelines for Power Platform | Deploy Solutions to Environments | Tutorial

Подписаться 128 тыс.

Просмотров 75 тыс.

50% 1

Power Platform Pipelines aims to simplify application lifecycle management (ALM) for Power Platform by bringing deployment automation capabilities in a manner that’s approachable for all makers, admins, and developers.
Create and run pipelines to easily deploy solutions to environments.
Pipelines can be setup and run entirely within Power Platform - with governance, visibility, and safeguards automatically built in so that your business solutions can come to market faster with less effort and higher quality.
Pipelines significantly reduce the effort and domain knowledge previously required to realize the ROI from adopting healthy, automated ALM processes within your team or organization.
Advantages of Pipelines:
✅ Admins easily configure automated deployment pipelines in minutes.
✅ Makers have an intuitive user experience for easily deploying their solutions.
✅ Professional developers can (optionally) run pipelines using their preferred tools such as the Power Platform command line interface (CLI).
Power Platform administrators can create one or more pipelines, associate any number of environments, then share access with those that will administer or run pipelines.
Pipelines deploy solutions as well as configuration for the target environment such as connections, connection references, and environment variables
#PowerPlatform #Pipelines #ALM #CICD
References 🔗:
Automate deployments with pipelines in Power Platform
powerapps.microsoft.com/en-us...
Overview of Power Platform pipelines
learn.microsoft.com/en-us/pow...
Set up Power Platform pipelines
learn.microsoft.com/en-us/pow...
Run Power Platform Pipelines
learn.microsoft.com/en-us/pow...
Managed Environments
learn.microsoft.com/en-us/pow...
Table of Contents:
00:00 - Introduction to Pipelines for Power Platform
00:51 - Setup Pipeline Host Environment
03:07 - Setup Environment Information in Deployment Pipeline Configuration Power App
05:29 - Define Linked Development environments & Deployment stages for Pipeline
07:34 - Grant access to Makers to run Power Platform Pipelines
08:28 - Run Pipeline - Automated Solution deployments across environments
10:54 - Pipeline Run History & Solution Artifacts
11:46 - Subscribe to Reza Dorrani channel
🤝 Let’s connect on social:
🔗 Reza Dorrani LinkedIn: / rezadorrani
🐦 Reza Dorrani Twitter: / rezadorrani

Наука

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

30 июн 2024

Ссылка:

Скачать:

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

Добавить в:

Мой плейлист

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

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

@RezaDorrani Год назад

Important Notes: 1 - The new Developer environments can be used in pipelines for dev & QA w/o needing premium licenses. Only end users in the prod env will ultimately need premium licenses (and not until pipelines GA). Makers won't need unless they're also an end user in prod. 2 - Environment Type can be Production, Developer, Sandbox etc. (only Dataverse for Teams based environments are not supported) 3 - All environments part of a pipeline configuration must be in same region as host environment for Pipeline. 4 - You can create multiple host environments. 5 - You can create upto 7 stages in pipeline configuration.

@CatherineChazelas-bu7ob Год назад

thank you for the presentation. if i understand well, all basic users and app makers will need a premium license?

@CatherineChazelas-bu7ob Год назад

last question: is the Managed environment replacing devops tool?

@neverusethis000 Год назад

Great Presentation like always Reza !!

@RezaDorrani Год назад

@@CatherineChazelas-bu7ob Yes

@RezaDorrani Год назад

@@CatherineChazelas-bu7ob No

@branislavblatnjak1671 Год назад

Thank you for producing these videos Reza. They are really well made, and you are great at explaining topics.

@RezaDorrani Год назад

Glad you like them!

@diegoecoo 8 месяцев назад

Your teachings are so clear! You are a great reference! Thank you for helping us to improve as professionals.

@RezaDorrani 8 месяцев назад

Thanks so much Diego

@yoismelperez2744 Год назад

Thanks Reza. I have been reading about this in the last couple days and now this video just answered almost all the questions I had.

@RezaDorrani Год назад

Glad to hear that the video has answered most questions. Thanks for watching.

@s961201 8 месяцев назад

You are phenomenal, Reza! Love your pedagogical approach both in the visuals and narrative :-) And it's always so relevant to my challenges!

@RezaDorrani 8 месяцев назад

Awesome! So happy to hear the feedback. Thanks so much Preben

@swapnilwani7084 6 месяцев назад

First time going to try this Pipeline deployment, really happy to see your video.. thanks for that and keep sharing!! :)

@RezaDorrani 6 месяцев назад

Thanks for watching

@SHAli1474 Год назад

Another brilliant feature explained brilliantly. Thanks Reza

@RezaDorrani Год назад

You are most welcome! Thanks so much for watching.

@oluwatobipaul6171 Год назад

Thank you Reza. It is indeed a useful way of deployment process

@RezaDorrani Год назад

Glad it was helpful!

@satyenkasturi Год назад

As usual.....very detailed...... you have answered few of my questions.... Reza. Thanks

@RezaDorrani Год назад

Glad to hear!

@EWPiano 5 месяцев назад

Exactly what I needed. Thank you!

@satyenkasturi Год назад

Thanks Reza. Very cool feature, especially when you have multiple flows and components.

@RezaDorrani Год назад

👍

@AmmarRamadan Год назад

Thank you Reza, very useful way of the deployment process, if we can do this across different tenants that will be boom!!

@RezaDorrani Год назад

Currently, across tenants is not supported.

@antonioskokiantonis7051 Год назад

Microsoft is working on it.

@danielmilloc2289 11 месяцев назад

Can solutions be exported to another tenants?

@AmmarRamadan 11 месяцев назад

@@danielmilloc2289 yes

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

Flawless video Reza!!! Thanks a lot!!!

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

My pleasure!

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

Absolutely amazing, THANK YOU

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

You're very welcome!

@venumadhavravulapalli1463 Год назад

Awesome update Reza... Highly useful. Thank you

@RezaDorrani Год назад

Most welcome

@Father_Prime Год назад

Thank you so much for this, Reza. It is amazingly helpful! Several follow up questions: ENVIRONMENTS: (1) Does Sarah only need to be added as a Maker in the Pipeline Orchestrator & Dev Zone Environments? (2) What should her access level be in the Test & Prod Zones? SECURITY ROLES: (3) How should Sarah's Security roles be configured in order to have proper access to this solution in the Dev, Test, and Prod Zones? (4)Are there any other roles beyond the Pipeline User that she would need? USERS: (5) What would the best practice(s) be for user addition to/management in the Test and Prod Zones? (6) When sharing the app with new users, does it matter which environment the "share" link is sent from? DATA STORAGE: (7) Let's say an App developed in Dev Zone leverages Dataverse for record storage. Once ready, that App is deployed in Prod Zone. Will users in Prod Zone still be able to enter/read data in the table through the Prod Zone App, even if they cannot see the Dataverse table itself? Apologies if these have already been answered. If you have other videos explaining these, please do link them.

@RezaDorrani Год назад

1 - Sarah does not need Maker Access in Pipeline Orchestrator. Sarah would need "Pipeline User" role & the pipeline config record must be shared with Sarah - both are shown in video. 2 - Sarah would need maker access in dev, test and prod. 3 - Sarah would need maker role in dev, test and prod. 4 - Pipeline user role + record shared (as shown in video) 5 - learn.microsoft.com/en-us/power-apps/developer/data-platform/user-team-entities 6 - No 7 - As long as user has the security role that grants access to tables which app connects to, they can access it.

@Father_Prime Год назад

@@RezaDorrani got it. Thank you so much for the thorough response! I really appreciate it and look forward to more videos.

@maamirkhan2005 10 месяцев назад

as always, great, great, great work!

@RezaDorrani 10 месяцев назад

Thank you! Cheers!

@ketanpimple1933 10 месяцев назад

Amazing 👏 thanks Reza for sharing this.

@RezaDorrani 10 месяцев назад

Most welcome

@SauloOliveira Год назад

Thank you for sharing Reza.

@RezaDorrani Год назад

You are most welcome

@ItsMeProday83 Год назад

Thanks Reza, great video!

@RezaDorrani Год назад

Most welcome

@MrGaztab Год назад

Great video. Thanks again Reza.

@RezaDorrani Год назад

Most welcome

@manjunath5727 Год назад

Thanks for the clear explanation

@RezaDorrani Год назад

Most welcome

@shrutidwivedi2142 7 месяцев назад

Hi Reza, Thank you for Great Video.

@RezaDorrani 7 месяцев назад

Most welcome

@iliyasshaikh4206 Год назад

Thanks Reza. Nice demo. Finally Microsoft made something on deployment pipeline. Looking for more advanced feature like option for deploying unmanaged solution, continuous deployment, approvals,etc.

@RezaDorrani Год назад

This is V1. A lot more to come.

@andreasvanbergen9696 Год назад

Thanks again Reza! 🙏

@RezaDorrani Год назад

Most welcome

@venkatasubbaraopolisettymv3802 Год назад

Thank you Reza for another great video, looking forward for the unmanaged solution deployments as well to get real strength!

@RezaDorrani Год назад

Let's see if and when it makes it to Power Pipelines.

@satyenkasturi Год назад

Deploying to Unmanaged.......we are opening up a can of worms. LOL.

@RezaDorrani Год назад

@@satyenkasturi it could be deployment across dev environments

@venkatasubbaraopolisettymv3802 Год назад

@@satyenkasturi : We have 5 development teams working in 5 different dev environments before they go to test. Hope you get my pain point here .

@satyenkasturi Год назад

@@venkatasubbaraopolisettymv3802 I understand Venkat, but my point is deploying to Unmanaged (Production Env.)means you are allowing the code changes in that environment. Specially when there are different teams any one can change the code to fix minor error or add simple enhancement. Now you lost the sync.

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

the best Reza. thank you

@KrishnaRachakonda Год назад

Very detailed demo Reza. Thank you.

@RezaDorrani Год назад

Most welcome

@shjohn28 Год назад

Great video!! Thank you!!

@RezaDorrani Год назад

Most welcome

@pranavkahol5925 Год назад

Thank You Reza!!!

@RezaDorrani Год назад

Most welcome

@iektech Год назад

First of all, thanks for this demo Reza, it really helped to get started, now while the approach seems to be very helpful to make your deployment process more straightforward, we have found a little glitch that is preventing us from approving this tool for general use, the issue is with Environment Variables, seems that for some variables (not all, even if they are the same type), the value on the destination environment gets overwritten with the one set on Dev, for example, let's say that you set your values on QA on a first deployment and don't expect to update them later, so you ensure the values are set in Dev too so you are not prompted for those values again, run the pipeline process and then when looking at QA variables have been overwritten, curiously enough if we do it with the manual deployment process this doesn't seem to happen. 🤷‍♂

@RezaDorrani Год назад

I have not experienced this behavior. Note: Pipelines is currently in preview. Hence not recommended to use in production scenarios until it goes GA.

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

You can use free DevOps with a Pipeline to avoid this as you can set the variables in YAML or through the Pipeline steps. Also, with DevOps you do not need to run Managed Environments so you avoid the full licensing costs required for Managed Environments.

@NEHAGUPTA-fb5yl Год назад

Thankyou so much,very helpful

@RezaDorrani Год назад

Most welcome

@nadeemhassan8301 Год назад

Well explained . Thanks

@RezaDorrani Год назад

Most welcome

@bensalins 9 месяцев назад

Thank you for the content.

@RezaDorrani 9 месяцев назад

Welcome

@badiualex23 Год назад

Thank you @Reza Dorrani ! Your video is awesome as usual and the V1 Pipelines are great! I have 2 questions regarding the video. 1. You mentioned that the host environment does not need to have Managed Env enabled, but all environments that will be part of the pipeline deployment process should. Does this apply to DEV environment as well? (usually DEV env is unmanaged) 2. The entire experience requires Microsoft Dataverse. That means we need to have Dataverse licensing even though all our apps in the solution are based on SharepointLists? It would be really great to be able to set up the pipelines even though we do not (yet) have Dataverse. Thank you in advance for your reply! Keep up the great job !

@RezaDorrani Год назад

1 - Dev needs to be a managed environment. Don’t get confused with managed/unmanaged solutions :) You will have unmanaged solutions in dev. 2 - Managed environments requires Dataverse and premium license for all users. I understand the SharePoint scenario from a licensing perspective but Pipelines is a premium feature.

@chadtaylor4539 Год назад

Awesome video as always! I was hopeful there would be a way for citizen developers to run pipelines without having System Customizer role (or sys admin if custom security roles are in the solution) in the production environment but I don’t believe that’s possible. Would be nice to keep prod as locked down as possible but grant users the ability to deploy their solutions as they wish.

@RezaDorrani Год назад

Its great feedback. I will share with the team. Currently Maker role is needed at a minimum to deploy the solutions across environments.

@elvismakuthi Год назад

Thank you Reza this really helpful

@RezaDorrani Год назад

Glad it was helpful!

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

Thank you for the great content. You have been my greatest inspiration. I never go wrong with your video tutorials. Are you planning to make a video on Wrap for Power Apps?

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

Most welcome! Not planning a video on wrap as I have received very few requests on that topic.

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

Thank you@@RezaDorrani

@vaibhav2741 9 месяцев назад

Excellent 🎉

@RezaDorrani 9 месяцев назад

Thanks

@galleon8129 10 месяцев назад

Ah alas, been looking for this for ages. Why are there few people making videos like this on Power Platform?

@RezaDorrani 10 месяцев назад

Probably because very few people are watching these videos. Viewership for basic videos on app and flow development are higher. I do like mixing up though and hence made a few videos on ALM and Solutions.

@danielwu8660 Год назад

Reza thanks for another amazing video! Currently from what you demoed, the pipeline need to be manually triggered Stage by Stage, only saving the export import time. Since the Stages & pipelines are managed as Dataverse records now, do you think we can potentially do some automation with Power Automate like we did to DevOps CI/CD pipelines? For example what we did in DevOps pipeline was: DEV deployed to TEST (manually triggered) -> On completion, approval email send to QA for validation / testing in TEST environment -> On approved, the deployment of TEST to PROD is automatically triggered without the need of manual action from user.

@RezaDorrani Год назад

Thanks for watching and liking the content. Currently its manual - this is V1. A lot more is planned and coming. Check powerapps.microsoft.com/en-us/blog/power-platform-build-tools-and-azure-devops/

@branislavblatnjak1671 Год назад

Thanks!

@RezaDorrani Год назад

Thank You

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

Excellent

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

Thanks

@ashokpershad Год назад

Thank you Reza wonderful video. Please make one video related to WRAP feature for Android if possible.

@RezaDorrani Год назад

Thanks for watching. I make videos when I get multiple requests on a topic. Every quarter I ask subscribers for topic suggestions on community tab of my channel. Most voted topics get added to my backlog. It would be best to post this idea in next topic suggestion post.

@charlesdawnbeltran9603 Месяц назад

Again a superb video from Reza that is really applicable to my project. If I have one dataverse table being utilized by multiple solutions. In terms of deployment, do I need the to add same table to all solutions utilizing it, or adding it only to the main solution?

@RezaDorrani Месяц назад

Main solution is enough

@julien8979 Год назад

Thank you Reza for sharing. Does it support to "Export configuration/master data" to the environment which is very similar to how we usually do it in either Azure DevOps/CDS Configuration Migration Tool?

@RezaDorrani Год назад

learn.microsoft.com/en-us/power-platform/alm/pipelines Check Q/A section at end of documentation.

@balasabarishudayakumar9235 Год назад

Thanks Reza, helps everyone to have a quick understanding on Power Pipelines. Can I implement this between two different tenants? Also is it possible to move from Default Environment to specified Dev/Uat/Prod?

@RezaDorrani Год назад

Currently, cross tenant is not supported. You can move from dev to specified environments (defined in pipeline configuration as shown in video, however currently it will move solutions across environments as managed solutions only.

@GjergjiKoleka Год назад

Dear Mr. Reza. I have recently started to follow your work and took advantage of your Leave Request App. Can't thank you enough not only for the free release but also for the quality of work and detailed walkthroughs...to me that is unparalleled in this space. I was wondering if you have developed any staff performance evaluation app or if you plan to do so in the future (already subscribed to your blog)? . Thank you again and keep up the good work. Sincerely, Gjergji

@RezaDorrani Год назад

Thank You Gjergji for following and liking the videos. I have not built any videos on staff performance evaluation and currently have no plans to build one in future. Every quarter I ask subscribers for topic suggestions on community tab of my channel. Most voted ideas get added to my backlog.

@GjergjiKoleka Год назад

@@RezaDorrani Thank you for the prompt reply. Br

@abhishekinvisible Год назад

Amazing

@RezaDorrani Год назад

Thanks

@arihaanjindal548 Год назад

Thanks for the informative video, I always look forward to your new videos and functionality explained to use in our workings.. this is of great help. While we were searching through automating deployment of our Apps (Canvas app and many flows more than 100 in one app.) created, we understand that the first step is to integrate all of them inside solution. Is there any suggestion to automate this thing because it will be like creating app and flows from scratch and integrating inside solution. We have flows some of them are coupled with app while many other are independent flows as well. Looking forward response and expert suggestion for this .

@RezaDorrani Год назад

100 flows in an app. Must be an extremely complex solution. I don’t think there is any easy way to achieve this. My policy is always to build things in solutions to begin with.

@srinivasacharyvishwanadula787 9 месяцев назад

Hi Reza, Thanks for this awesome video as always. So this video is also referred as CI & CD in PowerApps right !!

@RezaDorrani 9 месяцев назад

Yes

@billkuhn9886 Год назад

Great video! In instances where you are deploying the same solution, but with changes (so a different version number) are the managed solutions being deployed using the “Upgrade” option?

@RezaDorrani Год назад

I believe it uses upgrade under the hoods

@spen2431 Год назад

Nice one Reza ⭐⭐ How does this work with security groups? ie a testers group and a "live"(all users) group? Or is that all still managed separately in each environment?

@RezaDorrani Год назад

Managed in environment

@paolovr1970 Год назад

Thanks Reza 🙏🙏🙏

@RezaDorrani Год назад

Most welcome

@itvtheworldofknowledge5652 Год назад

Sir, please make one playlists of learning step by step 1 ,2 3,... Of your total video on channel to make learning easy

@RezaDorrani Год назад

I have organized all videos in playlists based on topic. Most of my videos start with simple content and then I show more advanced cases.

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

nice video

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

Thanks

@misganawkibret603 Год назад

Thank you Reza

@RezaDorrani Год назад

Welcome

@banksa71 Год назад

Reza, thanks for the this informative video. I was wondering if there is a way to target solution artifacts in an environment. If I have more than one solution can a pipeline be set up for a specific solution.

@RezaDorrani Год назад

Pipelines are specific to an environment. Not solutions.

@mkhijazi Год назад

Thank you Riza for your efforts. A question: is there any licensing requirements required to use this feature?

@RezaDorrani Год назад

Yes, needs managed environments which require premium licenses for all users part of the environment.

@raychoe7390 Год назад

I've always appreciate your insight knowledge. My question is once I am in the solution in the dev environment, I don't see pipelines under history icon. Am I missing some sort of set up in Power Apps?

@RezaDorrani Год назад

Power Pipelines must be configured in tenant. The dev environment must be part of a pipeline. The environment must be a managed environment.

@ppl111 7 месяцев назад

Thank you for this video. So we dont need Azure DevOps Pipelines for PowerApps CI / CD anymore?

@RezaDorrani 7 месяцев назад

This does not have source control. You can use pipeline extensions to save solutions managed/unmanaged in source control using ADO or GitHub

@DriantX Год назад

Nice quick introduction, thanks. Was there any reason for DEV/TEST environments to be set as production instead of sandbox?

@RezaDorrani Год назад

They could be sandbox or production. In my case I had those environments setup as prod type. No specific reason.

@DriantX Год назад

@@RezaDorrani Thanks for the clarification & quick response! Much appreciated.

@abdurahmanjardine6467 Год назад

Thank you Reza for the video. This is extremely useful. The only concern I have with this is that all the environments have to be managed environments. This might work well for a small company but for an organization with +-28000 users this is not feasible. Microsoft's licensing model needs a serious review, its just not practical. We would love to benefit from the ALM capabilities for our environments but the cost will be too high. We implemented DevOps pipelines for this, however its clunky and this seems more straightforward and intuitive. Secondly, does the pipelines allow for approval between deployment steps at the moment? Based on your demo, I haven't noticed any settings in relation to that. I will set up my own lab to investigate the capabilities as well.

@RezaDorrani Год назад

Please check comments in video. These questions are covered.

@naveenkarla Год назад

Thank you Great Video as always! so no Azure Devops or Github subscription needed anymore or are they still relevant?

@RezaDorrani Год назад

Not needed if Power Platform Pipelines meets your ALM needs but there will be options to integrate with devops and more in future.

@arydias85 6 месяцев назад

Hi, brilliant video. Quick question. Is it possible to share only stages of the pipeline ? I want to allow every developer to deploy to UAT but only a select few to deploy to PROD

@RezaDorrani 6 месяцев назад

Currently you would need to share the entire pipeline. If you concern is access to prod, now we have a new feature which is SPN based deployments. Check the documentation.

@christerrussberg3059 Год назад

Hi Reza, Thanks for a great video. Some questions. 1) What is your prediction that this function will reach GA? 2) As i understand the soultion that is being deployed can have a SharePoint list or Dataverse as datasource. Is that correct?

@RezaDorrani Год назад

1) Not aware of GA date 2) Yes

@antonioskokiantonis7051 Год назад

I've created the Host environment as a non-managed, but I had difficulties during the pipeline procedure, with a pop-up stating that the environment must be a managed-one. After I've created it as a managed, it worked fine.

@RezaDorrani Год назад

Should not be the case. Might very well be a bug.

@allenzhang7407 5 месяцев назад

Thank you for the great video! One question, in this scenario, do we still need to create a patch for a solution? Or we just update the solution and deploy again through the pipeline? If we create the patch, do we put the patch into the pipeline?

@RezaDorrani 5 месяцев назад

Pipelines only does upgrade as I know. No need for any patch or any setup. Everything is handled for us. Simply deploy the solution.

@allenzhang7407 5 месяцев назад

@@RezaDorrani thank you so much Reza!

@firmhand Год назад

thanks for the video! how much would this setup cost in your estimates? how do makers change solution version of they are not exporting manually anymore?

@RezaDorrani Год назад

Setup cost - same as licensing for managed environments - learn.microsoft.com/en-us/power-platform/admin/managed-environment-licensing Solution version option is auto setup as shown in video. Pipelines default behavior is Upgrade with Maintain customizations.

@cambly2701 7 месяцев назад

Could you please make a video related to Appsource depolyment Package creation, or maybe a link recommendation. Your insights are always valuable.

@RezaDorrani 7 месяцев назад

Documentation would be the best recommendation. I make videos when I receive multiple requests on a topic. Every quarter I ask subscribers for topic suggestions on Community Tab of my channel. Most voted idea gets added to my backlog. Make sure to post this idea whenever I post the next topic suggestion post.

@senthilkumarchandran3680 5 месяцев назад

Thank you for the wonderful video. I have deployed multiple versions of the same solution to the Target environment. Is there any way in the pipeline I can redeploy the previous version of the solution to the target environment? I can see the run history for the pipeline, but I am not finding the option to redeploy to the previous version.

@RezaDorrani 5 месяцев назад

You can only deploy higher versions.

@andyhurd5796 5 месяцев назад

Hi Reza, great stuff, concise and clear as ever. One question around Publishing: when you export solutions manually the UI always prompts you to Publish Customisations (which you should do if you haven't already!). Do you know if Power Pipelines remove the need to Publish all, or is this still a recommended manual step before triggering the deployment?

@RezaDorrani 5 месяцев назад

Thanks! Pipelines I believe does a publish prior to exporting but no harm in performing that action prior to publishing.

@andyhurd5796 5 месяцев назад

@@RezaDorrani it would be odd if it didn't publish first, but as you say, no harm in making sure (except I find it often times out manually!)

@jherizaldo11 Год назад

Hi Reza, Thank you for this! It was really helpful. I just have few questions: 1. Can I use a sandbox environment as a host? 2. Any recommended capacity storage for the host environment? 3. Can I use sandbox environment for target development environments?

@RezaDorrani Год назад

Currently pipelines is in preview so I believe no restrictions. But once GA, I believe it host must be production. Capacity recommendations will be updated in documentation once GA. Currently, you could use sandbox. Im not 100% certain about my answers as this feature is in preview.

@jherizaldo11 Год назад

@@RezaDorrani thank you for the quick response. I can't find any documentation regarding that questions also. So last thing to do was to try. I'll give a feedback here too once I've tested it. Thanks again!

@RezaDorrani Год назад

@@jherizaldo11 Reason for no detailed documentation is because its a preview feature.

@avinashhiradodde7246 Год назад

Great Video RD, Can we deploy solution as unmanaged in targeted environments by using this method ?

@RezaDorrani Год назад

Currently, No

@avinashhiradodde7246 Год назад

@@RezaDorrani thank you for confirmation.

@anantv10 Год назад

Great Work, Can we do this same for Power Pages.

@RezaDorrani Год назад

Im not sure about pages.

@eugenevanbetonio7314 Год назад

Thanks for the video Reza. I have question, where or how can we set the environment variable when we are using the pipeline?

@RezaDorrani Год назад

If they are a part of a solution and setup as shown in this video ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Xo-TvZ9N3BM.html They will show up when running the pipeline

@eugenevanbetonio7314 Год назад

@@RezaDorrani Cool. Thank you!

@Linex1986 10 месяцев назад

Great video, Thank you I have DEV-TEST-PROD I did multiple deployments from DEV to test and to PROD, but now we need to change a SharePoint list. I didn't find any way to remove previous environment variable value in TEST and PROD, just never prompts for value after first successful deployment. Only way works is to delete solution from TEST and PROD, this option might work in some scenarios but in case we have dataverse tables with data deleting solution also delete all custom tables :( I was trying to see if somehow deleting deployment artifacts in host environment might help to trigger the prompt for new variable values, but nothing...

@RezaDorrani 10 месяцев назад

I have not come across this issue and hence not sure what is the cause for your issue. I recommend posting your issue/query with screenshots on the forums at powerusers.microsoft.com

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

Great video! How we can prevent developers from creating solutions and flows on Test and Prod, so that they're forced to create it on dev and then use pipelines? Shall we just do not give them app maker role on Test and Prod? Will they be able to still test and run their solutions? Or maybe there is smarter way of doing that?

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

Check documentation on delegated departments via pipelines.

@danielmilloc2289 11 месяцев назад

Very interesting to know this! Is there currently a way to retract a solution that has been deployed?

@RezaDorrani 11 месяцев назад

powerusers.microsoft.com/t5/Power-Apps-Governance-and/Rollback-Solution/td-p/821607

@user-oq5sd9fb9j 7 месяцев назад

Hi @Reza Dorrani, A great video from you...May I ask you a quick question if that's ok. By using Power Platform pipelines how to update or upgrade solution while deploying the solution?

@RezaDorrani 7 месяцев назад

Pipelines only does upgrade I believe. There are no choices.

@user-oq5sd9fb9j 7 месяцев назад

@@RezaDorrani , Thanks for answering. Is there anywhere I can find such information on Microsoft websites I tried to find but couldn't find anywhere.

@RezaDorrani 7 месяцев назад

@@user-oq5sd9fb9j Documentation has it all. Simply search on web for pipelines for power platform documentation

@JohnAckery 11 дней назад

Hi Reza, thanks for the fab video. FYI, I have been able to configure these pipelines as per your video. Great stuff! Thank you!! Do you know if there is any validation on the solution before a push from DEV to TEST or TEST to PROD? Does each deployment get versioned, and do we have a 'Roll back' option if needed? I assume that we only push logic from DEV to TEST to PROD and that all underlying fact data in the PROD application is always un-changed.

@RezaDorrani 11 дней назад

Solution checker is available for validations. Each deployment solution is saved (version available) and I believe rollback option is coming soon. Data stays intact.

@JohnAckery 10 дней назад

@RezaDorrani Hi Reza, thanks for the prompt reply. Do you know if Pipelines can be used across tenants? Here is the use case: If we build a standard solution for several customers, can we use pipelines to update new features across many PROD environments in different tenants?

@RezaDorrani 10 дней назад

@@JohnAckery Pipelines currently does not support cross-tenants

@vaithikarthi7380 Год назад

Video is Simply Awesome ❤ would like to know do we really need to have separate environment to configure pipeline information.will it impact if we install powerapp pipeline solution in dev environment.

@RezaDorrani Год назад

It must be a different environment. You do not want to store pipeline configuration information in a dev environment.

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

@@RezaDorrani thanks for this awesome video as always. would like to know what would be the issue if the pipeline config is in the DEV environment

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

@@reivaxmik9058 Check documentation to see the requirements.

@blink182joel Год назад

If you made changes in Dev and used the standard Dev>Test>Prod pipeline, when you deploy to Test again, will it recognise that it already exists, and simply overwrite/upgrade, with an incrementing version number?

@RezaDorrani Год назад

Yes it would

@enitesh Год назад

Sorry for the question. But the licensing part is a bit confusing for me. All our users have E5 license. So will they require additional license to run the app which are on managed environments? And will it require additional license to run the model driven app on host environment ?

@RezaDorrani Год назад

Power Apps premium licenses will be required for all users. E5 does not cover premium licenses.

@dhananjaykharade2711 5 месяцев назад

Great video. What would be the right way/strategy to deploy the Canvas apps across Dev/Test/Prod env.?

@RezaDorrani 5 месяцев назад

There is no right way. There are options. Pipelines is an in-product experience, simple to configure and use. Video shows canvas app deployment.

@dhananjaykharade2711 5 месяцев назад

@@RezaDorrani Thanks a lot for the response.

@SmartLearningAI 7 месяцев назад

Great. Is there a best method way for Sarah to replace the Production deployed version with the last known good (working solution) if the latest solution has too many errors? I don't mean re-deploy but more like backup / restore or other options. Ie a temp quick fix for the production application solution while Sarah works on fixing the issue(s) in Dev before re-deploying to Test and Production again.

@RezaDorrani 7 месяцев назад

Making changes in production is not a recommended option even for quick fixes. Best practice is to go from dev-test-prod

@pallavigupta8378 Год назад

HI Reza.Thanks for amazing content.Just wanted to understand is it necessary to make host environment as PRODUCTION?

@RezaDorrani Год назад

I’m not 100% sure about that. Check the documentation on pipelines. I would say it would be best to make it production type as it would be a permanent environment.

@pallavigupta8378 Год назад

@RezaDorrani thanks Reza.I was thinking to do it for a demo within my organization.Will it be ideal in that case?

@RezaDorrani Год назад

@@pallavigupta8378 Im not sure if it even allows non prod environments. Hence was asking to check documentation. If it allows then use it for demo.

@pallavigupta8378 Год назад

Thanks a lot.Really appreciate all the good work you are doing.Thanks for always helping.

@mehdichellak4373 Год назад

It's a great video as always, but I have a question about how we can handle versions rollback with pipelines?

@RezaDorrani Год назад

Currently, it does not handle versioning

@mehdichellak4373 Год назад

@@RezaDorrani thank. You sir

@09prasad Год назад

Hi Reza, First of all thanks for such useful video. I tried this but it's not asking to configure key vault values. Is there any way out for this?

@RezaDorrani Год назад

I have not tried specifically with key vault but it should ask for the same. Ensure you follow steps shown in video for environment variables prior to deploying solution. I may have also shown that in a separate video on environment variables.

@samawel83 Год назад

Amazing! Thanks Reza.. Is it possible to add Power Pages to the pipeline?

@RezaDorrani Год назад

Whatever can be added to a solution can be added to pipeline. I don’t believe pages are solution aware yet but I have not done much work with them.

@samawel83 Год назад

@@RezaDorrani Thanks for your quick reply. In this video (ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-uILb28j4lso.html), Phil Topness asked Kartik if this is going to work for power pages (3:24). The answer was absolutly. So let's wait for that :) 🤞🤞

@RezaDorrani Год назад

@@samawel83 :)

@subodhmoktan2448 Год назад

Hi Reza, Thank you for the video. I am trying to set up pipelines for our organization. I created and configured the pipelines as you showed above. The problem is when I share the pipeline with the user, we do not see the pipeline icon on our dev environment inside the solutions. Is it something that needs to be turned on? I supposed it should show up in environments with "Development Environment" environment type. Any help or suggestions will be appreciated. Thanks.

@RezaDorrani Год назад

Check documentation on pipelines for prerequisites needed. Managed environments must be enabled, user needs maker rights in downstream environments and more.

@jslj5774 Год назад

Great video, I have succeded to depoly to the test enviorment but after that I can't further deploy it to the production env, the solution becomes managed and checked and I think that stops it from not being deployed further. Also I noticed when a solution is managed and checked the pipline button on the side panel dosent show up.

@RezaDorrani Год назад

Pipelines currently only deploys as managed. As shown in video, it can be moved to higher environments. I would recommend posting your issue with screenshots on the forums at powerusers.microsoft.com

@jslj5774 Год назад

@@RezaDorrani Thanks, I did but im not getting any any answers. When I try to depoly from Test env to Prod env I get the error message: ''The request message was already sent. Cannot send the same request message multiple times.''

@RezaDorrani Год назад

@@jslj5774 Not sure about this as I have not faced this issue. Forums will be your best bet.

@Samshujayanagar 6 месяцев назад

Hi Reza, You are amazing as always 🤝 after seeing this video I’ve created a flow in the solution. Later I created a copy of the same flow inside my flows tab which is not showing in the add existing cloud flow option. Did I do anything wrong 😑

@RezaDorrani 6 месяцев назад

Why would you create a copy of the same flow? If flow is in solution, simply make changes there in dev and then deploy via pipeline

@Samshujayanagar 6 месяцев назад

@@RezaDorrani Thank you for your reply. I’ve 5 different lists connected to the app. So wanted to trigger an email with some conditions every time a new item is created in those lists. So thought of creating the copy and modify the steps wherever required because most of the steps remain same.

@RezaDorrani 6 месяцев назад

@@Samshujayanagar I would recommend checking on forums in case someone has done something similar powerusers.microsoft.com

@Samshujayanagar 6 месяцев назад

@@RezaDorrani sure, Thank you

@kenkapp1076 Год назад

Reza, thank you so much for this excellent tutorial on the new Power Platform Pipeline feature. I was able to follow it almost perfectly until index time of 9:32. This is where you demo Sarah deploying to the Dev environment. At this point she is prompted to enter a value for the solution's environment variable Banner Text. But in my test solution, I am not being prompted to enter a value for my solution's environment variable. What might be keeping it from prompting me in the same fashion? Thanks in advance.

@RezaDorrani Год назад

Depends on the steps you took prior to exporting solution. Check my video on solution exporting. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Xo-TvZ9N3BM.html

@christophe7519 Год назад

@@RezaDorrani I am a little bit confused by your reply. The point of pipelines is that you should not have to export anymore, you would build in the dev environment then run the pipeline. What am I missing? Updating environment variable values is a pain - what Ken is experiencing - and I am trying to figure out how pipelines can help. Ken, I suspect your environment variable is already set with a value or a default value.

@RezaDorrani Год назад

@@christophe7519 Pipelines is currently a preview feature. MY environment variable is set but I have also ensured I take t step shown in video link provided to ensure when it exports, it allows me to enter its value in subsequent environment.

@christophe7519 Год назад

@@RezaDorrani Got it, you were talking about the dev preparation ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Xo-TvZ9N3BM.html, not the pipeline.

@agnetheblarsen5547 Год назад

Did you find a solution to this? I'm running into the same issue.

@kishorekrishna83 Год назад

Thanks Reza just to know is it possible to put schedule to deploy solution

@RezaDorrani Год назад

Currently scheduling is not supported

@simmyjer 6 месяцев назад

Hi Rezza, Does each environemnt (Dev (Sandbox), Test (Sandbox), Prod (Production) need to be Enabled Managed Environments?

@RezaDorrani 6 месяцев назад

Only target environments need to be managed. So test and prod.

@henryburkhardt4160 Год назад

Hi Reza, great video and introduction to the topic. I just followed your steps and created a pipeline but I intentionally ignored setting the involved environments to manged. I also got the note in the pipeline App that only managed environments are support but ignored it. Even though I was able to deploy a simple App through the pipeline. Am I missing something, has there been an update or is using only managed environments more an advise than an actual limitation?

@RezaDorrani Год назад

powerapps.microsoft.com/en-us/blog/pipelines-in-power-platform-is-generally-available-ga/

@henryburkhardt4160 Год назад

@@RezaDorrani thanks for sharing the news here which is brand new from yesterday. So from what I see "enforcing use of Managed Environments in pipelines will come in the second half of 2023". So it is a good Idea to implement it already so everything keeps running smoothly in the future :)

@RezaDorrani Год назад

@@henryburkhardt4160 It would be the best thing to do.

@dannynlpd6924 Год назад

Hello Reza. Thank you so much for your channel. It is very helpful. I have a issue with delegation in powerapps and wonder if you can give me some of you insights. basically, I want to filter my gallery by my group. First, I get the manager's email and then use that to get the list of emails that direct report to it by using directreportsV2. I store the list to a collection and use it to filter my gallery. I check if the submittedby email is in that list. I get delegation. Can you help me with that? Thank you so much

@RezaDorrani Год назад

I do not have a video reference on this scenario and would have to try it out to provide guidance. I would recommend posting your issue/query with screenshots on the forums at powerusers.microsoft.com

@ujwalnemade6410 Год назад

Thank you for posting this helpful video. I have 2 queries. 1. This pipeline works only for managed Environment as you said but when i tried to deploy the solution in an unmanaged environment it still worked. So I am a little confused here. Can this pipeline be used for unmanaged environments as well ? 2. Do you have a detailed video that explains Managed and Unmanaged Environment in detail specially their license requirements part. Thanks Again.

@RezaDorrani Год назад

1 - Currently there is no hard enforcement for managed environments but will be in effect soon. Im not aware of the timeline though. 2 - I have done a video on solutions. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Xo-TvZ9N3BM.html

@ujwalnemade6410 Год назад

@@RezaDorrani thanks for the reply for 2nd one I was checking for Managed Environment and not Managed solution. Can you please provide the correct URL if you have one. Thanks again.

@RezaDorrani Год назад

I do not have any video references for managed environments. Check Microsoft documentation.

@marcinjarzabek7021 Год назад

Hello Reza, new feature looks good, however there is still case which pipelines don't cover. How would you approach this scenario: You've got one app with multiple flows assigned to it. All these resources are part of solution and reside in development environment as managed. You want to create a copy of this app (solution) and point them on production to 3 separate data sources (lets say each app should be connected to different SharePoint site). All these three 'copies' should be provisioned on production environment. Is there a way to copy/duplicate the solution? Please help

@RezaDorrani Год назад

There are various cases which pipelines currently do not cover. This is V1 of pipelines and a lot more to come. For your scenario, what you need to look into is data source environment variables.