Skip to main content

Step 2: Add Your Team's Knowledge

5 min · Teach your agent YOUR team's procedures so it gives relevant answers.

What you'll accomplish​

By the end of this step, your agent will:

  • Use YOUR runbooks when troubleshooting
  • Reference YOUR documentation in responses
  • Show Sources proving which document it used

Prerequisites​

RequirementDetails
Agent createdComplete Step 1 first
Documentation filesRunbooks, playbooks, or troubleshooting guides (.md, .txt)
Knowledge sources go beyond file uploads

This step covers file uploads—the fastest way to add knowledge. Your agent can also reference documentation from Azure DevOps repositories and GitHub repositories via connectors (see Builder → Connectors), and even third-party data sources via MCP connectors.

Step 1: Open the knowledge base​

  1. Click Builder in the left sidebar.
  2. Select Knowledge base.

You'll see an empty state prompting you to add a knowledge source.

Step 2: Upload your files​

  1. Click Add file.
  2. Select your documentation files — runbooks, escalation procedures, query references.
  3. Wait for indexing (usually instant).
Supported formatsMax size
Markdown (.md), Text (.txt)16 MB per file, 100 MB per upload
Start with 2-3 files

Upload your most-used runbooks first. You can always add more later. Don't have runbooks yet? Your agent can create them for you during conversations — it turns investigation findings into documented procedures automatically.

Verify it works​

Ask your agent about something in your uploaded file:

What runbooks or procedures do you have in your knowledge base?

You should see:

  1. "Searching your knowledge base..." indicator
  2. Sources: showing your uploaded file name
  3. Content FROM your document—not generic examples

Agent response showing sources from knowledge base

The difference​

Without knowledge base:

"I don't have specific information about your team's procedures..."

With YOUR knowledge base:

"Based on your knowledge base, I found the following procedures in [your-file.md]:

  1. [Content from YOUR document]
  2. [More content from YOUR document]"

Your agent references YOUR documented procedures, not generic examples.

What to upload​

Document TypeExampleValue
Troubleshooting guideshttp-500-errors.mdFirst response steps
Query referencesloki-queries.mdTeam's proven queries
Escalation pathson-call.mdWho to contact when
Runbooksdeployment-rollback.mdStep-by-step procedures

What you unlocked​

✅ Your agent now:

  • Uses YOUR team's procedures when troubleshooting
  • References YOUR runbooks when troubleshooting
  • Searches YOUR knowledge base first before answering
  • Shows Sources proving which document it used

Next step​

→ Step 3: Connect Source Code

Learn more​

Last updated on
Was this page helpful?
Report an issue with this page