Connecting Azure DevOps Wiki to Knowledge Management
The Azure DevOps Wiki knowledge integration syncs wiki pages from your Azure DevOps projects into the Rezolve.ai Knowledge Base. It covers both project wikis and code wikis published from a repository. The Virtual Agent can then use the content to answer questions and link back to the wiki page.
This page covers the Azure Wiki-specific setup. For the wizard, sync status, bounced files, and other functions that all integrations share, see Knowledge Integrations.
Prerequisites
- Azure DevOps Services (cloud). Azure DevOps Server (on-premises) is not supported.
- An Azure DevOps organization connected to Microsoft Entra ID.
- An Entra ID administrator who can register an application.
- An Azure DevOps organization administrator (Project Collection Administrator) who can add users.
- Knowledge Management admin access in the Rezolve.ai console.
Personal access tokens (PATs) are not supported. The integration signs in as an Entra ID application (service principal).
Step 1: Register an Entra ID application
- In the Azure portal, open App registrations and click + New registration.
- Enter a name, for example
Rezolve.ai Wiki Ingestion, and click Register. - Copy the Directory (tenant) ID and the Application (client) ID.
- Open Certificates & secrets → + New client secret. Create a secret and copy its Value right away.
No Microsoft Graph API permissions are needed.
Step 2: Add the application to your Azure DevOps organization
- In Azure DevOps, go to Organization settings → Users → Add users.
- Search for the application by name and add it. Use the Basic access level.
- Add it to each project you want to sync, with at least Readers permissions. It needs read access to the project, its wikis, and the Git repositories that store the wikis.
Step 3: Create the Azure Wiki integration
- In the Rezolve.ai console, go to Knowledge Management → Knowledge Integrations.
- Click Add Integrations and select Azure Wiki.
3a. Connection setup
Enter a Title for the integration. Then either choose an existing Azure Wiki connection or select Create New Connection and enter these details:
| Field | Description | Example |
|---|---|---|
| Name | A descriptive name for the connection | Contoso DevOps Wiki |
| Organisation URL | Your Azure DevOps organization URL | https://dev.azure.com/contoso |
| Azure Tenant Id | Directory (tenant) ID from Step 1 | 72f988bf-... |
| Client Id | Application (client) ID from Step 1 | bf7f3a64-... |
| Client Secret | Client secret value from Step 1 |
Use the https://dev.azure.com/<organization> form of the URL. With the legacy https://<organization>.visualstudio.com form, images and attachments in wiki pages may fail to load.
3b. Content selection
Content is organized into one or more content sets. In each content set:
- Tick one or more projects. Every wiki in a selected project is synced, including all of its pages. You can't select individual wikis or pages.
- To limit who can get answers from this content set, open the ⋮ menu, turn on Restrict Access, and choose Restrict by Audience.
3c. Configuration
Under Sync Details, set the Frequency (daily, weekly, or monthly), Start Time, Timezone, and Schedule Start Date. Optionally turn on Subscribe to Sync Reports and add User Subscribers. Then click Save.
What gets ingested
| Content | Details |
|---|---|
| Wiki pages | The Markdown content of every page. The wiki's root page is skipped. |
| Images | Images stored in the wiki's .attachments folder are kept and shown with the answer |
| Linked attachments | Documents linked from pages are ingested as separate knowledge items: .pdf, .doc, .docx, .txt, .md, .ppt, .pptx, .msg, and archives |
Excel and CSV attachments are not ingested. Files over 25 MB are bounced. Answers link to the page in Azure DevOps.
Sync behavior
| Behavior | Details |
|---|---|
| First sync | Full ingestion of every wiki in the selected projects |
| Later syncs | Incremental. A page is re-ingested when its content changes in the wiki's Git repository. |
| Deleted pages | Removed from the Knowledge Base on the next sync |
| Partial failures | If one project fails, for example because of missing access, the others still sync. The failure is recorded in the sync log. |
Access control
Access comes from the Audience set on each content set. Azure DevOps permissions are not inherited.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| "No projects found" or an authentication error | Wrong tenant ID, client ID, or secret, or the app wasn't added to the organization | Check the values, and complete Step 2 |
| A project is missing from the list | The app isn't a member of that project | Add the app to the project with Readers access |
| Images missing from answers | The organization uses the *.visualstudio.com URL, or a code wiki is published from a branch other than the default | Use the dev.azure.com URL |
| Edited pages aren't updated | The wiki's Git repository couldn't be read | Give the app read access to the project's repositories |
Page titles end in .md | This is expected | No action needed |
Next Steps
- Manage syncs, logs, and bounced files in Knowledge Integrations
- Set up audience targeting