Skip to content

Commit 320752f

Browse files
committed
craig feedback
1 parent c894fd0 commit 320752f

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

articles/app-service/tutorial-sre-agent.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,7 @@ ms.date: 05/18/2025
1212
> [!NOTE]
1313
> Site Reliability Engineering (SRE) Agent is in preview. By using SRE Agent, you consent the product-specific terms on this page: [Preview Terms Of Use | Microsoft Azure](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
1414
15-
## Introduction
16-
17-
The Azure SRE (Site Reliability Engineering) Agent uses AI to monitor and manage your Azure resources, helping you quickly diagnose and fix issues.
15+
Site Reliability Engineering (SRE) focuses on creating reliable, scalable systems through automation and proactive management. An SRE Agent brings these principles to your cloud environment by providing AI-powered monitoring, troubleshooting, and remediation capabilities. An SRE Agent automates routine operational tasks and provides reasoned insights to help you maintain application reliability while reducing manual intervention. Available as a chatbot, you can ask questions and give natural language commands to maintain your applications and services. To ensure accuracy and control, any agent action taken on your behalf requires your approval.
1816

1917
This sample app demonstrates error detection by simulating HTTP 500 failures in a controlled way. You can safely test these scenarios using Azure App Service **deployment slots**, which let you run different app configurations side by side.
2018

@@ -27,7 +25,7 @@ In this tutorial, you will:
2725
> * Deploy a sample app from GitHub.
2826
> * Configure the app with a startup command and enable logging.
2927
> * Create a deployment slot to simulate failure.
30-
> * Set up an Azure SRE Agent (preview) to monitor the app.
28+
> * Set up an Azure SRE Agent to monitor the app.
3129
> * Trigger a failure by swapping to the broken slot.
3230
> * Use AI-driven chat to diagnose and resolve the issue by rolling back the swap.
3331
@@ -37,7 +35,7 @@ In this tutorial, you will:
3735

3836
To complete this tutorial, you need:
3937
- An [Azure subscription](https://azure.microsoft.com/free/).
40-
- Permissions to create role assignments (Role Based Access Control Administrator or User Access Administrator) for SRE Agent setup.
38+
- `Microsoft.Authorization/roleAssignments/write` permissions to create role assignments (Role Based Access Control Administrator or User Access Administrator) for SRE Agent setup.
4139

4240
## 1. Create an App Service app
4341

@@ -73,7 +71,11 @@ In the *Basics* tab, provide the following details:
7371

7472
1. Select the **Deployment** tab.
7573

76-
1. Under *Authentication settings*, enable **Basic authentication**. Basic authentication is used later for a one-time deployment from GitHub. [Disable Basic Auth](configure-basic-auth-disable.md?tabs=portal) in production.
74+
1. Under *Authentication settings*, enable **Basic authentication**.
75+
76+
> [!NOTE]
77+
> Basic authentication is used later for a one-time deployment from GitHub. [Disable Basic Auth](configure-basic-auth-disable.md?tabs=portal) in production.
78+
>
7779
7880
1. Select **Review and create**, then **Create** when validation passes.
7981

@@ -264,7 +266,7 @@ Now that the app is experiencing failures, use the SRE Agent to diagnose and res
264266
>
265267
> *“I will now perform mitigation for my-sre-app by swapping the slots back to recover the application to a healthy state. Please note that swapping slots back may not always immediately restore health. I will keep you updated on the progress.”*
266268
267-
1. After a short delay, the agent will prompt you to approve the rollback:
269+
1. After a pause, the agent prompts you to approve the rollback:
268270
269271
> *Performing Slot Swap rollback to Restore Application Availability for my-sre-app*
270272
> **[Approve]**   **[Deny]**

0 commit comments

Comments
 (0)