Connect Knowledge
- Builder → Knowledge base is the central place to manage all knowledge sources — files, web pages, and repositories
- Upload runbooks and docs, add web pages by URL, or connect source code repositories
- Your agent references indexed knowledge automatically during investigations
- The more relevant knowledge your agent has, the faster and more accurate its responses
Why knowledge matters
Your agent is powerful out of the box with Azure observability and connected tools. But every team has unique context — runbooks, architecture docs, internal wikis, and code repositories that contain the tribal knowledge needed to resolve incidents quickly.
When your agent has access to this knowledge, it can:
- Reference your team's runbooks during incidents instead of starting from scratch
- Correlate production issues to specific code changes in your repositories
- Apply troubleshooting steps your team has already documented
Knowledge base — one place for all sources
The Knowledge base page in the portal (Builder → Knowledge base) is where you manage your agent's knowledge. You can upload files, add web pages, and view connected repositories.
Three types of knowledge sources:
| Source type | What it provides | How to add |
|---|---|---|
| Files | Runbooks, troubleshooting guides, architecture docs, configuration references | Upload via portal, drag-and-drop, or let your agent create them during conversations |
| Web pages | External documentation, status pages, internal wiki URLs | Add by URL — your agent indexes the content |
| Repositories | Source code for root cause analysis, deployment configs, infrastructure-as-code | Connect GitHub or Azure DevOps repos |
Each entry shows its name, indexing status (Indexed, Pending, or Not indexed), type, and last modified date.
Upload documents
Your agent can create and upload knowledge during conversations — ask it to save a runbook from what you just resolved, and it stores the document automatically. You can also upload files directly through the portal.
For supported file formats and size limits, see Upload Knowledge Documents → Supported file formats.
→ Upload Knowledge Documents — full details on file types, limits, and agent-generated documents
Share files in chat
You can also attach files directly in chat — drag and drop, paste from clipboard, or use the + button. Chat attachments are stored with the thread and give your agent immediate context for analysis.
After attaching a file in chat, ask your agent: "Save this to knowledge settings." The agent reads the file from the thread and uploads a copy to Knowledge settings — making it indexed and searchable across all future conversations. The original stays in the thread too.
| Upload Knowledge | Share Files in Chat | |
|---|---|---|
| Where | Builder → Knowledge settings, or ask in chat | Chat message input (+, drag/drop, paste) |
| Storage | Agent-level — indexed, searchable across all threads | Thread-level — available in that conversation |
| Best for | Runbooks, architecture docs, procedures you want the agent to reference in every future conversation | Screenshots, logs, config files you need analyzed right now |
| Promote to knowledge | Already there | Ask the agent: "Save this to knowledge settings" — it copies the content to agent-level storage |
| Formats | 28 types — documents, data, images | 31 types — adds code, scripts, infrastructure, web |
| Size limits | 16 MB per file · 100 MB per upload | 10 MB per file · 50 MB total · 5 files |
→ Share Files in Chat — drag and drop, clipboard paste, and multimodal analysis
Connect source code
Connect your GitHub or Azure DevOps repositories so your agent can read code, search for errors, and correlate deployments with incidents. Repositories appear in the knowledge base with clone and indexing status.
→ GitHub Connector — OAuth or PAT authentication, repo selection, and what your agent can do with GitHub
→ Azure DevOps Connector — OAuth, Managed Identity, or PAT authentication, plus wiki knowledge indexing
Get started
| Resource | What you'll learn |
|---|---|
| Upload Knowledge Documents → | Add runbooks and docs to your agent's knowledge base |
| Connect to ADX → | Connect Azure Data Explorer for log queries |
| Connect GitHub → | Connect a source code repository |
Related capabilities
| Capability | What it adds |
|---|---|
| Upload Knowledge Documents → | Persistent file formats, limits, and agent-generated knowledge |
| Share Files in Chat → | Temporary file attachments for immediate analysis in a conversation |
| GitHub Connector → | Source code, issues, pull requests, and workflow access |
| Azure DevOps Connector → | Source code, work items, wiki knowledge, and pipeline access |
| MCP Connectors → | Extend to Datadog, Splunk, and other external systems |