You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/routine-maintenance.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
1
---
2
-
title: Routine maintenance for Azure App Service
2
+
title: Routine Maintenance for Azure App Service
3
3
description: Learn more about routine, planned maintenance to help keep the App Service platform up to date and secure.
4
4
author: msangapu-msft
5
5
tags: app-service
6
6
7
7
ms.topic: article
8
-
ms.date: 02/08/2023
8
+
ms.date: 04/29/2025
9
9
ms.author: msangapu
10
10
---
11
11
12
-
# Routine (planned) maintenance for Azure App Service
12
+
# Routine planned maintenance for Azure App Service
13
13
14
-
Routine maintenance covers behind-the-scenes updates to Azure App Service. Types of maintenance can be performance improvements, bug fixes, new features, or security updates. App Service maintenance can be on the service itself or the underlying operating system.
14
+
Routine maintenance covers behind-the-scenes updates to Azure App Service. Types of maintenance can be performance improvements, bug fixes, new features, or security updates. App Service maintenance can be on the service itself or on the underlying operating system.
15
15
16
16
> [!IMPORTANT]
17
-
> A breaking change or deprecation of functionality is not a part of routine maintenance. For more information, see [Modern Lifecycle Policy](/lifecycle/policies/modern).
17
+
> A breaking change or deprecation of functionality isn't a part of routine maintenance. For more information, see [Modern Lifecycle Policy](/lifecycle/policies/modern).
18
18
19
19
Microsoft service quality and uptime guarantees continue to apply during maintenance periods. Notifications mention maintenance periods to help customers get visibility into platform changes.
20
20
@@ -24,38 +24,38 @@ Like personal computers, mobile phones, and other devices, machines in the cloud
24
24
25
25
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).
26
26
27
-
The following screenshot shows an example of a maintenance event:
27
+
To find maintenance events, search for **Service Health** in the Azure portal. Under **Active Events**, select **Planned maintenance**.
28
28
29
-
:::image type="content" source="./media/routine-maintenance/routine-maintenance.png" alt-text="Screenshot of a maintenance event in the Azure portal.":::
29
+
:::image type="content" source="media/routine-maintenance/routine-maintenance.png" alt-text="Screenshot of a maintenance event in the Azure portal." lightbox="media/routine-maintenance/routine-maintenance.png":::
30
30
31
-
In order from top to bottom, the example shows:
31
+
From top to bottom, the example shows:
32
32
33
33
- A descriptive title of the maintenance event.
34
34
- Affected regions and subscriptions.
35
35
- The expected maintenance window.
36
36
37
-
The following screenshots show additional information available through the Impacted Resources dropdown:
37
+
The following screenshots show additional information available through the **Impacted Resources** tab:
38
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.":::
39
+
:::image type="content" source="media/routine-maintenance/routine-maintenance-first-page.png" alt-text="Screenshot of the Impacted Resources section in the Azure portal." lightbox="media/routine-maintenance/routine-maintenance-first-page.png":::
40
40
41
-
In order from left to right, the example shows:
41
+
From left to right, the example shows:
42
42
43
-
- Selecting the "Impacted Resources" dropdown.
44
-
- The "More info" option.
43
+
- Selecting the **Impacted Resources** tab.
44
+
- The **More info** option.
45
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.":::
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." lightbox="media/routine-maintenance/routine-maintenance-more.png":::
47
47
48
48
This example shows:
49
49
50
50
- The state of the maintenance, which can be pending, started, or completed.
51
-
- Once maintenance starts, timestamps can be viewed under "More info."
51
+
- Once maintenance starts, timestamps can be viewed under **More info**.
52
52
53
53
54
54
## Frequently asked questions
55
55
56
56
### Why is the maintenance taking so long?
57
57
58
-
Fundamentally, routine maintenance delivers the latest updates to the platform and service. It's hard to predict how the maintenance will affect individual apps down to a specific time, so notifications tend to be more general. The time ranges in notifications don't reflect the experiences at the app level, but rather the overall operation across all resources. Apps that undergo maintenance instantly restart on freshly updated machines and continue working. There's no downtime when requests and traffic aren't served.
58
+
Fundamentally, routine maintenance delivers the latest updates to the platform and service. It's hard to predict how the maintenance affects individual apps down to a specific time, so notifications tend to be more general. The time ranges in notifications don't reflect the experiences at the app level, but rather the overall operation across all resources. Apps that undergo maintenance instantly restart on freshly updated machines and continue working. There's no downtime when requests and traffic aren't served.
59
59
60
60
### Why am I getting so many notifications?
61
61
@@ -77,7 +77,7 @@ Maintenance operations upgrade machines iteratively while App Service monitors t
77
77
78
78
### Are business hours reflected?
79
79
80
-
Yes, business hours are reflected for the time zone of the region. Maintenance operations are optimized to start outside the standard business hours of 9 AM to 5 PM. Statistically, that's the best time for any interruptions and restarts of workloads because there's less stress on the system (in customer applications and transitively on the platform itself). App Service maintenance makes a best effort to reduce maintenance operations during these business hours. If resources are still upgrading by 9 AM in a given region, the upgrade will continue until reaching a safe stopping point, pausing before the next critical step and until the end of business hours.
80
+
Yes, business hours are reflected for the time zone of the region. Maintenance operations are optimized to start outside the standard business hours of 9 AM to 5 PM. Statistically, that's the best time for any interruptions and restarts of workloads because there's less stress on the system (in customer applications and transitively on the platform itself). App Service maintenance makes a best effort to reduce maintenance operations during these business hours. If resources are still upgrading by 9 AM in a given region, the upgrade continues until reaching a safe stopping point, pausing before the next critical step and until the end of business hours.
81
81
82
82
### What are my options to control routine maintenance?
83
83
@@ -93,6 +93,6 @@ You can use health check to inform the platform that your application isn't read
93
93
94
94
Updates and maintenance events have been happening to the platform since its inception. The frequency of updates decreased over time, so the number of interruptions also decreased and uptime increased. However, you now have more visibility into all changes. Increased visibility might cause the perception that more changes are happening.
95
95
96
-
## Next steps
96
+
## Related content
97
97
98
-
Get more information about maintenance notifications by reading the blog post [Routine Planned Maintenance Notifications for Azure App Service](https://azure.github.io/AppService/2022/02/01/App-Service-Planned-Notification-Feature.html).
98
+
-[Routine Planned Maintenance Notifications for Azure App Service](https://azure.github.io/AppService/2022/02/01/App-Service-Planned-Notification-Feature.html)
0 commit comments