Skip to content

Commit 17598ed

Browse files
committed
pm-article
1 parent c7ac570 commit 17598ed

File tree

4 files changed

+61
-0
lines changed

4 files changed

+61
-0
lines changed
Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
title: Resource impact from Azure security incidents
3+
description: This article details where to find information from Azure Service Health about how Azure Planned Maintenance impact your resources.
4+
ms.topic: conceptual
5+
ms.date: 9/29/2023
6+
---
7+
8+
# Impacted Resources for Planned Maintenance events
9+
10+
In support of the experience for viewing Impacted Resources, Service Health has enabled a new feature to:
11+
12+
- Display resources that are impacted by a planned maintenance event.
13+
- Provide impacted resources information for planned maintenance via the Service Health Portal.
14+
15+
This article details what is communicated to users and where they can view information about their impacted resources.
16+
17+
>[!Note]
18+
>This feature will be rolled out in phases. Initially, impacted resources will only be shown for **SQL resources with advance customer notifications and rebootful updates for compute resources.** Planned maintenance impacted resources coverage will be expanded to other resource types and scenarios in the future.
19+
20+
## Viewing Impacted Resources for Planned Maintenance Events on the Service Health Portal
21+
22+
In the Azure portal, the **Impacted Resources** tab under **Service Health** > **Planned Maintenance** displays resources that are affected by a planned maintenance event. The following example of the Impacted Resources tab shows a planned maintenance event with impacted resources.
23+
24+
:::image type="content" source="./media/impacted-resource-pm/ir-grid-pm.PNG" alt-text="Screenshot of planned maintenance impacted resources in Azure Service Health.":::
25+
26+
Service Health provides the information below on resources impacted by a planned maintenance event:
27+
28+
|Fields |Description |
29+
|---------|---------|
30+
|**Resource Name**|Name of the resource impacted by the planned maintenance event|
31+
|**Resource Type**|Type of resource impacted by the planned maintenance event|
32+
|**Resource Group**|Resource group which contains the impacted resource|
33+
|**Region**|Region which contains the impacted resource|
34+
|**Subscription ID**|Unique ID for the subscription that contains the impacted resource|
35+
|**Action(*)**|Link to the apply update page during Self-Service window (only for rebootful updates on compute resources)|
36+
|**Self-serve Maintenance Due Date(*)**|Unique ID for the subscription that contains the impacted resource.|
37+
38+
>[!Note]
39+
>Fields with an asterisk * are optional fields that are available depending on the resource type.
40+
41+
42+
43+
## Filters
44+
45+
Customers can filter on the results using the below filters
46+
- Region
47+
- Subscription ID: All Subscription IDs the user has access to
48+
- Resource Type: All Resource types under the users subscriptions
49+
50+
:::image type="content" source="./media/impacted-resource-pm/pm-filters.PNG" alt-text="Screenshot of filters used to sort impacted resources":::
51+
52+
## Export to CSV
53+
54+
The list of impacted resources can be exported to an excel file by clicking on this option.
55+
56+
:::image type="content" source="./media/impacted-resource-pm/ir-csv.PNG" alt-text="Screenshot of export to csv button":::
57+
58+
## Next steps
59+
- [Introduction to the Azure Service Health dashboard](service-health-overview.md)
60+
- [Introduction to Azure Resource Health](resource-health-overview.md)
61+
- [Frequently asked questions about Azure Resource Health](resource-health-faq.yml)
435 KB
Loading
62.1 KB
Loading
427 KB
Loading

0 commit comments

Comments
 (0)