Configure with Azure DevOps

After successfully authenticating, you will be redirected into your private Baz workspace. Select Sign in with Microsoft to connect your Azure DevOps account.

Note: If your Azure DevOps admin already integrated your organization, you will be able to select it from the organization navigation menu.

Authorize Baz

You will be redirected to Microsoft's permissions page. Review the requested permissions and click Accept to authorize Baz.

Baz uses this connection to access your Azure DevOps organization, repositories, pull requests, work items, projects, teams, and related review activity.

Create or Select Organization

After authorization, Baz will redirect you back to the onboarding flow.

If this is a new workspace, give your Baz organization a name. If you expect to be part of an existing organization, reach out to your organization admin.

Connect Azure DevOps Repositories

Baz will ask you to connect to your Azure DevOps repositories.

Click Connect to Azure DevOps. You will be redirected to Microsoft to approve the connection if needed, then returned to Baz.

Select Repositories

Baz will show the repositories available from your Azure DevOps organization.

Select the repositories Baz should access and click Continue.

Repository names are shown in this format:

<azure-devops-organization>/<project>/<repository>

Selecting Projects and Repositories

Azure DevOps organizations can span many projects and repositories, and admins do not need to grant Baz access to all of them. Admins can scope an Azure DevOps connection to specific projects and repositories instead of the entire account.

During onboarding, or when reconfiguring the integration later, admins can open the project and repository picker to choose exactly which Azure DevOps projects and repositories Baz should have access to. Selections are organized by project, so an admin can grant Baz access to a handful of repositories in one project while leaving other projects untouched.

Baz keeps webhook coverage aligned with this selection automatically. When a repository is added to the selection, Baz registers the webhooks it needs to detect pull requests and review activity in that repository. When a repository is removed from the selection, Baz cleans up the webhooks it previously registered there. Admins do not need to manage webhooks manually in Azure DevOps.

Only Azure DevOps admins can change the project and repository selection.

Note: If you connected Azure DevOps before project-scoped selection was available, you may need to reconnect the integration from the Integrations Page to grant Baz project-scoped access. Reconnecting lets you choose specific projects and repositories instead of the whole organization.

Code Review Agents

After repository selection, Baz activates the default code review agents for your workspace:

• Code Correctness
• Code Styling
• Security

Click Continue to proceed.

Optional Integrations

You can connect a ticketing system during onboarding to enrich Baz reviews with work item context.

If Azure DevOps is already connected, Baz will show a success state and you can continue to the next step.

Permission Model

Baz uses Microsoft OAuth to connect Azure DevOps.

For Azure DevOps repos, Baz can read repository code, pull requests, commits, changed files, comments, threads, reviewers, projects, teams, and work items.

Baz can also post review comments, replies, statuses, and approvals back to Azure DevOps.

PAT-based onboarding is not currently available in the Baz UI.

Reconfiguring

At any point, you can go back and reconfigure Azure DevOps from the Integrations Page.

Use this page to reconnect Azure DevOps, update repository access, or change which repositories Baz should review.

FAQ