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

[@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. 6 - All Target environments must be Managed.

[@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

[@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.

[@vedmishra5967]

This is it folks, much appreciated Reza

[@RezaDorrani]

Most welcome

[@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]

Can solutions be exported to another tenants?

[@AmmarRamadan]

@@danielmilloc2289 yes

[@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.

[@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]

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

[@RezaDorrani]

Thanks so much Diego

[@satyenkasturi]

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

[@RezaDorrani]

Glad to hear!

[@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.

[@SHAli1474]

Another brilliant feature explained brilliantly. Thanks Reza

[@RezaDorrani]

You are most welcome! Thanks so much for watching.

[@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]

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.

[@swapnilwani7084]

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

[@RezaDorrani]

Thanks for watching

[@oluwatobipaul6171]

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

[@RezaDorrani]

Glad it was helpful!

[@andersgustavsson213]

Thanks, great video. I have a question: I already have 4 environments, Dev, QA, UAT and Production. Only the production environment is a production environment. Your example has all environments as production environments. Does this mean that I need to convert my existing sandbox environments to production?

[@RezaDorrani]

You don’t need to do that. Pipelines works with most if not all environment types

[@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

[@andyhurd5796]

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]

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

[@andyhurd5796]

@@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!)

[@ppl111]

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

[@RezaDorrani]

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

[@s961201]

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

[@RezaDorrani]

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

[@SaddamKhan-mv3iw]

Thanks Reza, Always love watching your video.

[@RezaDorrani]

Glad to hear that

[@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.

[@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.

[@satyenkasturi]

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

[@RezaDorrani]

👍

[@arydias85]

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]

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.

[@allenzhang7407]

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]

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]

@@RezaDorrani thank you so much Reza!

[@SmartLearningAI]

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]

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

[@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.

[@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.

[@Gu13091989]

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

[@RezaDorrani]

My pleasure!

[@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

[@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.

[@MouniB-d2c]

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]

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

[@MouniB-d2c]

@@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]

@@MouniB-d2c Documentation has it all. Simply search on web for pipelines for power platform 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.

[@senthilkumarchandran3680]

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]

You can only deploy higher versions.

[@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.

[@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 kzbin.info/www/bejne/jqCQhamQbrNmeK8 They will show up when running the pipeline

[@eugenevanbetonio7314]

@@RezaDorrani Cool. Thank you!

[@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.

[@SauloOliveira]

Thank you for sharing Reza.

[@RezaDorrani]

You are most welcome

[@conraddugger4165]

Absolutely amazing, THANK YOU

[@RezaDorrani]

You're very welcome!

[@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/

[@venumadhavravulapalli1463]

Awesome update Reza... Highly useful. Thank you

[@RezaDorrani]

Most welcome

[@simmyjer]

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

[@RezaDorrani]

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

[@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.

[@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.

[@galleon8129]

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

[@RezaDorrani]

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.

[@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

[@srinivasacharyvishwanadula787]

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

[@RezaDorrani]

Yes

[@Radekk225]

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]

Check documentation on delegated departments via pipelines.

[@ketanpimple1933]

Amazing 👏 thanks Reza for sharing this.

[@RezaDorrani]

Most welcome

[@alexagarcia3085]

Hi Reza! Amazing video and very detailed. I have two questions: 1. Is it necessary to have a separate environment to host the pipelines, or can I use the production environment to host them? If not, could you please explain why? 2. What is the difference between the sandbox environment type and the production environment type? My test and development environments are sandbox types, but yours are production types. Thank you in advance :)

[@RezaDorrani]

1 - Its not necessary but I would keep it separate (admin and governance) 2 - check documentation on environment types (it explains what they are best suited for and their differences. Pipelines works with both sandbox and production env types.

[@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.

[@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.

[@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.

[@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

[@nickthoman2280]

If the deployment to test is a managed solution, then how do you change environment variables? For instance... have an environment variable for a SharePoint list that points to a DEV list, TEST list and Prod list.

[@RezaDorrani]

When you import, it will ask you to add info for env variables. managed solution does not mean components cannot be edited. You cannot change them within solution context but they can be updated in context of environment. There is a default solution for env where all these components would also live in which can be updated.

[@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.

[@kishorekrishna83]

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

[@RezaDorrani]

Currently scheduling is not supported

[@mehrdadameli2430]

Hi Reza, thanks a lot for this video! I have a question about the host environment: Does the host environment type need to match the test or dev environment? For example, if the dev environment is set to 'sandbox,' should the host also be a 'sandbox'?

[@RezaDorrani]

Host env needs to be of type Prod.

[@mehrdadameli2430]

Tank you so much Reza for your answare. I have another question . Can I install the pipeline app in prod env. to import a solution from dev to test . And install in dev to import solution from test to prod?

[@RezaDorrani]

Check documentation on requirements and best practices for pipeline host. Ideally it should be it's own prod env.

[@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

[@MrGaztab]

Great video. Thanks again Reza.

[@RezaDorrani]

Most welcome

[@shrutidwivedi2142]

Hi Reza, Thank you for Great Video.

[@RezaDorrani]

Most welcome

[@RajeshSharma-fe9dy]

I watched the video and proceeded without using Managed Environments and it still worked successfully. Could you clarify why you recommended using Managed Environments?

[@RezaDorrani]

As per documentation, target environments for pipelines must be managed

[@RajeshSharma-fe9dy]

​@@RezaDorranithanks for the reply, would you see any issues if we still proceed without managed solutions. All we are using it for is promoting it PROD. Appreciate your time.

[@RezaDorrani]

@@RajeshSharma-fe9dy I would follow what the documentation says.

[@benjaminlahsen6721]

Hi Reza. How are the conections automatically set in Prod if I am targeting a Prod database for example that is diferent from the dev database?

[@RezaDorrani]

When you deploy via pipelines, the first thing it sets is connections. Check documentation

[@sergioivan6631]

Will this create in the background a series of CI/CD pipelines in Azure DevOps???

[@RezaDorrani]

No, but pipelines now has extensibility features which allows you to trigger flows. You can take the solution and store it in ADO repo and more. Check documentation on pipelines.

[@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.

[@danielmilloc2289]

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

[@RezaDorrani]

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

[@clairevoyance26]

Do you need to export the solution from dev to test environment before using the deployment pipeline?

[@RezaDorrani]

Deploying from dev to test is also using the pipeline

[@KrishnaRachakonda]

Very detailed demo Reza. Thank you.

[@RezaDorrani]

Most welcome

[@mehulchawhan6900]

how about the configuration deployment? this solution deployment can be done more easily with just import and export functionality, if this pipeline even does configuration deployment then it would be more helpful, kindly advise

[@RezaDorrani]

Pipelines has added extensibility capabilities. Recommend checking documentation - learn.microsoft.com/en-us/power-platform/alm/pipelines

[@clairevoyance26]

Hi Reza, when deploying from source environment -> target environment. Is it a best practice to have a separate connection (ex. Sharepoint connection) for each application? Or is it safe to share 1 sharepoint connection with multiple applications?

[@RezaDorrani]

Each environment will have a separate connection. I'm assuming you mean connection reference fot data source. That is completely up yo you.

[@clairevoyance26]

@@RezaDorrani ah yes, the connection reference. Is there a best practice on that? what is your preference?

[@RezaDorrani]

@clairevoyance26 Ideally one should have different lists for dev, test and prod

[@clairevoyance26]

@@RezaDorrani ahh right2. How about connection references for applications? Do you usually go for sharing 1 sharepoint connection to multiple applications or 1 sharepoint connection per application? Sorry for the questions. I have been using 1 connection per application and i was wondering if it were better to share 1 application to multiple apps

[@RezaDorrani]

@clairevoyance26 there is no right or wrong way. I use the same connection.

[@dc7798]

Hi Reza, I'm currently working on implementing email actions in our Power Platform pipelines, and I have a question regarding email recipients. During development and testing phases, I'd like to configure the email action to send notifications to my email address for testing purposes. However, once the solution is deployed to the production environment, I want the email action to send notifications to the appropriate recipients intended for production. Is there a way to dynamically configure the email recipients based on the environment (e.g., dev/test vs. prod) in Power Platform pipelines? Or do we need to manually adjust the email recipients each time we deploy the solution to different environments? Any insights or best practices on how to handle this scenario would be greatly appreciated. Thank you!

[@RezaDorrani]

Environment variables is the answer

[@EWPiano]

Exactly what I needed. Thank you!

[@RaviKrishnaSrivastava]

In this video, you have created the pipleline for a model driven app. Is this pipeline approch work for canvas app also?

[@RezaDorrani]

It will work for any component that can be added to a solution

[@RaviKrishnaSrivastava]

@@RezaDorrani Thank you Reza.

[@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.

[@udp77fac1]

Hi Reza! Do you know if I can use pipelines if my databases are in Oracle?

[@RezaDorrani]

I have done no work with Oracle, hence not sure

[@Linex1986]

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]

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

[@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.

[@manjunath5727]

Thanks for the clear explanation

[@RezaDorrani]

Most welcome

[@onyebuchiboss]

Hi @reza, so this can't be used across different tenants?

[@RezaDorrani]

Currently, you cannot use pipelines to deploy across tenants.

[@SmartLearningAI]

I tried it with your example and it worked fine, however trying it with another of my own solutions it failed. When I ran the pipeline from . Dev>Tes>Prod with the same toolset as per your video, I get an error: Missing dependencies....You will need to import the following items to this environment...Surely, the point of the pipeline is to transfer the entire solution (which works fine) from Dev to Test to Production? Advice? Update: I found the issue, just had to manually add required objects and republish and re-run pipeline. (My solution was using a global lookup list which had to be 'included' in the Dev solution for the pipeline to run and publish it to the 'Test' Environment and from there to the 'Prod' environment. Works fine now, but it would be nice if the system could warn of dependent objects and offer to auto pull them in.

[@RezaDorrani]

Dependencies clearly means your solution is dependent upon certain components being installed in the target environment being missing. Advice would be to do what you did related to adding the required objects. Pipelines automates process of deployment not handling dependencies (at least not currently)

[@TraderZo1]

Is there anything like this that can be used for database for teams?

[@RezaDorrani]

Pipelines is not supported for DV4T environments. Not sure if there is any options for Teams environments as basically each team can only have 1 environment.

[@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. kzbin.info/www/bejne/jqCQhamQbrNmeK8

[@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.

[@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.

[@emilioroqueta4445]

Hi Reza, Pipelines are available in PowerApps for Teams? Thanks in advance.

[@RezaDorrani]

Not for teams

[@jesuschrist6811]

why did you grant "deployment pipeline user" at 8:08 and share the pipeline at 8:18 ? what is the difference? why both?

[@RezaDorrani]

Deployment pipeline user role is to run pipelines. Sharing is for them to be able to run that specific pipeline. Check documentation for details.

[@JohnAckery]

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]

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]

@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]

@@JohnAckery Pipelines currently does not support cross-tenants

[@dhananjaykharade2711]

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

[@RezaDorrani]

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]

@@RezaDorrani Thanks a lot for the response.

[@maamirkhan2005]

as always, great, great, great work!

[@RezaDorrani]

Thank you! Cheers!

[@ItsMeProday83]

Thanks Reza, great video!

[@RezaDorrani]

Most welcome

[@junedshaikh9074]

I have UAT and DEV environments, I want to move solutions from UAT (un-managed solution) to Dev (also to un-unmanaged solution) because we usually do some immediate changes in Dev also. I tried this, it is only importing as managed solution in Dev environments.

[@RezaDorrani]

Currently pipelines only supports managed solution deployments

[@Abdulkhaleq-cb5sb]

Fantastic Work

[@RezaDorrani]

Thanks

[@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

[@SmartLearningAI]

For learning purposes of pipelines is it possible to use 3 free Development Environments instead for Dev, Test, Prod)?

[@RezaDorrani]

I believe so but have not tried it so not 100% sure

[@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.

[@benjaminlahsen6721]

Hello Reza. What if I would like the solution to be unmanaged, so that I can still make changes in production, I would have to leave the Enable Management Eniorement off right? But also I would have to mannually apply the changes to the dev enviorment right?

[@RezaDorrani]

Pipelines only supports managed solution exports as of now

[@benjaminlahsen6721]

@@RezaDorrani I see. Also with regards to the connections, I could find whe can I map 'em, because as I told you before I am targeting a dev SQL Database in the dev enviorement and a Prod SQL Datavase in the production enviroment. I can't see where in the pipeline deplyment window I can manage that

[@RezaDorrani]

Cannot as of now.

[@benjaminlahsen6721]

@@RezaDorrani but I mean, what happends in that case where I want to target a prod database because is logical that that db is different from the dev one, right?

[@RezaDorrani]

@benjaminlahsen6721 you will need to go to app in test or prod and update connection

[@legendgod]

Could we apply approval/reject logic in the pipleline?

[@RezaDorrani]

Currently, it is not an option

[@imranbasha4113]

Hi Reza, It’s a great walkthrough, I have configured by following your tutorial at 9:33 the Deploy option doesn’t shows me to enter destination environment variables different site and list. Yes, I do have environment variables created for site and list . Is it bug or glitch? If any points to be keep in mind what should those please let me know. Thanks in advance

[@RezaDorrani]

I have done 2 other videos on environment variables and solutions. Check those. You have to do some setup for env variables prior to export.

[@imranbasha4113]

@@RezaDorrani Thanks for your quick reply, I have removed environment variables current values in solution and saved. Then i try to deploy using pipeline at that time it's asking me to provide environment variable values correctly.

[@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

[@anantv10]

Hey Raza, Can we add any approver before clicking the production

[@RezaDorrani]

Approver based clicking? I assume you mean approvals. Check documentation on pipelines. We have extensibility options now.

[@MohammadsadeghSalehi-l5x]

Hi Reza, Thanks for this video. I have an app which is using some connections that I'm not own some of them, but the owner has shared them with me so I can use the connections but when I want to deploy my solution to test env it's asking me to update the connections! how can I handle this? and is there any wat that we can use our own connection in new env (managed env)?

[@RezaDorrani]

That would require a post deployment step to swap the connections (via an admin account)

[@MohammadsadeghSalehi-l5x]

@@RezaDorrani is there any reference or document for this?

[@RezaDorrani]

@@MohammadsadeghSalehi-l5x I am not aware of one

[@satyenkasturi]

Hello Reza.........when I redo the same for second version from Dev to Test....does the Solution updates itself in test env or recreates the whole thing again?

[@RezaDorrani]

Upgrades