Merge pull request #300047 from msangapu-msft/routine-maintenance

updates

Author: prmerger-automator[bot]

articles/app-service/routine-maintenance.md

@@ -5,24 +5,27 @@ author: msangapu-msft
 tags: app-service
 
 ms.topic: article
-ms.date: 04/29/2025
+ms.date: 05/19/2025
 ms.author: msangapu
+ms.collection: ce-skilling-ai-copilot
 ---
 
 # Routine planned maintenance for Azure App Service
 
-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.
+Routine maintenance includes behind-the-scenes updates to Azure App Service. These updates may include performance improvements, bug fixes, new features, or security updates. Maintenance can apply to the App Service platform or the underlying operating system.
 
 > [!IMPORTANT]
-> A breaking change or deprecation of functionality isn't a part of routine maintenance. For more information, see [Modern Lifecycle Policy](/lifecycle/policies/modern).
+> A breaking change or deprecation of functionality isn't part of routine maintenance. For more information, see [Modern Lifecycle Policy](/lifecycle/policies/modern).
 
-Microsoft service quality and uptime guarantees continue to apply during maintenance periods. Notifications mention maintenance periods to help customers get visibility into platform changes.
+Microsoft's service quality and uptime guarantees continue to apply during maintenance periods. Notifications are provided to give customers visibility into platform changes.
 
 ## What to expect
 
-Like personal computers, mobile phones, and other devices, machines in the cloud need the latest updates. Unlike physical devices, cloud solutions like Azure App Service provide ways to handle routine maintenance with more ease. There's no need to stop working and wait until patches are installed. Any workload can be shifted to different hardware in a matter of seconds and while updates are installed. The updates happen monthly but can vary, depending on your organization's needs and other factors.
+Like personal computers, mobile phones, and other devices, machines in the cloud need regular updates. Unlike physical devices, Azure App Service handles routine maintenance with minimal disruption. Workloads can be shifted to updated hardware in seconds, allowing updates to proceed without downtime.
 
-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).
+Maintenance typically occurs monthly but may vary depending on your organization's needs and other factors.
+
+Because a typical cloud solution consists of multiple applications, databases, storage accounts, functions, and other resources, parts of your solution may undergo maintenance at different times. This variation can be due to geography, region, datacenters, and availability zones. For more information, see [Safe deployment practices](/devops/operate/safe-deployment-practices).
 
 To find maintenance events, search for **Service Health** in the Azure portal. Under **Active Events**, select **Planned maintenance**.
 
@@ -50,16 +53,15 @@ This example shows:
 - The state of the maintenance, which can be pending, started, or completed.
 - Once maintenance starts, timestamps can be viewed under **More info**.
 
-
 ## Frequently asked questions
 
 ### Why is the maintenance taking so long?
 
-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.
+Routine maintenance delivers the latest updates to the platform and service. It's difficult to predict how maintenance affects individual apps, so notifications provide general time ranges. These ranges reflect the overall operation across all resources, not specific app-level experiences. Apps that undergo maintenance restart on freshly updated machines and continue working. There's no downtime when requests and traffic aren't served.
 
 ### Why am I getting so many notifications?
 
-A typical scenario is that customers have multiple applications that are upgraded at different times. To avoid sending notifications for each of them, we send one notification that captures multiple resources. We send the notification at the beginning and throughout the maintenance window. You might receive multiple reminders for the same rollout if the time window is long, so you can more easily correlate any restarts, interruptions, or other issues.
+Customers often have multiple applications that are upgraded at different times. To avoid sending notifications for each of them, we send one notification that captures multiple resources. We send the notification at the beginning and throughout the maintenance window. You might receive multiple reminders for the same rollout if the time window is long, so you can more easily correlate any restarts, interruptions, or other issues.
 
 ### How is routine maintenance related to SLA?
 
@@ -71,13 +73,13 @@ We don't expect sites to incur any service-level agreement (SLA) violations duri
 
 ### How does the upgrade ensure the smooth operation of my apps?
 
-Azure App Service represents a fleet of scale units that provide hosting of web applications and solutions to customers. Each scale unit is divided into upgrade domains and availability zones. This division optimizes placements of bigger App Service plans and smooth deployments, because not all machines in each scale unit are updated at once.
+Azure App Service represents a fleet of scale units that provide hosting of web applications and solutions to customers. Each scale unit is divided into upgrade domains and availability zones. This division optimizes placement of larger App Service plans and enables smooth deployments, because not all machines in each scale unit are updated at once.
 
 Maintenance operations upgrade machines iteratively while App Service monitors the health of the fleet. If there's a problem, the system can stop the rollout. For more information about this process, see the blog post [Demystifying the magic behind App Service OS updates](https://azure.github.io/AppService/2018/01/18/Demystifying-the-magic-behind-App-Service-OS-updates.html).
 
 ### Are business hours reflected?
 
-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.
+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 is designed to minimize disruption during business hours. If any upgrades are still in progress by 9 AM in a given region, they will attempt to pause before reaching critical phases. Some underlying instance movements may continue, but they are orchestrated to overlap safely and maintain site availability.
 
 ### What are my options to control routine maintenance?
 
@@ -91,7 +93,7 @@ You can use health check to inform the platform that your application isn't read
 
 ### My applications have been online, but things are worse since these notifications started showing up. What changed?
 
-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.
+Updates and maintenance events have been happening to the platform since its inception. The frequency of updates has decreased over time, so the number of interruptions has also decreased and uptime has increased. However, you now have more visibility into all changes. Increased visibility might cause the perception that more changes are happening.
 
 ## Related content