--- title: Collaborating on Power Apps Using Personal Environments, Power Platform CLI, Git, and Azure DevOps description: Learn how to collaborate on Power Apps using personal environments like Power Platform CLI, Git, and Azure DevOps. image: https://blog.metrostar.com/hubfs/MicrosoftTeams-image%20(82).png --- [![MetroStar Systems Logo](https://blog.metrostar.com/hs-fs/hubfs/raw_assets/public/MetroStar_Jan2021/images/Logo-2021.png?width=413&name=Logo-2021.png "MetroStar Systems Logo")](https://www.metrostar.com/) - Who We Are - [Meet MetroStar](https://metrostar.com/who-we-are/) - [Leadership](https://metrostar.com/leaders/) - [Partnerships](https://www.metrostar.com/partnerships/) - [Innovation Lab](https://www.metrostar.com/innovation-lab/) - [Contract Vehicles](https://www.metrostar.com/contract-vehicles/) - What We Do - [Artificial Intelligence](https://www.metrostar.com/ai-and-government/) - [Digital Experience](https://www.metrostar.com/digital-experience/) - [Application Modernization](https://www.metrostar.com/application-modernization/) - [Enterprise IT](https://www.metrostar.com/enterprise-it-services/) - [Products + Solutions](https://www.metrostar.com/federal-government-products-solutions/) - Who We Serve - [National Security](https://www.metrostar.com/national-security/) - [Defense](https://www.metrostar.com/defense-customers/) - Insights - [Blog](https://blog.metrostar.com/) - [Case Studies](https://www.metrostar.com/case-studies/) - [News + Events](https://metrostar.com/news-events/) - Join Us - [Careers](https://www.metrostar.com/join-us/) - [Open Roles](https://www.metrostar.com/jobs/) - [Cleared Jobs](https://www.metrostar.com/cleared-jobs/) - [Veterans](https://www.metrostar.com/veterans/) - [Internships](https://www.metrostar.com/internships/) - [Contact Us](https://metrostar.com/contact-us/) - Who We Are - [Meet MetroStar](https://metrostar.com/who-we-are/) - [Leadership](https://metrostar.com/leaders/) - [Culture](https://metrostar.com/culture/) - [Partnerships](https://www.metrostar.com/partnerships/) - [Innovation Lab](https://www.metrostar.com/innovation-lab/) - [Contract Vehicles](https://www.metrostar.com/contract-vehicles/) - What We Do - [Artificial Intelligence](https://www.metrostar.com/ai-and-government/) - [Digital Experience](https://www.metrostar.com/digital-experience/) - [Application Modernization](https://www.metrostar.com/application-modernization/) - [Enterprise IT](https://www.metrostar.com/enterprise-it-services/) - [Products + Solutions](https://www.metrostar.com/federal-government-products-solutions/) - Who We Serve - [National Security](https://www.metrostar.com/national-security/) - [Defense](https://www.metrostar.com/defense-customers/) - Insights - [Blog](https://blog.metrostar.com/) - [Case Studies](https://www.metrostar.com/case-studies/) - [News + Events](https://metrostar.com/news-events/) - Join Us - [Careers](https://www.metrostar.com/join-us/) - [Open Roles](https://www.metrostar.com/jobs/) - [Cleared Jobs](https://www.metrostar.com/cleared-jobs/) - [Veterans](https://www.metrostar.com/veterans/) - [Internships](https://www.metrostar.com/internships/) - [**Contact Us**](https://metrostar.com/contact-us/) [blogs](https://blog.metrostar.com/) > [Enterprise IT](https://blog.metrostar.com/tag/enterprise-it) # Collaborating on Power Apps Using Personal Environments, Power Platform CLI, Git, and Azure DevOps 4 MIN READ 09/29/2021 | [Enterprise IT](https://blog.metrostar.com/tag/enterprise-it) ![Graphic with text that reads ](https://blog.metrostar.com/hubfs/MicrosoftTeams-image%20(82).png) One of the challenges of working on Power Apps with multiple developers is that you can accidentally overwrite each other's work. This is a common challenge whenever you develop in a "shared" development environment. You can communicate and coordinate at all times to avoid losing progress but that's not an ideal solution. Luckily for professional developers, there are some tools you can use to collaborate in a more effective way. ## Using Personal Environments Each developer can create their own personal environment instead of using a shared environment where everyone develops in parallel.  You can use the built-in [copy environment](https://docs.microsoft.com/en-us/power-platform/admin/copy-environment) feature if your personal environment is within the same tenant. If your personal environment is on a separate tenant, then you can export the desired solutions manually or use the Power Platform CLI and then import those solutions into your personal environments. These customizations are applied to the target environment when you're exporting and importing solutions, but no data is imported, unlike when you use the copy feature. ## Using Git, Power Apps CLI, and SolutionPackager to Move Customizations Between Environments Once every developer has their own environment, you can establish a process for moving changes from the shared environment back into the personal environment and changes from the personal environment back to the shared environment. Shown below is a visualized example of this process. This diagram was developed during our internship program by [Brendan Moore. ](https://www.linkedin.com/in/brendanrmoore/) ![Visual process of building customizations between environments](https://lh5.googleusercontent.com/TPsy90Fz1C_i3sUb7hmj1jlOXiEorExt59sLcSvvt1zqQ7jrt6WTl6bP2JroYw4jrib-hTlvnXhcBBf01cMbUpdQPIDKkgG-unmUBCGcGy1-uiOxYbCtBoLFJlVLcQZLqS3bpsja=s0) The following components are in the above process: - *A remote git repository.* In this project, it was an Azure Repository but it could be any git remote. This remote repository holds all of the customizations merged together by different developers. - *A local git repository.* The developers use this to track their local changes and merge them with changes made in the remote repository. - *A personal Power Apps environment.* This allows developers to implement their features before pushing them to the shared environment.  - *A shared Power Apps environment (staging)*. This holds all of the merged customizations from the remote git repository. As a developer wanting to start work on a new feature, you will need to follow the following steps on the diagram: 1. Pull the latest changes from the remote git repository to your local repository using git. These changes are stored in unpacked solution files. 2. Pack the solution files into solutions using the [SolutionPackager tool](https://docs.microsoft.com/en-us/power-platform/alm/solution-packager-tool) and use the [Power Platform CLI](https://docs.microsoft.com/en-us/powerapps/developer/data-platform/powerapps-cli#solution) to import the solutions. 3. Once you have implemented your feature in your personal environment, you should export the solutions using [Power Platform CLI](https://docs.microsoft.com/en-us/powerapps/developer/data-platform/powerapps-cli#solution) and unpack the solutions using the [SolutionPackager tool](https://docs.microsoft.com/en-us/power-platform/alm/solution-packager-tool). 4. Review the local changes and commit them to the local git repository when ready. Pull the latest version from the remote git repository and merge any conflicts if necessary. Push the merged changes back to the remote git repository. 5. You can deploy them to the shared development environment once the changes have been merged and pushed to the remote git repository. In this project, the deployment was automated using Azure Pipelines. Depending on your needs, you may want to introduce multiple branches and pull requests into your process. During our internship project, Brendan made this process more approachable for developers with different levels of experience by wrapping each of these steps in PowerShell scripts which guides developers through. Read these additional resources if you're interested in learning more:  - [How to Deploy Solutions Using Azure Pipelines and Power Platform Build Tools](https://swimburger.net/blog/dynamics/how-to-deploy-power-apps-solutions-using-azure-pipelines) - [How to Deploy Portals Using Azure Pipelines and Power Platform CLI](https://swimburger.net/blog/dynamics/how-to-deploy-power-apps-portals-using-azure-pipelines).  ## Summary It can be hard to collaborate on Power Apps with other developers. Sometimes you can overwrite each other's work or break things; however, each developer can safely make their changes by using personal environments instead of a shared development environment. They can then merge their work together into the shared environment. A developer can track changes to solutions using git and move solutions between environments using the Power Platform CLI and SolutionPackager tool. The Power Platform team has been developing more tools, features, and documentation for professional developers to get the most out of the Power Platform. Read this documentation on [Application Lifecycle Management (ALM)](https://docs.microsoft.com/en-us/power-platform/alm/) to dive deeper and author your own processes for developing Power Apps.  ## About the Author  Niels is a Sr. .NET Developer at MetroStar and a technical content creator. Get in touch with [Niels on Twitter @RealSwimburger](https://twitter.com/RealSwimburger) and follow [Niels’ blog](https://swimburger.net/) on .NET, Azure, and web development.  ![Picture of Niels Swimberghe](https://blog.metrostar.com/hs-fs/hubfs/MetroStar-Logo-2021-sun@3x-2.png?width=150&name=MetroStar-Logo-2021-sun@3x-2.png) Written By: [Niels Swimberghe](https://blog.metrostar.com/author/niels-swimberghe) Former MetroStar Senior .NET Developer ### you might like these too ### [Modernizing Legacy Java Applications in Kubernetes Environments](https://blog.metrostar.com/modernizing-legacy-java-applications-in-kubernetes-environments) ##### Enterprise IT | Feature ### [Enhancing Government Operations: Power BI and Data-Driven Decision Making](https://blog.metrostar.com/microsoft-power-platform-power-bi) ##### Enterprise IT | DevSecOps | AI/ML ### [Five 2024 GovCon Tech Trends: Perspectives from Six Industry Experts](https://blog.metrostar.com/five-govcon-tech-trends-from-six-industry-experts) ##### Enterprise IT | Feature | Cyber | AI/ML | Human-Centered Design [view more](https://blog.metrostar.com/tag/enterprise-it) ## want to stay in the loop? Never miss a thing by signing up for our newsletter. We periodically send out important news, blogs, and other announcements. Don’t worry, we promise not to spam you. [![MetroStar Systems Logo](https://blog.metrostar.com/hs-fs/hubfs/raw_assets/public/MetroStar_Jan2021/images/MetroStar-Footer-Logo.png?name=MetroStar-Footer-Logo.png "MetroStar Systems Logo")](https://www.metrostar.com/) - [Services](https://www.metrostar.com/#digital-services) - [About Us](https://www.metrostar.com/company/) - [Jobs](https://www.metrostar.com/jobs/) - [Contract Vehicles](https://www.metrostar.com/contract-vehicles/) Creating dynamic digital solutions is kind of our thing - we've been transforming and accelerating government missions since 1999. [say hello](https://www.metrostar.com/contact-us/) [![MetroStar Systems Logo](https://blog.metrostar.com/hs-fs/hubfs/raw_assets/public/MetroStar_Jan2021/images/MetroStar-Footer-Logo.png?name=MetroStar-Footer-Logo.png "MetroStar Systems Logo")](https://www.metrostar.com/) [employee login](https://stargate.metrostarsystems.com/) © 2026 MetroStar Systems, LLC - All Rights Reserved | [Privacy Policy](https://www.metrostar.com/privacy-policy/) Go to Top