Azure DevOps
Connects workspaces to Git repositories in an Azure DevOps organization. Azure DevOps Server (on-premises) is not yet supported.
Infracodebase connects as its own identity, not as a person. Nothing expires, and no one's departure breaks the connection.
Get set up in four steps
1. Connect with Microsoft
In Infracodebase, go to Settings → Version control → Azure DevOps. Enter your organization name, optionally a project name, and click Connect with Microsoft. Sign in and approve.
You need a Global, Application, or Cloud Application Administrator in Microsoft Entra for this.
2. Add Infracodebase to your organization
In Azure DevOps, go to Organization settings → Users → Add users. Paste the application ID the connection shows you, set the access level to Basic, and click Add.
You need to be an Azure DevOps administrator for this, which is often a different person. Entra roles don't carry over.
3. Grant its permissions
Back in Infracodebase, the connection lists any permission it's still missing. Copy the command it shows you, run it as a Project Collection Administrator, then click Check setup.
Repository permissions come with Basic access. Service hook permissions don't, and Azure DevOps has no settings page for them — that's what the command is for. Without them everything else works, but pull requests are never checked.
4. Require the check
Compliance posts to pull requests as soon as step 3 is done, but it doesn't block anything until you say so.
In Azure DevOps: Project settings → Repositories → Policies → your default branch → Status checks, add infracodebase/compliance, set it to Required.
Policies apply to the branch a pull request targets, and only to pull requests created or updated after you add one.
Pinning a project
Leave Project blank to browse every project in the organization. Set it to narrow the connection to one.
It's a filter, nothing more. Creating a repository works either way — if the connection isn't pinned, you pick the project when you create.
Permissions are granted per project, so an unpinned connection can work in one project and not another. The connection lists any project that's short.
What you get
- Repository access to list, connect, and create repositories
- Two-way sync between the workspace and Azure DevOps
- Pull request support to create, comment on, and merge pull requests
- Compliance checks posted back to pull requests as commit statuses
Cost
Azure DevOps licenses Infracodebase like a user, so it takes one Basic seat per organization. Five Basic users are free.