Merge pull request #314342 from dm-chelupati/docs-agent/learn-2026-03-25

denrea · web-flow · commit 53e6f08dff9c · 2026-04-07T09:58:52.000-07:00
[Docs] SRE Agent Learn update — 2026-03-25
diff --git a/articles/sre-agent/automate-actions.md b/articles/sre-agent/automate-actions.md
@@ -40,7 +40,7 @@ First, connect an external tool. You need the connector before you can assign it
 1. Select **Builder** in the left sidebar.
 1. Select **Connectors**.
 1. Select **Add connector**.
-1. Select **Send email (Office 365 Outlook)**.
+1. Select the **Notification** tab, then select **Send email (Office 365 Outlook)**.
 1. Sign in with your Microsoft account.
 1. Select **Add connector**.
 
@@ -100,7 +100,7 @@ The canvas now shows the complete workflow: scheduled task to subagent to tool.
 
 Test your scheduled task to confirm everything works together.
 
-1. Select **Builder** > **Scheduled tasks**.
+1. Select **Scheduled tasks** in the left sidebar.
 1. Select your task in the list (check the checkbox).
 1. Select **Run task now** in the toolbar.
 1. Select the chat thread that opens to see execution details.
diff --git a/articles/sre-agent/automate-workflows.md b/articles/sre-agent/automate-workflows.md
@@ -51,7 +51,7 @@ Connectors let the agent interact with external services. Start with a notificat
 
 1. Go to **Builder** > **Connectors** in the left sidebar.
 1. Select **Add connector**.
-1. Select **Send email (Office 365 Outlook)**.
+1. Select the **Notification** tab, then select **Send email (Office 365 Outlook)**.
 1. Sign in and authorize access.
 1. Select **Next**.
 1. Select a **Managed identity**. The agent uses this identity at runtime to securely access the connector. Use a **User assigned** managed identity so you can reuse it across connectors and manage its lifecycle independently.
@@ -105,7 +105,7 @@ Link a scheduled task to the subagent so it runs automatically.
     | **Task name** | `daily-health-report` |
     | **Task details** | Check the health of the resources in my resource group. Verify all apps are running, check CPU, and memory metrics over the last hour, review any recent warning logs. Summarize findings and send the report. |
     | **Frequency** | Daily |
-    | **Time of day** | 8:00 AM |
+    | **Time of day** | 8:00 AM (label shows your local timezone) |
 
 1. Select **Create task**.
 
@@ -119,7 +119,7 @@ The canvas now shows the complete workflow chain visually.
 
 Run the task immediately to verify everything works.
 
-1. Go to **Builder** > **Scheduled tasks**.
+1. Go to **Scheduled tasks** in the left sidebar.
 1. Select your task by checking the checkbox.
 1. Select **Run task now** in the toolbar.
 1. To watch execution, select the **task name** to open the executions view, and then select the **thread name** link. You can also find the thread under **Chats** in the sidebar.
diff --git a/articles/sre-agent/connect-knowledge.md b/articles/sre-agent/connect-knowledge.md
@@ -43,7 +43,7 @@ The following table describes the three types of knowledge sources.
 |---|---|---|
 | **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 of the given URL. |
-| **Repositories** | Source code for root cause analysis, deployment configs, infrastructure-as-code | Connect GitHub or Azure Repos |
+| **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.
 
@@ -75,9 +75,30 @@ The following table compares uploading knowledge documents and sharing files in
 
 ## Connect source code
 
-Connect your GitHub or Azure DevOps repositories so your agent can read code, search for errors, and correlate deployments with incidents. The knowledge base displays repositories with clone and indexing status.
+Connect GitHub or Azure DevOps repositories so your agent can search code, correlate errors with recent changes, and reference deployment configurations during investigations.
 
-- To connect a GitHub repository, see [Connect source code](connect-source-code.md).
+### Add repositories
+
+From **Builder** > **Knowledge base**, select **Add repository** to open a guided wizard that walks you through three steps:
+
+| Step | What you do |
+|------|------------|
+| **1. Choose a platform** | Select **GitHub** or **Azure DevOps**. For Azure DevOps, enter your organization name. |
+| **2. Authenticate** | Sign in with OAuth or enter a personal access token (PAT). Azure DevOps also supports managed identity. |
+| **3. Add repositories** | Browse available repos from the dropdown or enter URLs manually. Add a display name and optional description for each entry. For Azure DevOps, select a project first to filter the repo list. |
+
+You can add multiple repositories in a single session. Select **+** to add rows, then select **Save** when done.
+
+After saving, your repositories appear in the knowledge base list with indexing status. Once indexed, your agent can reference the code in conversations.
+
+### Supported platforms and authentication
+
+| Platform | Auth methods | What you need |
+|----------|-------------|--------------|
+| **GitHub** | OAuth, Personal access token | GitHub account with repo access. For PAT, create a token with `repo` scope. |
+| **Azure DevOps** | OAuth, Personal access token, Managed identity | Azure DevOps organization access. For managed identity, assign a user-assigned managed identity to the agent resource. |
+
+- To learn more about connecting GitHub repositories, see [Connect source code](connect-source-code.md).
 - To connect an Azure DevOps repository, see [Set up an Azure DevOps connector](azure-devops-connector.md).
 
 ## Next step
diff --git a/articles/sre-agent/connect-source-code.md b/articles/sre-agent/connect-source-code.md
@@ -50,7 +50,7 @@ Connect a GitHub or Azure DevOps repository so your agent indexes it as a knowle
 
 During onboarding, select the **Add repository** card in the Knowledge Base step.
 
-For an existing agent, go to **Builder** > **Knowledge settings** and select the **Add repository** action card.
+For an existing agent, go to **Builder** > **Knowledge base** and select the **Add repository** action card.
 
 ### Step 2: Choose a platform
 
@@ -95,6 +95,19 @@ Select **Add repository** to save your changes.
 
 The system automatically creates the appropriate GitHub OAuth or Azure DevOps OAuth connector if one doesn't already exist.
 
+### Step 5: Try creating a pull request (preview)
+
+With your repository connected, your agent can now create pull requests directly from chat.
+
+1. Open a chat thread with your agent.
+1. Type a prompt like: *"Create a PR in https://github.com/OWNER/REPO from fix/my-branch to main titled 'Fix connection timeout'"*.
+1. In Review mode, select **Continue** to approve the PR creation.
+
+Your agent returns a tool card with a clickable link to the created PR.
+
+> [!NOTE]
+> Create pull requests requires Review or Autonomous run mode. The source branch must already exist with your changes committed.
+
 ## Manage connected repositories
 
 When you reopen the Add Repository dialog, existing connected repositories appear as read-only rows in the grid.
@@ -103,7 +116,7 @@ When you reopen the Add Repository dialog, existing connected repositories appea
 
 Use the following steps to remove a connected repository.
 
-1. Go to **Builder** > **Knowledge settings** and select the **Add repository** action card.
+1. Go to **Builder** > **Knowledge base** and select the **Add repository** action card.
 1. Find the repository row in the grid.
 1. Select the **trash icon** on the row to mark it for deletion.
 1. Select **Add repository** to save changes.
@@ -122,7 +135,7 @@ This approach uses the Model Context Protocol (MCP) to connect GitHub tools to a
 
 ## Summary
 
-Your agent now analyzes source code during investigations, provides file and line references for problems, creates To-do Plans showing investigation steps, and correlates production symptoms to code changes.
+Your agent now analyzes source code during investigations, provides file and line references for problems, creates To-do Plans showing investigation steps, correlates production symptoms to code changes, and can create pull requests in connected repos directly from chat.
 
 ## Next step
 
diff --git a/articles/sre-agent/create-and-set-up.md b/articles/sre-agent/create-and-set-up.md
@@ -140,6 +140,9 @@ Granting the agent Reader access to your Azure resources allows it to query metr
 
 **Checkpoint:** The Azure Resources card shows the connected subscriptions or resource groups.
 
+> [!TIP]
+> The subscription picker shows **all** your subscriptions in two sections: those you can assign (where you have Owner or User Access Administrator) and those that require a higher role. A **User role** column displays your current role on each subscription. If you use **Privileged Identity Management (PIM)** for just-in-time access, the picker detects your active PIM role within seconds—no need to wait for cache refreshes.
+
 > [!NOTE]
 > After you add subscriptions or resource groups, the agent automatically assigns the required permissions to its managed identity. This can take a few seconds—you'll see the status update on the permissions review step. Reader role provides read-only access. For advanced permission management, see [Manage permissions and access](manage-permissions.md).
 
diff --git a/articles/sre-agent/create-scheduled-task.md b/articles/sre-agent/create-scheduled-task.md
@@ -33,7 +33,7 @@ In this tutorial, you:
 
 Follow these steps to create a new scheduled task from the portal.
 
-1. Go to your agent, and select **Builder** > **Scheduled tasks**.
+1. Go to your agent, and select **Scheduled tasks** in the left sidebar.
 
     :::image type="content" source="media/common/portal-scheduled-tasks.png" alt-text="Screenshot of scheduled tasks dashboard showing task list and toolbar.":::
 
@@ -46,7 +46,7 @@ Follow these steps to create a new scheduled task from the portal.
     | **Task name** | Daily Health Check |
     | **Task details** | Check Azure Resource Health for all resources in prod-rg. Summarize healthy, warning, and critical counts. |
     | **Frequency** | Daily |
-    | **Time of day** | 9:00 AM |
+    | **Time of day (*timezone*)** | 9:00 AM |
 
     Don't change the default values for optional fields:
 
@@ -84,7 +84,7 @@ To change the schedule, update instructions, or switch the agent mode, edit the
 
     | What to change | Field to update |
     |----------------|-----------------|
-    | When it runs | **Frequency** and **Time of day** |
+    | When it runs | **Frequency** and **Time of day (*timezone*)** |
     | What it does | **Task details** |
     | Who handles it | **Response subagent** |
     | How long it runs | **Repeat until** or **Run limit** |
diff --git a/articles/sre-agent/scheduled-tasks.md b/articles/sre-agent/scheduled-tasks.md
@@ -3,7 +3,7 @@ title: Schedule tasks with Azure SRE Agent
 description: Learn how to use scheduled tasks in SRE Agent to automate monitoring, enforce security, and validate recovery.
 author: craigshoemaker
 ms.topic: overview
-ms.date: 03/18/2026
+ms.date: 03/25/2026
 ms.author: cshoe
 ms.service: azure-sre-agent
 ---
diff --git a/articles/sre-agent/track-incident-value.md b/articles/sre-agent/track-incident-value.md
diff --git a/articles/sre-agent/workflow-automation.md b/articles/sre-agent/workflow-automation.md
