Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Estimated time: 5 minutes
Upload your runbooks and documentation so your agent uses your team's procedures, not generic advice.
What you accomplish
By the end of this step, your agent:
- Uses your runbooks when troubleshooting
- References your documentation in responses
- Shows Sources to prove which document it used
Prerequisites
| Requirement | Details |
|---|---|
| Agent created | Complete Create and set up first. |
| Documentation files | Runbooks, playbooks, or troubleshooting guides (.md, .txt). |
Note
This step covers file uploads, which is the fastest way to add knowledge. Your agent can also reference Azure DevOps repositories and GitHub repositories through Build + setup > Context > Code access, and non-Microsoft data sources through MCP connectors.
Open the knowledge base
Go to the knowledge base in the agent portal.
- Select Build + setup, and then expand Context in the left sidebar.
- Select Knowledge sources.
An empty state appears that prompts you to add a knowledge source.
Upload your files
Add your first documentation files to the knowledge base.
- Select Add file.
- Drag files or folders into the drop zone, or select browse for files to choose documentation such as runbooks, escalation procedures, and query references.
- Select Add file in the dialog.
- Wait for indexing to complete (usually instant).
| Supported formats | Maximum size |
|---|---|
Markdown (.md), Text (.txt) |
16 MB per file, 100 MB per upload |
Tip
Upload your most-used runbooks first. You can always add more later. If you don't have runbooks yet, your agent can create them for you during conversations. It turns investigation findings into documented procedures automatically.
Verify the knowledge base
Confirm your agent can access the uploaded documentation.
Ask your agent about something in your uploaded file:
What runbooks or procedures do you have in your knowledge base?
You should see the following results:
- A "Searching your knowledge base..." indicator.
- Sources showing your uploaded file name.
- Content from your document, not generic examples.
Understand the difference
Without a knowledge base, the agent responds with generic answers:
"I don't have specific information about your team's procedures..."
With your knowledge base, the agent references your documented procedures:
"Based on your knowledge base, I found the following procedures..."
Recommended documents
The following table lists common document types to upload and the value they provide.
| Document type | Example | Value |
|---|---|---|
| Troubleshooting guides | http-500-errors.md |
First response steps |
| Query references | loki-queries.md |
Team's proven queries |
| Escalation paths | on-call.md |
Who to contact |
| Runbooks | deployment-rollback.md |
Step-by-step procedures |