Skip to content

Commit b28722b

Browse files
v-dirichardsv-dirichards
authored
Merge pull request #314174 from craigshoemaker/learn/sre-agent-pr6030-connectors
SRE Agent: Connectors and knowledge sources from PR 6030 (split 1/2)
2 parents 5d707cc + abc99df commit b28722b

10 files changed

Lines changed: 694 additions & 243 deletions

‎articles/sre-agent/add-web-page-knowledge.md‎

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
---
2+
title: Add Web Page Knowledge Sources in Azure SRE Agent
3+
description: Learn how to add publicly accessible web pages as knowledge sources in Azure SRE Agent.
4+
ms.topic: concept-article
5+
ms.service: azure-sre-agent
6+
ms.date: 04/03/2026
7+
author: dm-chelupati
8+
ms.author: dchelupati
9+
ms.ai-usage: ai-assisted
10+
ms.custom: knowledge, web-page, URL, knowledge-base, external-resources
11+
---
12+
13+
# Add web page knowledge sources in Azure SRE Agent
14+
15+
Add any publicly accessible web page by URL. Your agent automatically fetches and indexes the content so it can reference external documentation, status pages, and wiki articles during investigations.
16+
17+
> [!TIP]
18+
> - Add any publicly accessible web page by URL. Your agent automatically fetches and indexes the content.
19+
> - Reference external documentation, status pages, runbook sites, and wiki articles during investigations.
20+
> - One-step setup: provide a URL, name, and optional description.
21+
22+
## The problem: external docs stay external
23+
24+
Your team's knowledge isn't all in one place. Runbooks live on wiki sites. Vendor documentation is on external portals. Architecture diagrams and status pages are scattered across different URLs. When your agent investigates an issue, it can't reference these external resources - unless someone manually copies the content and uploads it as a file.
25+
26+
That manual process is tedious and creates stale copies. The original page gets updated, but the uploaded file doesn't.
27+
28+
## How web page knowledge works
29+
30+
When you add a web page as a knowledge source, the agent fetches the page content and stores it for reference:
31+
32+
1. You provide a URL, a name, and an optional description.
33+
1. The agent fetches the page content through an anonymous HTTP request.
34+
1. The page content is stored and indexed.
35+
1. Your agent can reference this content during conversations and investigations.
36+
37+
The fetch happens when you add the URL. Content is stored as a point-in-time snapshot of the page.
38+
39+
The agent fetches pages anonymously, without authentication credentials. Pages that require sign in, VPN access, or corporate SSO can't be indexed. To add content from protected pages, [upload it as a file](upload-knowledge-document.md) instead.
40+
41+
## What gets indexed
42+
43+
| Aspect | Behavior |
44+
|--------|----------|
45+
| **Content fetched** | Full page content from the single URL provided |
46+
| **Link following** | No. Only the specified URL is fetched, not linked pages |
47+
| **Authentication** | Anonymous. No credentials are sent with the request |
48+
| **Supported protocols** | HTTP and HTTPS |
49+
| **Fetch timeout** | 30 seconds |
50+
| **Refresh** | Manual. Delete and re-add the URL to get updated content |
51+
52+
## When to use web page knowledge
53+
54+
Web page knowledge sources work best for:
55+
56+
- **Public documentation**: vendor docs, API references, cloud service guides
57+
- **Status pages**: service health dashboards, incident history pages
58+
- **Wiki articles**: publicly accessible knowledge base articles
59+
- **Architecture overviews**: publicly hosted architecture diagrams and design docs
60+
- **Runbook sites**: external runbook repositories accessible without authentication
61+
62+
For internal or protected content that requires authentication, use [file uploads](upload-knowledge-document.md) instead.
63+
64+
## Limitations
65+
66+
| Limitation | Details |
67+
|------------|---------|
68+
| **No authentication** | Can't access pages behind authentication, VPN, or SSO |
69+
| **Single page only** | Doesn't crawl or follow links to other pages |
70+
| **Point-in-time snapshot** | Content isn't automatically refreshed when the source page changes |
71+
| **30-second timeout** | Pages that take longer than 30 seconds to load fail |
72+
| **URL format** | Must be an absolute HTTP or HTTPS URL |
73+
74+
## Related content
75+
76+
- [Connect knowledge](connect-knowledge.md)
77+
- [Upload knowledge documents](upload-knowledge-document.md)
78+
- [File attachments](file-attachments.md)
79+
80+
## Next step
81+
82+
> [!div class="nextstepaction"]
83+
> [Add a web page knowledge source](tutorial-upload-knowledge-document.md)

‎articles/sre-agent/add-web-page.md‎

Lines changed: 97 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,97 @@
1+
---
2+
title: "Tutorial: Add a Web Page Knowledge Source in Azure SRE Agent"
3+
description: Add a web page URL as a knowledge source so your agent can reference external documentation.
4+
ms.topic: tutorial
5+
ms.service: azure-sre-agent
6+
ms.date: 04/03/2026
7+
author: dm-chelupati
8+
ms.author: dchelupati
9+
ms.ai-usage: ai-assisted
10+
ms.custom: knowledge, web-page, URL, tutorial
11+
---
12+
13+
# Tutorial: Add a web page knowledge source in Azure SRE Agent
14+
15+
Add a public URL as a knowledge source that your agent references during investigations. You add the URL, verify it appears in the knowledge base, and confirm your agent can use the content.
16+
17+
**Time**: ~5 minutes
18+
19+
## Prerequisites
20+
21+
- An Azure SRE Agent in **Running** state
22+
- **Write** permissions on the agent (AgentMemoryWrite)
23+
- A publicly accessible web page URL (any page that loads in a browser without authentication)
24+
25+
## Step 1: Open Knowledge Sources
26+
27+
1. Go to [sre.azure.com](https://sre.azure.com) and select your agent.
28+
1. In the left sidebar, select **Builder**.
29+
1. Select **Knowledge Sources**.
30+
31+
You see the Knowledge Sources page with three action cards: **Add file**, **Add web page**, and **Add repository**.
32+
33+
## Step 2: Open the Add Web Page dialog
34+
35+
Select the **Add web page** card (the one with the globe icon).
36+
37+
A dialog opens with three fields:
38+
39+
- **Web page URL** (required): the URL to fetch
40+
- **Name** (required): a display name for this knowledge source
41+
- **Description** (optional): a brief description of what the page contains
42+
43+
## Step 3: Enter the web page details
44+
45+
1. **Web page URL**: Enter the full URL of the page you want to add. For example: `https://learn.microsoft.com/en-us/azure/azure-monitor/overview`
46+
1. **Name**: Enter a descriptive name, such as `Azure Monitor Overview`.
47+
1. **Description**: Optionally describe the content.
48+
49+
> [!NOTE]
50+
> The URL must be an absolute URL (starting with `http://` or `https://`), publicly accessible, and reachable within 30 seconds.
51+
52+
## Step 4: Add the web page
53+
54+
Select **Add web page**.
55+
56+
The agent fetches the page content. If successful, a notification confirms the web page was added and the dialog closes automatically.
57+
58+
Common errors:
59+
60+
| Error | Cause | Fix |
61+
|-------|-------|-----|
62+
| Invalid URL format | URL isn't absolute or not HTTP/HTTPS | Use a full URL starting with `https://` |
63+
| HTTP 403 | Page blocks automated requests | Try a different page, or upload the content as a file instead |
64+
| HTTP 404 | Page not found | Check the URL for typos |
65+
| Request timed out | Page took longer than 30 seconds | Try again, or upload the content as a file |
66+
| Empty content | Page requires JavaScript to render | Upload the content as a file instead |
67+
68+
## Step 5: Verify the knowledge source
69+
70+
After adding the web page, it appears in the Knowledge Sources list. Verify the following values:
71+
72+
- **Name**: the display name you provided
73+
- **Type**: shows as **Web page**
74+
- **Status**: indicates whether the content was indexed
75+
76+
## Step 6: Test with your agent
77+
78+
1. Go to **Chats** in the left sidebar.
79+
1. Start a new conversation.
80+
1. Ask a question related to the web page content.
81+
82+
Your agent should reference information from the web page in its response.
83+
84+
## Updating web page content
85+
86+
Web page knowledge sources are point-in-time snapshots. To refresh the content:
87+
88+
1. Go to **Builder > Knowledge Sources**.
89+
1. Select the web page entry.
90+
1. Delete it.
91+
1. Re-add the URL by using the same steps.
92+
93+
## Related content
94+
95+
- [Upload knowledge documents](tutorial-upload-knowledge-document.md)
96+
- [Connect source code](connect-source-code.md)
97+
- [Connect knowledge](connect-knowledge.md)

‎articles/sre-agent/configuration-deletion.md‎

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: Remove Resources from Agent Scope in Azure SRE Agent
3+
description: Learn how to select and delete configured resources from your Azure SRE Agent scope.
4+
ms.topic: concept-article
5+
ms.service: azure-sre-agent
6+
ms.date: 04/03/2026
7+
author: dm-chelupati
8+
ms.author: dchelupati
9+
ms.ai-usage: ai-assisted
10+
ms.custom: delete, remove, configuration, scope, resources, cleanup
11+
---
12+
13+
# Remove resources from agent scope in Azure SRE Agent
14+
15+
Select and remove configured resources directly from the agent configuration overview without using the setup wizard. This process works for code repositories, log connectors, deployment connectors, Azure subscriptions, and resource groups.
16+
17+
> [!TIP]
18+
> - Select and remove configured resources directly from the agent configuration overview
19+
> - When you remove subscriptions or resource groups, the agent automatically revokes its managed identity permissions
20+
> - No need to re-enter the full setup wizard to clean up stale resources
21+
22+
## The problem
23+
24+
As your infrastructure evolves, your agent's scope needs to evolve with it. Repositories get archived, connectors point to decommissioned services, and subscriptions shift between teams. Previously, removing a resource from your agent's monitoring scope meant re-entering the full setup wizard.
25+
26+
## Prerequisites
27+
28+
- An Azure SRE Agent with at least one configured resource (repository, connector, subscription, or resource group)
29+
- Contributor or Owner role on the agent resource
30+
31+
## How removing resources works
32+
33+
Each resource grid in the configuration overview includes checkboxes for selection and a **Delete** button that appears when you select one or more items.
34+
35+
1. **Open the configuration overview.** From your agent's overview page, select **Expand** on the configuration status bar to see your configured resources organized by category.
36+
37+
1. **Select items to remove.** Each resource row has a checkbox. Select individual items or use the header checkbox to select all items in a category.
38+
39+
1. **Select Delete.** A **Delete** button with a trash icon appears next to the category header when you select items. A confirmation dialog titled **Remove from scope** appears, warning that permissions on those resources are revoked. Select **Remove** to confirm or **Cancel** to keep the resources.
40+
41+
1. **Resources are removed immediately.** The grid refreshes and the deleted items disappear. For Azure subscriptions and resource groups, the agent also revokes its managed identity role assignments on those resources.
42+
43+
### What you can remove
44+
45+
| Resource type | What happens on removal |
46+
|--------------|------------------------|
47+
| Code repositories | Repository disconnects from the agent's knowledge graph |
48+
| Log connectors | Agent loses access to log querying tools for that connector |
49+
| Deployment connectors | Agent loses access to deployment history from that connector |
50+
| Azure subscriptions | Subscription removed from monitored scope; managed identity permissions revoked |
51+
| Resource groups | Resource group removed from monitored scope; managed identity permissions revoked |
52+
53+
> [!WARNING]
54+
> Removal can't be undone. To restore a removed resource, re-add it through the setup wizard. You can't remove knowledge files from the configuration overview. Use the full setup wizard to manage them.
55+
56+
## Before and after
57+
58+
| Aspect | Before | After |
59+
|--------|--------|-------|
60+
| **Removing a resource** | Re-enter the full setup wizard | Select and delete from the overview |
61+
| **Stale connectors** | Visible but no way to remove without the wizard | Select, delete, done |
62+
| **Orphaned permissions** | Agent keeps permissions on removed subscriptions | Managed identity permissions automatically revoked |
63+
64+
## Related content
65+
66+
- [Favorites and Mine filter](favorites-mine-filter.md)
67+
- [Agent playground](agent-playground.md)

‎articles/sre-agent/connect-ado-repo-managed-identity.md‎

Lines changed: 104 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,104 @@
1+
---
2+
title: "Tutorial: Connect an ADO Repository with Managed Identity in Azure SRE Agent"
3+
description: Connect an Azure DevOps repository to your agent using managed identity authentication.
4+
ms.topic: tutorial
5+
ms.service: azure-sre-agent
6+
ms.date: 04/03/2026
7+
author: dm-chelupati
8+
ms.author: dchelupati
9+
ms.ai-usage: ai-assisted
10+
ms.custom: managed identity, azure devops, ado, repository, tutorial
11+
---
12+
13+
# Tutorial: Connect an ADO repository with managed identity in Azure SRE Agent
14+
15+
Connect an Azure DevOps repository to your agent using managed identity so you don't need to create or rotate PATs. Your agent uses its own Azure identity to access ADO repos for code-aware investigations.
16+
17+
**Time**: ~10 minutes (including ADO admin setup)
18+
19+
## Prerequisites
20+
21+
- An Azure SRE Agent in **Running** state
22+
- A managed identity enabled on your agent (system-assigned or user-assigned)
23+
- An Azure DevOps organization with at least one repository
24+
- **SRE Agent Administrator** or **Standard User** role on the agent
25+
26+
## Step 1: Grant the managed identity access to your ADO organization
27+
28+
Before connecting from the agent portal, your managed identity must have access to the Azure DevOps organization.
29+
30+
1. Go to your [Azure DevOps organization settings](https://dev.azure.com/) and select your organization.
31+
1. Go to **Organization settings** > **Users**.
32+
1. Select **Add users**.
33+
1. Search for your agent's managed identity by its service principal name or object ID.
34+
1. Set the access level to **Basic** (or higher).
35+
1. Add the identity to projects with **Code (Read)** permissions on the target repositories.
36+
37+
**Checkpoint:** The managed identity appears in the ADO Users list with a Basic access level.
38+
39+
## Step 2: Go to Knowledge sources
40+
41+
1. Open your agent in the [Azure SRE Agent portal](https://sre.azure.com).
42+
1. In the left sidebar, expand **Builder**.
43+
1. Select **Knowledge sources**.
44+
45+
**Checkpoint:** The Knowledge Sources page loads and shows any existing repository connections.
46+
47+
## Step 3: Open the Add Repository dialog
48+
49+
Select **Add repository**.
50+
51+
**Checkpoint:** The Add repositories dialog opens and shows platform selection cards, such as GitHub and Azure DevOps.
52+
53+
## Step 4: Select Azure DevOps with Managed Identity
54+
55+
1. Select the **Azure DevOps** platform card.
56+
1. Under **Sign In Methods**, select **Managed Identity**.
57+
58+
**Checkpoint:** The managed identity configuration form appears with an organization field and identity dropdown.
59+
60+
## Step 5: Configure the managed identity connection
61+
62+
1. Enter your Azure DevOps **Organization** name, which is the part after `dev.azure.com/` in your ADO URL.
63+
1. From the managed identity dropdown, select your identity:
64+
- **System assigned**: uses the agent's built-in identity
65+
- **User assigned**: select a specific identity attached to the agent
66+
1. Select **Connect**.
67+
68+
**Checkpoint:** The button changes to **Connected** with a checkmark.
69+
70+
> [!NOTE]
71+
> If the dropdown is empty, your agent might not have a managed identity enabled. Select the **Add identity** link below the dropdown to open the Azure portal Identity blade for your agent resource.
72+
73+
## Step 6: Advance to repository selection
74+
75+
Select **Next** to proceed to the repository selection step.
76+
77+
**Checkpoint:** The dialog advances to show a project picker and repository grid.
78+
79+
## Step 7: Select a project and add repositories
80+
81+
1. From the **Azure DevOps Project** dropdown, select the project containing your repositories.
82+
1. Select **Add** to add a repository row.
83+
1. From the **Repository** dropdown, select a repository from the project.
84+
1. Enter a **Display name** for the repository.
85+
1. Optionally, enter a **Description**.
86+
1. Repeat for more repositories.
87+
1. Select **Save**.
88+
89+
**Checkpoint:** Selected repositories appear in the Knowledge Sources page.
90+
91+
## Troubleshooting
92+
93+
| Problem | Cause | Fix |
94+
|---------|-------|-----|
95+
| Identity dropdown is empty | Agent has no managed identity enabled | Enable a system-assigned identity or attach a user-assigned identity in the Azure portal |
96+
| **Connect** button fails | Organization name is missing | Enter the ADO organization name before connecting |
97+
| Repos don't load after connecting | MI doesn't have access to the ADO organization | Add the MI service principal as a user in ADO Organization Settings > Users |
98+
| FIC connection fails | FederatedClientId and FederatedTenantId not both provided | Both fields are required when using FIC. Provide both or neither |
99+
100+
## Related content
101+
102+
- [Managed identity for ADO repos](managed-identity-ado-repos.md)
103+
- [Connect knowledge sources](connect-knowledge.md)
104+
- [Set up Azure DevOps connector](azure-devops-connector.md)

0 commit comments

Comments
 (0)