Source Control: Git Integration in Power Platform

Title card for the Git integration in Power Platform guide
Facebook
Twitter
LinkedIn

Source Control: Git Integration in Power Platform

Introduction

Microsoft Power Platform has revolutionized how businesses develop and automate processes. With the introduction of Git integration, managing source control becomes significantly more accessible and efficient. This article explores how to enable and use Git integration within Power Platform, making version control more intuitive for both seasoned developers and newcomers.

Why Git Integration Matters

Traditionally, incorporating Git into Power Platform required external tools like Visual Studio Code and complex configurations. The new native integration simplifies this process, allowing users to link their solutions directly to Azure DevOps repositories. This enhances collaboration, ensures version history, and reduces deployment risks. Azure DevOps was the only supported Git provider when this guide was written — GitHub is being added as a second provider in 2026 release wave 1.

On the left hand side we can see the Source Control Option.

Power Apps maker portal with Source control highlighted in the left navigation of a solution

After clicking that option, we can see that it is asking to connect to Git.

Power Apps Connect this solution to Git screen with the Connect button

Now, before connecting to Git we need to setup branch in the DevOps to connect.

So, lets go to the DevOps and we can initialize the project.

 

Setting Up Git Integration

To begin, navigate to the Power Platform Admin Center.

Once the environment is ready:

  • Visit Azure DevOps and create a new project.
  • Choose Git as the version control method.
  • Initialize a repository with a README file.

Azure DevOps empty repository page with the Initialize option for adding a README highlighted

Lets create a separate branch. I have created dev branch.

Azure DevOps branch selector with the New branch option highlighted

 

Azure DevOps Create a branch dialog creating a dev branch based on main

Now in PowerApps we can see the Organization, Repository, Project and branch as well. So, after selecting the correct values we can click the Connect button.

 

Connecting Power Platform to Azure DevOps

Switch back to Power Platform and choose the new environment. Within the Maker portal:

  1. Go to “Solutions.”
  2. Click “Connect to Git.”
  3. Choose the connection type as Environment.
  4. Select the DevOps organization, project, repository, and branch.
  5. Create additional branches (e.g., Dev, QA) if needed.

Power Apps Connect to Git dialog with the Organization dropdown open showing AQCDev

 

Power Apps Connect to Git dialog completed with organization, project, repository, dev branch and CRM Git folder

 

Now in power apps, we can see the commit option is appearing and we can also see the changes tab here.

Power Apps Source control tab with Check for updates highlighted and nine pending changes

Before commit, we can check the updates if there are any changes made by some other users.

Power Apps Source control tab listing nine changed solution objects on the dev branch

Now, we can commit the changes.

Power Apps Source control tab with the Commit button highlighted

And we can put the comments about the changes.

Power Apps Commit panel with a comment entered and the dev branch selected

We can see the commit is successful.

Power Apps Source control tab showing Update Successful and Commit Successful confirmations

After configuration, a confirmation message ensures the setup is successful. Folders will also appear in Azure DevOps reflecting the changes made in Power Platform.

Azure DevOps Files view showing the CRM solution folders committed from Power Platform

Using Git Features in Power Platform

Once integrated, developers can:

  • Create new solutions.
  • Track changes in a dedicated “Source Control” tab.
  • Commit updates and manage branches directly within Power Platform.

Conflicts (e.g., simultaneous changes) are highlighted, and users can resolve them using intuitive in-platform options like “Accept Incoming Changes.”

Benefits of the Integration

  • Simplicity: No need for separate Git clients or IDEs.
  • Visibility: All changes and history are accessible within both Power Platform and Azure DevOps.
  • Control: Manage environments, branches, and conflicts efficiently.

Conclusion

The Git integration in Power Platform marks a significant step toward empowering developers with modern source control tools. Its seamless setup and robust functionality enable better version management and foster collaborative development.

Whether you’re a solo maker or part of a large team, this integration is a game-changer for Power Platform solution management. Source control is only one part of a governed release process — our Power Platform deployment governance checklist covers the environment strategy, security roles and monitoring that belong around it.