You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Add web page knowledge sources in Azure SRE Agent
14
14
15
-
Add any publicly accessible web page by URL—your agent fetches and indexes the content automatically so it can reference external documentation, status pages, and wiki articles during investigations.
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
16
17
17
> [!TIP]
18
-
> - Add any publicly accessible web page by URL—your agent fetches and indexes the content automatically
19
-
> - Reference external documentation, status pages, runbook sites, and wiki articles during investigations
20
-
> - One-step setup: provide a URL, name, and optional description
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
21
22
22
## The problem: external docs stay external
23
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.
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
25
26
26
That manual process is tedious and creates stale copies. The original page gets updated, but the uploaded file doesn't.
27
27
@@ -30,42 +30,42 @@ That manual process is tedious and creates stale copies. The original page gets
30
30
When you add a web page as a knowledge source, the agent fetches the page content and stores it for reference:
31
31
32
32
1. You provide a URL, a name, and an optional description.
33
-
2. The agent fetches the page content via an anonymous HTTP request.
34
-
3. The page content is stored and indexed.
35
-
4. Your agent can reference this content during conversations and investigations.
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
36
37
-
The fetch happens at the time you add the URL. Content is stored as a point-in-time snapshot of the page.
37
+
The fetch happens when you add the URL. Content is stored as a point-in-time snapshot of the page.
38
38
39
-
The agent fetches pages anonymously—without authentication credentials. Pages that require login, VPN access, or corporate SSO can't be indexed. If you need to add content from protected pages, copy the content and[upload it as a file](upload-knowledge-document.md) instead.
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
40
41
41
## What gets indexed
42
42
43
43
| Aspect | Behavior |
44
44
|--------|----------|
45
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 sent with the request |
46
+
|**Link following**| No. Only the specified URL is fetched, not linked pages |
47
+
|**Authentication**| Anonymous. No credentials are sent with the request |
48
48
|**Supported protocols**| HTTP and HTTPS |
49
49
|**Fetch timeout**| 30 seconds |
50
-
|**Refresh**| Manual—delete and re-add the URL to get updated content |
50
+
|**Refresh**| Manual. Delete and re-add the URL to get updated content |
51
51
52
52
## When to use web page knowledge
53
53
54
54
Web page knowledge sources work best for:
55
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
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
61
62
62
For internal or protected content that requires authentication, use [file uploads](upload-knowledge-document.md) instead.
# Tutorial: Add a web page knowledge source in Azure SRE Agent
14
14
15
-
Add a public URL as a knowledge source that your agent references during investigations. You'll add the URL, verify it appears in the knowledge base, and confirm your agent can use the content.
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
16
17
17
**Time**: ~5 minutes
18
18
19
19
## Prerequisites
20
20
21
21
- An Azure SRE Agent in **Running** state
22
22
-**Write** permissions on the agent (AgentMemoryWrite)
23
-
- A publicly accessible web page URL (any page that loads in a browser without login)
23
+
- A publicly accessible web page URL (any page that loads in a browser without authentication)
24
24
25
25
## Step 1: Open Knowledge Sources
26
26
27
27
1. Go to [sre.azure.com](https://sre.azure.com) and select your agent.
28
-
2. In the left sidebar, select **Builder**.
29
-
3. Select **Knowledge Sources**.
28
+
1. In the left sidebar, select **Builder**.
29
+
1. Select **Knowledge Sources**.
30
30
31
-
You'll see the Knowledge Sources page with three action cards: **Add file**, **Add web page**, and **Add repository**.
31
+
You see the Knowledge Sources page with three action cards: **Add file**, **Add web page**, and **Add repository**.
32
32
33
33
## Step 2: Open the Add Web Page dialog
34
34
35
35
Select the **Add web page** card (the one with the globe icon).
36
36
37
37
A dialog opens with three fields:
38
-
-**Web page URL** (required)—the URL to fetch
39
-
-**Name** (required)—a display name for this knowledge source
40
-
-**Description** (optional)—a brief description of what the page contains
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
41
42
42
43
## Step 3: Enter the web page details
43
44
44
-
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`
45
-
2.**Name**—enter a descriptive name, such as `Azure Monitor Overview`.
46
-
3.**Description**—optionally describe the content.
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.
47
48
48
49
> [!NOTE]
49
50
> The URL must be an absolute URL (starting with `http://` or `https://`), publicly accessible, and reachable within 30 seconds.
50
51
51
52
## Step 4: Add the web page
52
53
53
-
Select the **Add web page** button.
54
+
Select **Add web page**.
54
55
55
56
The agent fetches the page content. If successful, a notification confirms the web page was added and the dialog closes automatically.
56
57
@@ -66,17 +67,17 @@ Common errors:
66
67
67
68
## Step 5: Verify the knowledge source
68
69
69
-
After adding the web page, it appears in the Knowledge Sources list. Verify:
70
+
After adding the web page, it appears in the Knowledge Sources list. Verify the following values:
70
71
71
-
-**Name**—the display name you provided
72
-
-**Type**—shows as **Web page**
73
-
-**Status**—indicates whether the content was indexed
72
+
-**Name**: the display name you provided
73
+
-**Type**: shows as **Web page**
74
+
-**Status**: indicates whether the content was indexed
74
75
75
76
## Step 6: Test with your agent
76
77
77
-
1.Navigate to **Chats** in the left sidebar.
78
-
2. Start a new conversation.
79
-
3. Ask a question related to the web page content.
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.
80
81
81
82
Your agent should reference information from the web page in its response.
82
83
@@ -85,9 +86,9 @@ Your agent should reference information from the web page in its response.
85
86
Web page knowledge sources are point-in-time snapshots. To refresh the content:
# Remove resources from agent scope in Azure SRE Agent
14
14
15
-
Select and remove configured resources directly from the agent configuration overview—no setup wizard needed. Works for code repositories, log connectors, deployment connectors, Azure subscriptions, and resource groups.
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
16
17
17
> [!TIP]
18
18
> - Select and remove configured resources directly from the agent configuration overview
@@ -34,24 +34,24 @@ Each resource grid in the configuration overview includes checkboxes for selecti
34
34
35
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
36
37
-
2.**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.
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
38
39
-
3.**Select Delete.** A **Delete** button with a trash icon appears next to the category header when items are selected. A confirmation dialog titled **Remove from scope** appears, warning that permissions on those resources will be revoked. Select **Remove** to confirm or **Cancel** to keep the resources.
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
40
41
-
4.**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.
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
42
43
43
### What you can remove
44
44
45
45
| Resource type | What happens on removal |
46
46
|--------------|------------------------|
47
-
| Code repositories | Repository is disconnected from the agent's knowledge graph |
47
+
| Code repositories | Repository disconnects from the agent's knowledge graph |
48
48
| Log connectors | Agent loses access to log querying tools for that connector |
49
49
| Deployment connectors | Agent loses access to deployment history from that connector |
| Resource groups | Resource group removed from monitored scope; managed identity permissions revoked |
52
52
53
53
> [!WARNING]
54
-
> Removal can't be undone. To restore a removed resource, re-add it through the setup wizard. Knowledge files can't be removed from the configuration overview—use the full setup wizard to manage them.
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.
# Tutorial: Connect an ADO repository with managed identity in Azure SRE Agent
14
14
15
-
Connect an Azure DevOps repository to your agent using managed identity—no PATs to create or rotate. Your agent uses its own Azure identity to access ADO repos for code-aware investigations.
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
16
17
17
**Time**: ~10 minutes (including ADO admin setup)
18
18
@@ -28,42 +28,42 @@ Connect an Azure DevOps repository to your agent using managed identity—no PAT
28
28
Before connecting from the agent portal, your managed identity must have access to the Azure DevOps organization.
29
29
30
30
1. Go to your [Azure DevOps organization settings](https://dev.azure.com/) and select your organization.
31
-
2. Navigate to **Organization settings** > **Users**.
32
-
3. Select **Add users**.
33
-
4. Search for your agent's managed identity by its service principal name or object ID.
34
-
5. Set the access level to **Basic** (or higher).
35
-
6. Add the identity to projects with **Code (Read)** permissions on the target repositories.
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
36
37
37
**Checkpoint:** The managed identity appears in the ADO Users list with a Basic access level.
38
38
39
-
## Step 2: Navigate to Knowledge sources
39
+
## Step 2: Go to Knowledge sources
40
40
41
41
1. Open your agent in the [Azure SRE Agent portal](https://sre.azure.com).
42
-
2. In the left sidebar, expand **Builder**.
43
-
3. Select **Knowledge sources**.
42
+
1. In the left sidebar, expand **Builder**.
43
+
1. Select **Knowledge sources**.
44
44
45
-
**Checkpoint:** The Knowledge Sources page loads showing any existing repository connections.
45
+
**Checkpoint:** The Knowledge Sources page loads and shows any existing repository connections.
**Checkpoint:** The Add repositories dialog opens and shows platform selection cards, such as GitHub and Azure DevOps.
52
52
53
53
## Step 4: Select Azure DevOps with Managed Identity
54
54
55
55
1. Select the **Azure DevOps** platform card.
56
-
2. Under **Sign In Methods**, select **Managed Identity**.
56
+
1. Under **Sign In Methods**, select **Managed Identity**.
57
57
58
58
**Checkpoint:** The managed identity configuration form appears with an organization field and identity dropdown.
59
59
60
60
## Step 5: Configure the managed identity connection
61
61
62
-
1. Enter your Azure DevOps **Organization** name—the part after `dev.azure.com/` in your ADO URL.
63
-
2. 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
-
3. Select **Connect**.
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
67
68
68
**Checkpoint:** The button changes to **Connected** with a checkmark.
69
69
@@ -79,12 +79,12 @@ Select **Next** to proceed to the repository selection step.
79
79
## Step 7: Select a project and add repositories
80
80
81
81
1. From the **Azure DevOps Project** dropdown, select the project containing your repositories.
82
-
2. Select **Add** to add a repository row.
83
-
3. From the **Repository** dropdown, select a repository from the project.
84
-
4. Enter a **Display name** for the repository.
85
-
5. Optionally enter a **Description**.
86
-
6. Repeat for more repositories.
87
-
7. Select **Save**.
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
88
89
89
**Checkpoint:** Selected repositories appear in the Knowledge Sources page.
90
90
@@ -95,7 +95,7 @@ Select **Next** to proceed to the repository selection step.
95
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
96
|**Connect** button fails | Organization name is missing | Enter the ADO organization name before connecting |
97
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 |
98
+
| FIC connection fails | FederatedClientId and FederatedTenantId not both provided | Both fields are required when using FIC. Provide both or neither |
0 commit comments