Skip to content

Commit 8623cda

Browse files
committed
date fix
1 parent 1add2b9 commit 8623cda

16 files changed

Lines changed: 442 additions & 0 deletions
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.guided-project-monitor-service-health-activity-alerts.introduction
3+
title: Introduction
4+
metadata:
5+
title: Introduction
6+
description: "Introduction"
7+
ms.date: 03/25/2026
8+
author: wwlpublish
9+
ms.author: robbarefoot
10+
ms.topic: unit
11+
ms.custom:
12+
- N/A
13+
durationInMinutes: 2
14+
content: |
15+
[!include[](includes/1-introduction.md)]
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.guided-project-monitor-service-health-activity-alerts.exercise-create-action-group
3+
title: Exercise - Create an action group
4+
metadata:
5+
title: Exercise - Create an action group
6+
description: "Exercise - Create an action group"
7+
ms.date: 03/25/2026
8+
author: wwlpublish
9+
ms.author: robbarefoot
10+
ms.topic: unit
11+
ms.custom:
12+
- N/A
13+
durationInMinutes: 7
14+
content: |
15+
[!include[](includes/2-exercise-create-action-group.md)]
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.guided-project-monitor-service-health-activity-alerts.exercise-create-service-health-alert
3+
title: Exercise - Create a Service Health alert
4+
metadata:
5+
title: Exercise - Create a Service Health alert
6+
description: "Exercise - Create a Service Health alert"
7+
ms.date: 03/25/2026
8+
author: wwlpublish
9+
ms.author: robbarefoot
10+
ms.topic: unit
11+
ms.custom:
12+
- N/A
13+
durationInMinutes: 7
14+
content: |
15+
[!include[](includes/3-exercise-create-service-health-alert.md)]
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.guided-project-monitor-service-health-activity-alerts.exercise-create-activity-log-alert
3+
title: Exercise - Create an Activity Log alert
4+
metadata:
5+
title: Exercise - Create an Activity Log alert
6+
description: "Exercise - Create an Activity Log alert"
7+
ms.date: 03/25/2026
8+
author: wwlpublish
9+
ms.author: robbarefoot
10+
ms.topic: unit
11+
ms.custom:
12+
- N/A
13+
durationInMinutes: 6
14+
content: |
15+
[!include[](includes/4-exercise-create-activity-log-alert.md)]
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.guided-project-monitor-service-health-activity-alerts.validate-success
3+
title: Validate success
4+
metadata:
5+
title: Validate success
6+
description: "Validate success"
7+
ms.date: 03/25/2026
8+
author: wwlpublish
9+
ms.author: robbarefoot
10+
ms.topic: unit
11+
ms.custom:
12+
- N/A
13+
durationInMinutes: 10
14+
content: |
15+
[!include[](includes/5-validate-success.md)]
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.guided-project-monitor-service-health-activity-alerts.clean-up-resources
3+
title: Clean up resources
4+
metadata:
5+
title: Clean up resources
6+
description: "Clean up resources"
7+
ms.date: 03/25/2026
8+
author: wwlpublish
9+
ms.author: robbarefoot
10+
ms.topic: unit
11+
ms.custom:
12+
- N/A
13+
durationInMinutes: 5
14+
content: |
15+
[!include[](includes/6-clean-up-resources.md)]
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.guided-project-monitor-service-health-activity-alerts.summary
3+
title: Summary
4+
metadata:
5+
title: Summary
6+
description: "Summary"
7+
ms.date: 03/25/2026
8+
author: wwlpublish
9+
ms.author: robbarefoot
10+
ms.topic: unit
11+
ms.custom:
12+
- N/A
13+
durationInMinutes: 2
14+
content: |
15+
[!include[](includes/7-summary.md)]
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
This guided project focuses on monitoring Azure using Service Health alerts, Activity Log alerts, and action groups.
2+
3+
Azure Monitor provides several alert types that notify you about issues without requiring paid compute resources. Service Health alerts watch for platform-level incidents and planned maintenance. Activity Log alerts fire when management operations — like resource deletion — occur. Action groups define who gets notified and how.
4+
5+
## Scenario
6+
7+
Your operations team wants to know immediately when Azure platform issues occur or when someone deletes a critical resource. You set up an action group with email notification, create a Service Health alert for platform incidents, and create an Activity Log alert for resource deletions. Together, these give the team proactive visibility into both platform and operational events.
8+
9+
- Exercise 1 - Create an action group and verify email delivery.
10+
- Exercise 2 - Create a Service Health alert for platform incidents.
11+
- Exercise 3 - Create an Activity Log alert for resource deletions.
12+
13+
:::image type="content" source="../media/overview-architecture.png" alt-text="Diagram showing the monitoring pipeline from Azure events through alert rules and action groups to email notifications." border="false":::
14+
15+
By the end of this project, you have a working notification pipeline that alerts your team about Azure service issues and unexpected infrastructure changes.
16+
17+
> [!NOTE]
18+
> This is a guided project module where you complete a project by following step-by-step instructions.
19+
20+
## Skilling areas
21+
22+
In this project, you practice skills in the following areas:
23+
24+
**Configure action groups**
25+
+ Create an action group with email notification.
26+
+ Test the action group to verify delivery.
27+
28+
**Create Service Health alerts**
29+
+ Navigate Azure Service Health.
30+
+ Configure an alert for service incidents and planned maintenance.
31+
+ Scope the alert to specific regions.
32+
33+
**Create Activity Log alerts**
34+
+ Configure an alert condition for resource deletion events.
35+
+ Attach an action group to an alert rule.
36+
+ Review alert rule configuration in the portal.
37+
38+
> [!IMPORTANT]
39+
> This project uses the Azure portal for every step. No prior Azure experience is required.
Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
This guided project consists of the following exercises:
2+
3+
- **Create an action group**
4+
- Create a Service Health alert
5+
- Create an Activity Log alert
6+
7+
In this exercise, you create an action group with email notification and send a test message to verify delivery. Action groups are the notification backbone for Azure alerts — you set them up once and reuse them across multiple alert rules.
8+
9+
This exercise includes the following tasks:
10+
11+
- Prepare the environment
12+
- Create the action group
13+
- Test the action group
14+
15+
**Outcome:** An action group configured to send email notifications when alerts fire.
16+
17+
> [!TIP]
18+
> Pause after each major action and confirm the page status before moving on. This habit prevents compounding mistakes.
19+
20+
## Task 1: Prepare the environment
21+
22+
Set up your Azure environment before you begin. You create a resource group to organize the monitoring resources for this project together.
23+
24+
> [!WARNING]
25+
> This project creates Azure resources that are free or near-free, but you should still complete the clean-up unit when you're done to avoid unintended expenses.
26+
27+
1. Sign in to the [Azure portal](https://portal.azure.com) with an account that has permissions to create monitoring resources.
28+
2. In the portal search bar, search for **Resource groups** and select **Resource groups**.
29+
3. Select **+ Create**. Name the resource group **rg-gp-monitoring-alerts**, choose your preferred region, and select **Review + create** then **Create**.
30+
4. Note the email address you want to use for alert notifications.
31+
32+
## Task 2: Create the action group
33+
34+
Create an action group that defines who gets notified and how. Action groups are reusable notification channels that you attach to alert rules, so the same team can be notified by multiple different alerts.
35+
36+
1. In the portal search bar, search for **Monitor** and select **Monitor**.
37+
2. In the left menu, select **Alerts**.
38+
3. Select **Action groups** from the top menu bar.
39+
4. Select **+ Create**.
40+
5. On the Basics tab, select **rg-gp-monitoring-alerts** as the resource group.
41+
6. For **Action group name**, enter **ag-gp-ops-email**.
42+
7. For **Display name**, enter **OpsEmail**.
43+
8. Select the **Notifications** tab.
44+
9. For **Notification type**, select **Email/SMS message/Push/Voice**.
45+
10. For **Name**, enter **ops-team-email**.
46+
11. In the panel that opens, check **Email** and enter your email address. Select **OK**.
47+
12. Select **Review + create** and then select **Create**.
48+
49+
> [!NOTE]
50+
> **Validation step:** Confirm the **ag-gp-ops-email** action group is created with email notification configured.
51+
52+
> [!NOTE]
53+
> Each exercise includes validation steps like this one. Track your results as you go — you'll review them all in the validation unit at the end of this module.
54+
55+
## Task 3: Test the action group
56+
57+
Send a test notification to verify the action group delivers email successfully. In production environments, you should always test notification channels before relying on them for incident response.
58+
59+
1. After the action group is created, select **ag-gp-ops-email** from the action groups list to open it.
60+
2. In the top menu bar, select **Test action group**.
61+
3. For **Select sample type**, choose **Service Health**.
62+
4. Make sure the **ops-team-email** notification is checked.
63+
5. Select **Test**.
64+
6. Wait for the test results to appear. Confirm the **Status** column shows **Success**.
65+
7. Check your email inbox for the test notification from Azure. Open the email and review its content — this is the same format you would receive during a real incident.
66+
67+
> [!NOTE]
68+
> **Validation step:** Confirm the test notification status shows **Success** and you received the email notification.
69+
70+
> [!NOTE]
Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
This guided project consists of the following exercises:
2+
3+
- Create an action group
4+
- **Create a Service Health alert**
5+
- Create an Activity Log alert
6+
7+
In this exercise, you create a Service Health alert that watches for platform incidents and planned maintenance in your regions. This free alert gives your team automatic visibility into Azure service issues that might affect your resources.
8+
9+
This exercise includes the following tasks:
10+
11+
- Navigate to Service Health
12+
- Create the alert rule
13+
14+
**Outcome:** A Service Health alert that notifies the operations team about Azure platform incidents and planned maintenance.
15+
16+
## Task 1: Navigate to Service Health
17+
18+
Open Azure Service Health, which tracks the status of Azure services across the regions you use. Service Health alerts notify you automatically when Azure platform issues might affect your resources.
19+
20+
1. In the portal search bar, search for **Service Health** and select **Service Health**.
21+
2. Select **Service issues** in the left menu. Review whether any active incidents are listed for your subscription. If none are active, that means all services are healthy in your regions.
22+
3. Select **Planned maintenance** and note any upcoming maintenance windows. These are the types of events your alert will notify you about.
23+
4. Select **Health advisories** to see any non-critical recommendations from Azure.
24+
5. Select **Health history** to view past incidents and their resolution timelines. This gives context for why proactive alerting matters.
25+
6. Select **Health alerts** in the left menu.
26+
27+
> [!NOTE]
28+
> **Validation step:** Confirm you reviewed all four Service Health tabs (Service issues, Planned maintenance, Health advisories, Health history).
29+
30+
## Task 2: Create the alert rule
31+
32+
Configure an alert that watches for service incidents and planned maintenance events in the regions you use. This is a free alert that requires no running compute resources.
33+
34+
1. Select **+ Create service health alert**.
35+
2. For **Subscription**, select your subscription.
36+
3. For **Service(s)**, leave the default to monitor all services, or select specific services you use.
37+
4. For **Region(s)**, select the region you used for the resource group (and any other regions you use).
38+
5. For **Event types**, check both **Service issue** and **Planned maintenance**.
39+
6. Select the **Actions** tab.
40+
7. Select **Select action groups** and choose **ag-gp-ops-email**.
41+
8. Select the **Details** tab.
42+
9. For **Resource group**, select **rg-gp-monitoring-alerts**.
43+
10. For **Alert rule name**, enter **ar-gp-service-health**.
44+
11. Make sure **Enable alert rule upon creation** is checked.
45+
12. Select **Create**.
46+
47+
> [!NOTE]
48+
> **Validation step:** Confirm the **ar-gp-service-health** alert rule is created and enabled.
49+
50+
> [!NOTE]

0 commit comments

Comments
 (0)