This feature is available to customers on specific editions. Visit Matillion pricing to learn more about each edition.
- To install the Matillion Azure application in your tenant, you’ll need to log in with a work/business or school account. For more information about how the Matillion Azure app works, read Apps with users in other tenants or other consumer accounts.
- You may need to confirm with your Azure tenant admins that you can install the Matillion Azure app and create a repository.
1 - Install the Matillion app in your Azure tenant
You need to install the Matillion app in the Azure tenant that will host the repository to be connected to your project. To do this, follow the steps at Installing the Matillion app in Azure DevOps. To confirm that the Matillion app has been installed in your tenant, visit the Enterprise Applications blade in the Azure Portal, and search for an application namedMatillion for Azure DevOps.
2 - Create a new Azure DevOps repository
In the Azure DevOps organization you wish to use within , create a new repository in your chosen project. Initialize the repository by adding a README file. This will automatically setmain as the default branch.
A branch called
main is required, but it does not have to be the default branch.Want to use an existing repo?
If you already have an existing Azure DevOps repository, you can connect that repository to your project, too. Once you complete the authorization between Azure and Matillion, you’ll see your existing repositories in the Project repository drop-down menu. If you choose an existing repository, all existing branches will be visible in your branch list in the Branches tab.3 - Set up Azure DevOps project/repository roles
There are many ways to control access of users to specific Azure DevOps projects and repositories. This topic is not a primer on Azure access controls; however, you can read more about Azure Permissions and Access in the Microsoft documentation. For a user to be able to select an Azure DevOps repository when choosing the destination in , they will need to be a member of theContributor security group and be granted Basic access at minimum. Or, if custom security groups are used, then the user will need Read + Write permissions on the DevOps repository, project, or organization.

