Connect Your Azure DevOps Wiki
Your agent can reference your team's runbooks and procedures during investigations — but only if it can access them. Learn more about ADO Wiki Knowledge and what problem it solves.
What you'll build
By the end of this tutorial, your agent will search your Azure DevOps wiki when answering questions. You'll:
- Connect an ADO wiki using the Documentation connector
- Verify the connection is active
- Ask your agent a question that uses wiki content
Time: ~10 minutes
Prerequisites
Before starting, you need:
- An Azure SRE Agent (already created)
- An Azure DevOps project with a wiki containing content
- One of these authentication options:
- Managed identity — your agent's managed identity added as a user in your ADO organization (Organization Settings → Users → Add users → enter the identity's client ID)
- Personal Access Token (PAT) — generated in Azure DevOps with Code (Read) scope
Step 1: Get your wiki URL
- Go to your Azure DevOps project
- Click Wiki in the left sidebar
- Copy the URL from your browser's address bar
Your URL looks like this:
https://dev.azure.com/{your-org}/{your-project}/_wiki/wikis/{wiki-name}
Legacy URLs are also supported:
https://{your-org}.visualstudio.com/{your-project}/_wiki/wikis/{wiki-name}
To index only a specific section of your wiki, navigate to that page in ADO first, then copy the URL. The page ID in the URL tells your agent to crawl only that page and its subpages — useful for large wikis where only the /Operations or /Runbooks section is relevant.
Step 2: Open the Connectors page
- Go to sre.azure.com
- Select your agent
- In the left sidebar, expand Builder
- Click Connectors
You'll see a list of your existing connectors with their names, service types, and connection status.
Step 3: Start the Add connector wizard
Click Add connector in the toolbar. A 3-step wizard opens:
- Choose a connector — select the connector type
- Set up connector — configure name, URL, and authentication
- Review + add — confirm and create
Step 4: Select Documentation connector
In the connector picker, find and select Documentation connector — it has the subtitle Azure DevOps. Its description reads: "The agent references documentation and files to understand your projects and processes."
Click Next to proceed to the setup form.
Step 5: Configure the connector
The form title shows "Set up Azure DevOps connector". Fill in these fields:
| Field | What to enter |
|---|---|
| Name | A descriptive name (e.g., ops-wiki or team-runbooks) |
| Azure DevOps URL | Your wiki URL from Step 1 |
Choose your authentication method
Select one of the two options:
Option A: Managed Identity (recommended)
- Select Managed Identity (selected by default)
- Choose your managed identity from the Managed identity dropdown (defaults to "System assigned")
- Optionally check Use managed identity as federated identity credential
Option B: Personal Access Token (PAT)
- Select Personal Access Token (PAT)
- Paste your Azure DevOps PAT in the Personal Access Token field
Click Next to proceed to the review step.
Step 6: Review and create
Review your connector details on the summary screen. Click the submit button to create the connector.
Checkpoint: Your new connector appears in the connectors list with status Connected (green checkmark).
Initial indexing may take a few minutes depending on the size of your wiki. Your agent can use the wiki content once indexing completes.
Step 7: Test with a question
- Click New chat thread in the sidebar
- Ask a question that your wiki content can answer
For example:
What are our standard procedures for handling a database failover?
Your agent searches your wiki alongside other knowledge sources and includes citations linking to the original wiki page in its response.
Checkpoint: You should see your agent's response reference content from your wiki. The response includes a citation link back to the source wiki page in Azure DevOps.
What you've learned
- How to connect an Azure DevOps wiki using the Documentation connector
- How to choose between managed identity and PAT authentication
- How URL scoping lets you target specific wiki sections
- How your agent automatically searches wiki content during conversations
Troubleshooting
| Issue | Solution |
|---|---|
| Connector shows "Disconnected" | Verify your wiki URL format and authentication credentials |
| Wiki content not appearing in responses | Wait a few minutes for initial indexing to complete, then try again |
| URL validation error | Ensure URL matches: https://dev.azure.com/{org}/{project}/_wiki/wikis/{wiki-name} or https://dev.azure.com/{org}/{project}/_git/{repo}. Legacy visualstudio.com URLs are also accepted. |
| PAT authentication fails | Check that your PAT has Code (Read) scope and hasn't expired |
| Managed identity fails | Verify the agent's managed identity is added as a user in your ADO organization (Organization Settings → Users) |
Next steps
- Upload additional knowledge: Builder → Knowledge base → Add file
- Connect a GitHub repo: Set up connectors
- Explore knowledge concepts: Memory & Knowledge