Nota
L-aċċess għal din il-paġna jeħtieġ l-awtorizzazzjoni. Tista’ tipprova tidħol jew tibdel id-direttorji.
L-aċċess għal din il-paġna jeħtieġ l-awtorizzazzjoni. Tista’ tipprova tibdel id-direttorji.
To connect a Microsoft Dataverse environment or solution to Microsoft Azure DevOps, create or use an Azure DevOps project and repository, and then connect from the source control experience in your solution.
You can access solutions from Power Apps, Power Automate, Power Pages, and Copilot Studio.
Prerequisites
Dataverse Git integration is a feature of managed environments. Development and target environments must be enabled as managed environments.
An Azure DevOps subscription and licenses for users who interact with source control are required when connecting your Dataverse environment to Git.
Note
A limited number of licenses are available in Azure DevOps in the Basic Plan of the service. Go to Azure DevOps Services for more information on pricing and licensing for Azure DevOps.
Azure DevOps Services permission for making commits and reading source files is required. Members of the Contributors security group have permission.
You need a Dataverse environment where you have the System Administrator security role.
A custom unmanaged solution that you want to connect to source control. Create one if you don't have one yet.
Azure DevOps setup
To get started, you need an Azure DevOps project and repository to connect your Dataverse environment. If you don't have an Azure DevOps project and repository set up, follow these steps to create a new project and repository in Azure DevOps.
- Sign in to Azure DevOps and select your organization.
- Select New project, enter a name, make sure version control is set to Git, and then select Create.
- In the new project, select Repos, and then select Initialize at the bottom of the page to initialize the default repository.
Ensure that all users who make changes in your environment have access to your repository and can commit changes. Review your Azure DevOps licensing configuration and security groups to ensure they can use the solution source control panel.
Connect to Azure DevOps from a solution
When you connect to Git, you bind solutions in your environment to a specific location and branch within the Azure DevOps repository. You can bind your environment to a project by using either environment or solution binding. To learn more about the differences between environment and solution binding, see How to choose between environment and solution binding.
Enable all development and target environments as managed environments within the Power Platform admin center.
Sign in to Power Apps (or Copilot Studio, Power Automate, Power Pages) and then go to Solutions.
On the Solutions page, or the Source control page within a custom unmanaged solution, select Connect to Git.
Select either Environment or Solution from the connection type options, and select your Azure DevOps organization and project. More information: How to choose between environment and solution binding
Depending on your binding type, select a project, repository, or branch, and enter a folder to bind the environment or solution to.
Optionally, create a new branch.
Select Connect.
Note
By design, you can't connect the Default Solution and Common Data Service Default Solution to Git. Use a custom solution for app and solution development.
For information about connecting to Git by using code, see Connect and disconnect Dataverse from a Git repository by using code.