Skip to main content

​
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.
  1. Visit Azure DevOps: Navigate to https://dev.azure.com/
  2. Start Free or Sign In: Click “Start free” to create a new organization, or “Sign in to Azure DevOps” for existing accounts
  3. Create Organization: Follow prompts to set up your organization (provide name, select hosting region, optionally link to Azure account)
  4. Verify Email: Confirm your email address if prompted by clicking the verification link
  5. Enable Basic Subscription: Verify Basic subscription is enabled (typically enabled by default for new organizations)
  6. 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” Add user
  7. 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).
  1. Log in to Azure DevOps: Navigate to https://dev.azure.com/ and log in.
  2. Access User Settings: Click the User settings icon (top right) → select “Personal access tokens”.
  3. Generate New Token: Click ”+ New Token”.
  4. 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)
  5. Create Token: Click “Create”.
  6. Copy and Store Token: Copy the token immediately and store it securely in a password manager or ELITEA’s Secrets feature. Generate PAT
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

  1. Navigate to Credentials Menu: Open the sidebar and select Credentials.
  2. Create New Credential: Click the + Create button.
  3. Select Azure DevOps: Choose Ado as the credential type. Azure DevOps Credential Access
  4. Configure Credential Details:
    FieldDescriptionExample
    Display NameDescriptive name for the credentialAzure DevOps - Wiki Access
    IDUnique identifierAuto-populated from the Display Name
    Organization UrlYour Azure DevOps organization URLhttps://dev.azure.com/MyCompany
    TokenYour PAT or a secret containing your PATghp_1234...
  5. Test Connection: Click Test Connection to verify credentials.
  6. Save Credential: Click Save. Create Credentials
Use Secrets for your PAT instead of entering values directly.

​
Step 2: Create the Azure DevOps Wiki Toolkit

  1. Navigate to Toolkits Menu: Open the sidebar and select Toolkits.
  2. Create New Toolkit: Click the + Create button.
  3. Select Azure Wiki: Choose Azure Wiki (ADO Wiki) from the available toolkit types. Azure DevOps Wiki Toolkit Access
  4. Configure Toolkit Settings:
    FieldDescriptionExample
    Toolkit NameDescriptive name for your toolkitADO Wiki - Documentation Manager
    DescriptionOptional description of the toolkit’s purposeToolkit for managing project wiki pages and knowledge base
    Ado ConfigurationSelect your Azure DevOps credential. A credential may be pre-selected — verify it is correct or change it as needed.Azure DevOps - Wiki Access
    PgVector ConfigurationPgVector connection for vector database (required for indexing tools)elitea-pgvector
    Embedding ModelEmbedding model for semantic searchtext-embedding-3-small
    ProjectYour Azure DevOps project nameProjectAlpha
    Default Wiki IdentifierDefault Wiki ID or wiki name used when no wiki is specified in tool callsProjectWiki
  5. 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.
  6. Save Toolkit: Click Save.
Create Wiki Toolkit

​
Available Wiki Tools

Tool CategoryTool NameDescriptionPrimary Use Case
Wiki Access
Get wikiExtract ADO wiki informationRetrieve the list of all wikis available in the project
Wiki Page Retrieval
Get wiki pageExtract ADO wiki page contentFetch a wiki page with general parameters
Get wiki page by pathExtract ADO wiki page contentFetch a specific wiki page using its hierarchical path
Get wiki page by idExtract ADO wiki page contentFetch a specific wiki page using its unique ID
Wiki Page Management
Modify wiki pageCreate or update ADO wiki page contentCreate new or update existing wiki page content
Rename wiki pageRename pageRename an existing wiki page
Delete page by pathDelete ADO wiki pageDelete a specific wiki page using its path
Delete page by idDelete ADO wiki pageDelete a specific wiki page using its unique ID
Indexing & Search
Index dataLoads Azure DevOps wiki data to index for semantic searchEnable AI-powered semantic search across wiki pages
Search indexPerforms searches across indexed contentFind specific wiki content across indexed data
Stepback search indexPerforms advanced contextual searches with broader scopeExecute sophisticated searches with expanded context
Stepback summary indexCreates comprehensive summaries of indexed contentGenerate intelligent summaries of wiki information
Remove indexRemoves previously created search indexesClean up and manage indexed content
List collectionsLists available indexed collectionsView 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:
  1. Select LLM Model from the model dropdown
  2. Select a Tool from the available wiki tools
  3. Provide Input — enter required parameters or test queries
  4. 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

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

​
In Pipelines

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

​
In Chat

  1. Navigate to Chat: Open the sidebar and select Chat.
  2. Start New Conversation: Click +Create or open an existing conversation.
  3. Add the Toolkit: In the Participants section, click to add a toolkit and select your ADO Wiki toolkit.
Add to Chat
  • “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

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
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

After setting up the toolkit, test each tool you intend to use to ensure connectivity, correct authentication, and accurate execution of wiki actions.
Regularly monitor agents using the ADO Wiki toolkit. Track task completion, execution time, and error rates.
  • 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
Craft clear, unambiguous agent instructions. Specify wiki paths and identifiers explicitly to avoid ambiguity.
Begin with read-only operations (retrieving wiki pages) before enabling write operations (creating or modifying pages).
  • 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.
  • 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.
  • 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

Problem: Agent fails to connect to Azure DevOps Wiki.
  1. Verify the organization URL is correct (e.g., https://dev.azure.com/YourOrganizationName)
  2. Check that your PAT is accurate and not expired
  3. Regenerate the PAT if needed and update your ELITEA credential
  4. Verify network connectivity and firewall settings
Problem: “Permission Denied” or “Unauthorized” errors.
  1. Ensure the PAT has the vso.wiki_full scope for full wiki access
  2. Verify your Azure DevOps account has the necessary project permissions
  3. Check that the PAT has not expired
Problem: Cannot find specified organization or project.
  1. Verify the organization name matches your Azure DevOps URL exactly
  2. Confirm the project name is correct (case-sensitive)
  3. Ensure the URL format is: https://dev.azure.com/YourOrganizationName
Problem: Cannot access specific wiki pages.
  1. Confirm the wiki page exists at the specified path
  2. Verify the PAT has appropriate wiki scopes
  3. Ensure the Wiki service is enabled for the project (Project Settings → Services)
  4. Check that paths use the correct hierarchical format (e.g., /Folder/PageName)
Problem: Indexing tools fail or search returns no results.
  1. Verify PgVector is properly configured in toolkit settings
  2. Confirm an embedding model is selected
  3. Ensure the index was created successfully before searching
  4. Verify there is data available to index
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

No. You must use a Personal Access Token for secure integration. Regular passwords are not supported.
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.
https://dev.azure.com/YourOrganizationName — replace YourOrganizationName with your actual organization name. Do not include the project name in the URL.
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.
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.
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.
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.
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.
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.
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.
Use the get_wiki_page tool with recursion_level set to your desired depth:
ValueBehavior
noneReturns only the requested page metadata, no sub-pages
oneLevelReturns the page and its direct children (default)
oneLevelPlusNestedEmptyFoldersDirect children plus chains of nested single-child folders
fullReturns the entire descendant hierarchy from the page downward
Example: to map the complete structure of a wiki section, use recursion_level='full'.
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.
  • 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.
  1. Generate a new PAT in Azure DevOps
  2. Navigate to Credentials in ELITEA
  3. Edit your Azure DevOps credential and update the Token field
  4. Save the credential — all toolkits using it will automatically use the new token