Step 3: Connect source code in Azure SRE Agent

Connect your GitHub or Azure DevOps repository. Your agent can now perform root cause analysis by correlating production problems to specific code.

What you accomplish

By the end of this step, your agent:

• Analyzes source code during investigations
• Provides file:line references for problems
• Creates To-Do Plans that show investigation steps
• Correlates production symptoms to code changes

Prerequisites

Choose your authentication method

Connect your repository

Connect a GitHub repository so your agent can index it as a knowledge source. The dialog shows a browsable list of your repositories. Select from the dropdown instead of typing URLs manually.

Step 1: Open the Add Repository dialog

During onboarding, select the Add repository card in the Knowledge Base step.

For an existing agent, go to Build + setup > Context > Code access, choose the service tab, and select Add repository.

Step 2: Choose a platform

1. Select GitHub or Azure DevOps.

2. On the Connection step, enter the full Repository URL for GitHub, or the Organization name for Azure DevOps.

3. Choose an existing connection if one is available, or configure a new connection.

4. Select the authentication method and complete its fields. GitHub offers OAuth, Personal access token (PAT), and Use your GitHub App. Azure DevOps offers Your account, Managed Identity, and PAT.

5. Complete the sign-in or connection test shown by the selected method. For method-specific instructions, see Connect a source code service.

   Note

   If the sign-in dialog doesn't appear, check that your browser isn't blocking popups from sre.azure.com.

6. Confirm the connection succeeds.

7. Select Next.

Step 3: Select repositories

On Add repositories, review the initial repository and add more entries as needed. The Repository URL field supports repository selection and direct URL entry:

• GitHub repos appear as org/repo-name, sorted alphabetically (up to 100 repos).

• Azure DevOps repos appear after you select a project from the Azure DevOps Project dropdown, sorted alphabetically.

Select a repository from the dropdown. The Display name autocompletes with the repository name. You can also type any valid repository URL directly into the field.

For GitHub, select Add repository to add entries. Expand each entry to edit its Display name or use Add description. For Azure DevOps, use Add and edit those fields in the grid.

Step 4: Confirm and save

Select Save. The repositories appear on the Code access page with their connection and last-sync information.

Step 5: Try creating a pull request (preview)

With your repository connected, your agent can now create pull requests directly from chat.

1. Open a chat thread with your agent.
2. Type a prompt like: "Create a PR in https://github.com/OWNER/REPO from fix/my-branch to main titled 'Fix connection timeout'".
3. In Review mode, select Continue to approve the PR creation.

Your agent returns a tool card with a clickable link to the created PR.

Manage connected repositories

The Code access page lists connected repositories and their connection names.

To remove a repository:

Use the following steps to remove a connected repository.

1. Go to Build + setup > Context > Code access.
2. Select the service tab and the repository's checkbox.
3. Select Delete and review the confirmation before proceeding.

To update authentication: If your PAT expires or you need to switch accounts, reopen the Add Repository dialog and re-authenticate with new credentials.

Alternative: MCP + custom agent

To get full GitHub API access (search code, read files, and list commits across all repositories), connect GitHub as an MCP server with a dedicated custom agent.

This approach uses the Model Context Protocol (MCP) to connect GitHub tools to a custom agent. Follow the step-by-step tutorial, Set Up MCP Connector.

Your agent now analyzes source code during investigations, provides file and line references for problems, creates To-do Plans showing investigation steps, correlates production symptoms to code changes, and can create pull requests in connected repos directly from chat.

What you learned

• Your agent now analyzes source code during investigations.
• It provides file and line references for problems.
• It creates To-Do Plans that show investigation steps.
• It correlates production symptoms to code changes.

Related content