Skip to content

Commit 64e02f5

Browse files
authored
Merge pull request #126250 from jammul1/main
Added updated Service Health images
2 parents 13f2bf4 + 2697286 commit 64e02f5

File tree

3 files changed

+18
-1
lines changed

3 files changed

+18
-1
lines changed
68.1 KB
Loading
77 KB
Loading

articles/app-service/routine-maintenance.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Like personal computers, mobile phones, and other devices, machines in the cloud
2424

2525
Because a typical cloud solution consists of multiple applications, databases, storage accounts, functions, and other resources, parts of your solutions can undergo maintenance at different times. Some of this coordination is related to geography, region, datacenters, and availability zones. It can also be due to the cloud, where not everything is touched simultaneously. For more information, see [Safe deployment practices](/devops/operate/safe-deployment-practices).
2626

27-
The following screenshot shows an example of a maintenance event.
27+
The following screenshot shows an example of a maintenance event:
2828

2929
:::image type="content" source="./media/routine-maintenance/routine-maintenance.png" alt-text="Screenshot of a maintenance event in the Azure portal.":::
3030

@@ -34,6 +34,23 @@ In order from top to bottom, the example shows:
3434
- Affected regions and subscriptions.
3535
- The expected maintenance window.
3636

37+
The following screenshots show additional information available through the Impacted Resources dropdown:
38+
39+
:::image type="content" source="./media/routine-maintenance/routine-maintenance-first-page.png" alt-text="Screenshot of the Impacted Resources blade in the Azure portal.":::
40+
41+
In order from left to right, the example shows:
42+
43+
- Selecting the "Impacted Resources" dropdown.
44+
- The "More info" option.
45+
46+
:::image type="content" source="./media/routine-maintenance/routine-maintenance-more.png" alt-text="Screenshot of more info for a maintenance event in the Azure portal.":::
47+
48+
This example shows:
49+
50+
- The state of the maintenance, which can be pending, started, or completed.
51+
- Once maintenance starts, timestamps can be viewed under "More info."
52+
53+
3754
## Frequently asked questions
3855

3956
### Why is the maintenance taking so long?

0 commit comments

Comments
 (0)