ADO Wiki

Introduction

This guide provides step-by-step instructions for integrating and using the Azure DevOps Wiki (ADO Wiki) toolkit within ELITEA. It covers everything from setting up your Azure DevOps Personal Access Token to configuring the toolkit and using it within your Agents, Pipelines, and Chat conversations. Azure Wiki (ADO Wiki) Azure Wiki is a collaborative documentation service for creating and managing project documentation, knowledge bases, release notes, and meeting minutes. It provides a version-controlled repository for team documentation directly within your Azure DevOps organization. Integrating Azure DevOps Wiki with ELITEA enables your Agents, Pipelines, and Chat conversations to intelligently interact with wiki pages — automating documentation creation, updates, and retrieval as part of AI-driven workflows.

Toolkit’s Account Setup and Configuration

Account Setup

Create an Azure DevOps account and organization to access the Wiki service.

Visit Azure DevOps: Navigate to https://dev.azure.com/
Start Free or Sign In: Click “Start free” to create a new organization, or “Sign in to Azure DevOps” for existing accounts
Create Organization: Follow prompts to set up your organization (provide name, select hosting region, optionally link to Azure account)
Verify Email: Confirm your email address if prompted by clicking the verification link
Enable Basic Subscription: Verify Basic subscription is enabled (typically enabled by default for new organizations)
Add Users (Optional): Navigate to https://dev.azure.com/{YourOrganizationName}/_settings/users, click “Add users”, enter user details, select “Basic” access level, and click “Add”
Verify Access: Confirm “Wiki” appears in the left sidebar of your project

If Wiki isn’t visible, verify it is enabled in organization settings under General → Services.

Generate a Personal Access Token (PAT)

For secure integration with ELITEA, use an Azure DevOps Personal Access Token (PAT).

Log in to Azure DevOps: Navigate to https://dev.azure.com/ and log in.
Access User Settings: Click the User settings icon (top right) → select “Personal access tokens”.
Generate New Token: Click ”+ New Token”.
Configure Token Details:
- Name: Enter a descriptive label (e.g., “ELITEA Wiki Integration”)
- Organization: Select your organization
- Expiration: Set an expiration date
- Scopes: Select Custom defined, then enable:
  - Wiki → Read & write (or Read if the agent only reads wiki content)
Create Token: Click “Create”.
Copy and Store Token: Copy the token immediately and store it securely in a password manager or ELITEA’s Secrets feature.

Principle of Least Privilege: Grant only the scopes essential for your ELITEA integration.Avoid “Full Access” Scopes: Never grant full access unless absolutely necessary.Regular Token Review and Rotation: Rotate tokens periodically as a security best practice.

System Integration with ELITEA

To integrate Azure DevOps Wiki with ELITEA, follow this three-step process: Create Credentials → Create Toolkit → Use in Agents.

Step 1: Create Azure DevOps Credentials

Navigate to Credentials Menu: Open the sidebar and select Credentials.
Create New Credential: Click the + Create button.
Select Azure DevOps: Choose Ado as the credential type.

Configure Credential Details:

Field	Description	Example
Display Name	Descriptive name for the credential	`Azure DevOps - Wiki Access`
ID	Unique identifier	Auto-populated from the Display Name
Organization Url	Your Azure DevOps organization URL	`https://dev.azure.com/MyCompany`
Token	Your PAT or a secret containing your PAT	`ghp_1234...`

Test Connection: Click Test Connection to verify credentials.
Save Credential: Click Save.

Use Secrets for your PAT instead of entering values directly.

Step 2: Create the Azure DevOps Wiki Toolkit

Navigate to Toolkits Menu: Open the sidebar and select Toolkits.
Create New Toolkit: Click the + Create button.
Select Azure Wiki: Choose Azure Wiki (ADO Wiki) from the available toolkit types.

Configure Toolkit Settings:

Field	Description	Example
Toolkit Name	Descriptive name for your toolkit	`ADO Wiki - Documentation Manager`
Description	Optional description of the toolkit’s purpose	`Toolkit for managing project wiki pages and knowledge base`
Ado Configuration	Select your Azure DevOps credential. A credential may be pre-selected — verify it is correct or change it as needed.	`Azure DevOps - Wiki Access`
PgVector Configuration	PgVector connection for vector database (required for indexing tools)	`elitea-pgvector`
Embedding Model	Embedding model for semantic search	`text-embedding-3-small`
Project	Your Azure DevOps project name	`ProjectAlpha`
Default Wiki Identifier	Default Wiki ID or wiki name used when no wiki is specified in tool calls	`ProjectWiki`

Enable Desired Tools: Select the checkboxes next to the specific wiki tools you want to enable. Enable only the tools your agents will actually use.
- Make Tools Available by MCP — (optional) Make selected tools accessible through external MCP clients.
Save Toolkit: Click Save.

Available Wiki Tools

Tool Category	Tool Name	Description	Primary Use Case
Wiki Access
	Get wiki	Extract ADO wiki information	Retrieve the list of all wikis available in the project
Wiki Page Retrieval
	Get wiki page	Extract ADO wiki page content	Fetch a wiki page with general parameters
	Get wiki page by path	Extract ADO wiki page content	Fetch a specific wiki page using its hierarchical path
	Get wiki page by id	Extract ADO wiki page content	Fetch a specific wiki page using its unique ID
Wiki Page Management
	Modify wiki page	Create or update ADO wiki page content	Create new or update existing wiki page content
	Rename wiki page	Rename page	Rename an existing wiki page
	Delete page by path	Delete ADO wiki page	Delete a specific wiki page using its path
	Delete page by id	Delete ADO wiki page	Delete a specific wiki page using its unique ID
Indexing & Search
	Index data	Loads Azure DevOps wiki data to index for semantic search	Enable AI-powered semantic search across wiki pages
	Search index	Performs searches across indexed content	Find specific wiki content across indexed data
	Stepback search index	Performs advanced contextual searches with broader scope	Execute sophisticated searches with expanded context
	Stepback summary index	Creates comprehensive summaries of indexed content	Generate intelligent summaries of wiki information
	Remove index	Removes previously created search indexes	Clean up and manage indexed content
	List collections	Lists available indexed collections	View and manage indexed data collections

The tools Index data, List collections, Remove index, Search index, Stepback search index, and Stepback summary index require PgVector configuration and an embedding model.

Testing Toolkit Tools

After configuring the toolkit, test individual tools from the Toolkit detail page using the Test Settings panel:

Select LLM Model from the model dropdown
Select a Tool from the available wiki tools
Provide Input — enter required parameters or test queries
Run the Test and review the response

Verify that credentials and connection are configured correctly
Validate tool functionality with your Azure DevOps environment
Test different parameter combinations before production use

For detailed instructions, see How to Test Toolkit Tools.

Step 3: Add the Wiki Toolkit to Your Workflows

In Agents

Navigate to Agents: Open the sidebar and select Agents.
Create or Edit Agent: Create a new agent or select an existing one.
Add the Toolkit: In the TOOLKITS section, click “+Toolkit” and select your ADO Wiki toolkit.

In Pipelines

Navigate to Pipelines: Open the sidebar and select Pipelines.
Create or Edit Pipeline: Create a new pipeline or select an existing one.
Add the Toolkit: In the TOOLKITS section, click “+Toolkit” and select your ADO Wiki toolkit.

In Chat

Navigate to Chat: Open the sidebar and select Chat.
Start New Conversation: Click +Create or open an existing conversation.
Add the Toolkit: In the Participants section, click to add a toolkit and select your ADO Wiki toolkit.

“Show me the latest release notes from the project wiki.”
“Update the Team Meetings page with today’s meeting notes.”
“What does the Getting Started wiki page say?”

Instructions and Prompts for Using the ADO Wiki Toolkit

When crafting instructions for agents using the ADO Wiki toolkit, clarity and precision are essential. Break down tasks into simple, actionable steps and explicitly define all parameters. Effective instructions are:

Direct and Action-Oriented: Use strong action verbs (e.g., “Use the ‘get_wiki_page_by_path’ tool…”, “Update the wiki page using ‘modify_wiki_page’…”)
Parameter-Centric: Specify each required parameter and how the agent should obtain its value
Step-by-Step Structured: Use numbered steps for complex workflows

Retrieving a Wiki Page:

1. Goal: Retrieve content from a specific wiki page.
2. Tool: Use the "get_wiki_page_by_path" tool.
3. Parameters:
    - wiki_path: "Get the wiki page path from the user. Example: '/Release Notes/Latest'"
    - wiki_identifier: "Use the default wiki or ask the user which wiki to access"
4. Outcome: Display the wiki page content to the user with proper formatting.

Updating a Wiki Page:

1. Goal: Add new content to an existing wiki page.
2. Tool: Use the "modify_wiki_page" tool.
3. Parameters:
    - wiki_path: "Ask the user for the page path (e.g., '/Team Meetings')"
    - content: "Combine the existing page content with the new content provided by the user"
    - wiki_identifier: "Use the default wiki"
4. Outcome: Confirm the page was updated successfully and display the updated content.

Chat Usage Examples

Get Wiki Page by Path

Chat Example:

User: "Show me the latest release notes from our project wiki."

Agent Response: [Agent uses get_wiki_page_by_path tool]

📄 **Release Notes - Version 2.5.0**

**Released**: November 10, 2025

**New Features**:
- Enhanced user authentication with OAuth 2.0 support
- Real-time collaboration features in document editing
- Advanced search capabilities with AI-powered suggestions

**Bug Fixes**:
- Fixed issue with file upload timeouts
- Resolved memory leak in background processes
- Corrected timezone display in activity logs

Modify Wiki Page

Chat Example:

User: "Add today's meeting notes to the 'Team Meetings' wiki page."

Agent Response: [Agent uses modify_wiki_page tool]

✅ **Wiki Page Updated Successfully!**

- **Page**: Team Meetings
- **Path**: /Project Documentation/Team Meetings
- **Updated**: November 12, 2025

Added content includes attendees, agenda, key decisions, and action items.

Best Practices

Test Integration Thoroughly

After setting up the toolkit, test each tool you intend to use to ensure connectivity, correct authentication, and accurate execution of wiki actions.

Monitor Agent Performance

Regularly monitor agents using the ADO Wiki toolkit. Track task completion, execution time, and error rates.

Follow Security Best Practices

Use Personal Access Tokens instead of your main account password
Grant only the minimum necessary scopes (Wiki: Read or Read & write)
Store PATs using ELITEA’s Secrets Management feature

Provide Clear Instructions

Craft clear, unambiguous agent instructions. Specify wiki paths and identifiers explicitly to avoid ambiguity.

Start with Simple Use Cases

Begin with read-only operations (retrieving wiki pages) before enabling write operations (creating or modifying pages).

Automated Retrieval of Release Notes

Scenario: An agent automatically retrieves the latest release notes from the project wiki during support interactions.
Tools Used: get_wiki_page_by_path
Example Instruction: “Use ‘get_wiki_page_by_path’ to read the wiki page at ‘/Release Notes/Latest Release’ and display it to the user.”
Benefit: Provides agents with immediate access to current release information, improving support efficiency.

Dynamic Content Creation for Project Dashboards

Scenario: Agents dynamically generate wiki content by aggregating data from other ELITEA workflows.
Tools Used: modify_wiki_page
Example Instruction: “Use ‘modify_wiki_page’ to update the ‘Project Dashboard’ wiki page with the latest build status and test results.”
Benefit: Keeps dashboards current automatically without manual updates.

Automated Wiki Cleanup

Scenario: Automatically delete outdated meeting minutes or temporary documentation after a set period.
Tools Used: delete_wiki_page_by_path
Example Instruction: “Use ‘delete_wiki_page_by_path’ to delete pages in ‘/Meeting Minutes/Archive’ that are older than 90 days.”
Benefit: Keeps the project wiki organized and easy to navigate.

Troubleshooting

Connection Issues

Problem: Agent fails to connect to Azure DevOps Wiki.

Verify the organization URL is correct (e.g., https://dev.azure.com/YourOrganizationName)
Check that your PAT is accurate and not expired
Regenerate the PAT if needed and update your ELITEA credential
Verify network connectivity and firewall settings

Authorization Errors

Problem: “Permission Denied” or “Unauthorized” errors.

Ensure the PAT has the vso.wiki_full scope for full wiki access
Verify your Azure DevOps account has the necessary project permissions
Check that the PAT has not expired

Incorrect Organization or Project Names

Problem: Cannot find specified organization or project.

Verify the organization name matches your Azure DevOps URL exactly
Confirm the project name is correct (case-sensitive)
Ensure the URL format is: https://dev.azure.com/YourOrganizationName

Wiki Access Issues

Problem: Cannot access specific wiki pages.

Confirm the wiki page exists at the specified path
Verify the PAT has appropriate wiki scopes
Ensure the Wiki service is enabled for the project (Project Settings → Services)
Check that paths use the correct hierarchical format (e.g., /Folder/PageName)

Indexing and Search Tool Errors

Problem: Indexing tools fail or search returns no results.

Verify PgVector is properly configured in toolkit settings
Confirm an embedding model is selected
Ensure the index was created successfully before searching
Verify there is data available to index

Wiki Identifier Not Provided Error

Problem: Tools fail with an error such as “Wiki identifier must be provided either as a parameter or configured as default in toolkit settings.”Cause: The tool was called without a wiki_identified parameter and no Default Wiki Identifier is set in the toolkit configuration.Resolution:

Open the toolkit settings and set the Default Wiki Identifier field to your wiki name (e.g., ProjectAlpha.wiki for the project wiki, or the custom name you assigned when creating a code wiki)
Alternatively, instruct the agent to always pass the wiki_identified parameter explicitly in each tool call

To find your wiki identifier: In Azure DevOps, open your project and navigate to Overview → Wiki. The wiki name appears in the URL and in the wiki title bar.

Support Contact

If you encounter issues not covered in this guide, contact the ELITEA support team.Email: SupportAlita@epam.com

FAQ

Can I use my regular Azure DevOps password instead of a Personal Access Token?

No. You must use a Personal Access Token for secure integration. Regular passwords are not supported.

What scopes should I grant to the PAT for Wiki?

Grant Wiki → Read & write for full access, or Wiki → Read if the agent only needs to read wiki content. Always follow the principle of least privilege.

What is the correct format for the Azure DevOps Organization URL?

https://dev.azure.com/YourOrganizationName — replace YourOrganizationName with your actual organization name. Do not include the project name in the URL.

Can I use the same credential for multiple ADO toolkits?

Yes. One Azure DevOps credential can be reused across Wiki, Boards, and Test Plans toolkits as long as the PAT has the necessary scopes for all services.

How do I find my Azure DevOps organization and project names?

Your organization name appears in the URL when you log in (e.g., https://dev.azure.com/YourOrgName). Project names are listed in the Azure DevOps interface under your organization.

Why am I getting 'Permission Denied' errors even with a valid token?

Verify the PAT has the vso.wiki_write scope for write operations. Also ensure your Azure DevOps account has project-level permissions — having a valid token does not automatically grant project access.

What value should I use for the Default Wiki Identifier field?

The Default Wiki Identifier accepts either a wiki ID (a GUID) or the wiki name. For project wikis automatically created by Azure DevOps, the name is typically {ProjectName}.wiki (e.g., ProjectAlpha.wiki). For code wikis, use the name you assigned during creation.To find the correct value: in Azure DevOps, navigate to Overview → Wiki and check the name in the URL or the wiki title bar.

What happens when I try to create a wiki page that does not exist?

The modify_wiki_page tool handles missing pages gracefully:

If the page does not exist at the given path, it is created automatically
If the wiki itself does not exist under the given name, the toolkit creates a new wiki first, then creates the page

This means you can use modify_wiki_page for both creating new pages and updating existing ones without separate setup steps.

What branch name should I use when modifying or renaming wiki pages?

The default branch for Azure DevOps wikis is wikiMaster. Use this value for the version_identifier parameter in modify_wiki_page and rename_wiki_page calls unless your wiki uses a custom branch.If an invalid version identifier is provided to rename_wiki_page, the toolkit automatically retries the operation without the version constraint.

Can the agent describe images embedded in wiki pages?

Yes. By default, when retrieving wiki page content, the toolkit processes embedded images and replaces them with AI-generated descriptions (requires an LLM to be configured on the agent). To retrieve raw content without image processing — which is faster — instruct the agent to use process_images=False when calling get_wiki_page_by_path, get_wiki_page_by_id, or get_wiki_page.

How do I retrieve a full wiki page hierarchy including all sub-pages?

Use the get_wiki_page tool with recursion_level set to your desired depth:

Value	Behavior
`none`	Returns only the requested page metadata, no sub-pages
`oneLevel`	Returns the page and its direct children (default)
`oneLevelPlusNestedEmptyFolders`	Direct children plus chains of nested single-child folders
`full`	Returns the entire descendant hierarchy from the page downward

Example: to map the complete structure of a wiki section, use recursion_level='full'.

Do I need PgVector configuration for all wiki tools?

No. PgVector is only required for indexing and semantic search tools: Index data, Search index, Stepback search index, Stepback summary index, Remove index, and List collections. All other wiki tools work without it.

What's the difference between 'get_wiki_page_by_path' and 'get_wiki_page_by_id'?

get_wiki_page_by_path: Uses the hierarchical path (e.g., /Release Notes/Latest). More intuitive and user-friendly.
get_wiki_page_by_id: Uses the unique numeric ID of the wiki page. More precise but requires knowing the ID in advance.

Use the path-based method for most cases.

How do I update my PAT when it expires?

Generate a new PAT in Azure DevOps
Navigate to Credentials in ELITEA
Edit your Azure DevOps credential and update the Token field
Save the credential — all toolkits using it will automatically use the new token

Agent Menu — Complete reference for agent management
How to Use Chat Functionality — Guide to using ELITEA Chat with toolkits
Create and Edit Agents from Canvas — Quickly create agents from chat canvas
Indexing Overview — Understanding ELITEA’s indexing capabilities
Index ADO Wiki Data — Detailed instructions for indexing Azure DevOps Wiki data
Azure Repos (ADO Repos) Toolkit Integration Guide — Integrate Azure Repos for version control

Azure DevOps Documentation — Official Microsoft documentation
Azure Wiki Documentation — Creating and managing project wikis
Personal Access Tokens Guide — Best practices for PAT management

MCP

Toolkits

Applications

Third-Party Integrations

Extensions

Introduction

Toolkit’s Account Setup and Configuration

Account Setup

Generate a Personal Access Token (PAT)

System Integration with ELITEA

Step 1: Create Azure DevOps Credentials

Step 2: Create the Azure DevOps Wiki Toolkit

Available Wiki Tools

Testing Toolkit Tools

Step 3: Add the Wiki Toolkit to Your Workflows

In Agents

In Pipelines

In Chat

Instructions and Prompts for Using the ADO Wiki Toolkit

Chat Usage Examples

Best Practices

Troubleshooting

Support Contact

FAQ

​Introduction

​Toolkit’s Account Setup and Configuration

​Account Setup

​Generate a Personal Access Token (PAT)

​System Integration with ELITEA

​Step 1: Create Azure DevOps Credentials

​Step 2: Create the Azure DevOps Wiki Toolkit

​Available Wiki Tools

​Testing Toolkit Tools

​Step 3: Add the Wiki Toolkit to Your Workflows

​In Agents

​In Pipelines

​In Chat

​Instructions and Prompts for Using the ADO Wiki Toolkit

​Chat Usage Examples

​Best Practices

​Troubleshooting

Support Contact

​FAQ

Introduction

Toolkit’s Account Setup and Configuration

Account Setup

Generate a Personal Access Token (PAT)

System Integration with ELITEA

Step 1: Create Azure DevOps Credentials

Step 2: Create the Azure DevOps Wiki Toolkit

Available Wiki Tools

Testing Toolkit Tools

Step 3: Add the Wiki Toolkit to Your Workflows

In Agents

In Pipelines

In Chat

Instructions and Prompts for Using the ADO Wiki Toolkit

Chat Usage Examples

Best Practices

Troubleshooting

FAQ