Merge pull request #309236 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-09 23:00 UTC

Author: learn-build-service-prod[bot]

articles/app-service/media/routine-maintenance/routine-maintenance.png

@@ -1,9 +1,9 @@
 ---
 title: "App Service WebJobs Overview"
-description: "An overview of Azure WebJobs, covering its types, supported platforms, file types, scheduling with NCRONTAB expressions, deployment options, and benefits for background processing within Azure App Service."
+description: Learn about Azure WebJobs, including types, supported platforms, file types, scheduling, deployment, and background processing in Azure App Service.
 keywords: "Azure WebJobs, App Service, background processing, triggered jobs, continuous jobs, NCRONTAB, deployment, Azure, technical overview"
 ms.topic: overview
-ms.date: 5/2/2025
+ms.date: 11/19/2025
 ms.update-cycle: 180-days
 author: msangapu-msft
 ms.author: msangapu
@@ -15,12 +15,13 @@ ms.service: azure-app-service
 
 # App Service WebJobs overview
 
-Azure WebJobs is a built-in feature of [Azure App Service](overview.md) that enables you to run background tasks, scripts, and programs alongside your web, API, or mobile applications. WebJobs simplify automation for common operations—such as data processing, image resizing, queue handling, or file cleanup—by running in the same scalable, managed environment as your application.
+Azure WebJobs is a built-in feature of [Azure App Service](overview.md) that enables you to run background tasks, scripts, and programs alongside your web, API, or mobile applications. WebJobs simplify automation for common operations by running in the same scalable, managed environment as your application. Common operations include  data processing, image resizing, queue handling, and file cleanup.
 
 ## Choosing WebJobs
 
 WebJobs are a good fit when:
-- You're already hosting your application on App Service.
+
+- You already host your application on App Service.
 - You want to deploy and manage background tasks together with your app.
 - You don't require a separate scaling model or event-based triggers beyond basic scheduling or queue polling.
 
@@ -41,7 +42,7 @@ WebJobs come in three main types:
 
 - **Triggered WebJobs**: Run on demand or in response to specific events. You can trigger them manually or from a service like Azure Storage.
 - **Scheduled WebJobs**: A specialized type of triggered WebJob that runs on a defined schedule using a `settings.job` file with [NCRONTAB expressions](webjobs-create.md#ncrontab-expressions).
-- **Continuous WebJobs**: Run persistently in the background while your App Service app is running. Ideal for queue polling or background monitoring tasks.
+- **Continuous WebJobs**: Run persistently in the background while your App Service app runs. Ideal for queue polling or background monitoring tasks.
 
 :::image type="content" border="false" source="media/overview-webjobs/webjob-types-app-service.png" alt-text="Diagram overview of WebJobs in Azure App Service, showing job types.":::
 
@@ -51,43 +52,43 @@ WebJobs come in three main types:
 
 You can deploy WebJobs using several methods:
 
-- **Azure portal or zip upload**: Manually upload your script or job files.
+- **The Azure portal** or **zip upload**: Manually upload your script or job files.
 - **Visual Studio**: Deploy directly with your ASP.NET app to Windows App Service.
-- **CI/CD pipelines**: Automate deployment with GitHub Actions, Azure DevOps, or Azure CLI.
+- **CI/CD pipelines**: Automate deployment with GitHub Actions, Azure Pipelines, or Azure CLI.
 - **ARM/Bicep templates**: Deploy infrastructure and jobs declaratively.
 
-WebJobs also provide **built-in logging** via Kudu and integration with App Service diagnostics to help you monitor job activity and troubleshoot issues.
+WebJobs also provide **built-in logging** by using Kudu and integration with App Service diagnostics to help you monitor job activity and troubleshoot issues.
 
 ## Scaling considerations
 
 WebJobs scale together with your App Service plan. If your app is configured to scale out to multiple instances, your WebJobs run on each instance as appropriate:
-- **Triggered WebJobs** will run on a single instance by default.
+
+- **Triggered WebJobs** runs on a single instance by default.
 - **Continuous WebJobs** can be configured to run on all instances or a single one using the `WEBJOBS_RUN_ONCE` setting.
 
-If you need independently scalable or event-driven execution, [Azure Functions](../azure-functions/functions-overview.md) may be more appropriate.
+If you need independently scalable or event-driven execution, [Azure Functions](../azure-functions/functions-overview.md) might be more appropriate.
 
 ## Best practices
 
 - Use **triggered** WebJobs for improvised or scheduled operations.
-- Use **continuous** WebJobs only when the task needs to run constantly (e.g., polling a queue).
-- Implement **retry logic and error handling** within your scripts.
+- Use **continuous** WebJobs only when the task needs to run constantly, such as polling a queue.
+- Implement **retry logic** and **error handling** in your scripts.
 - Use **application logging** and **Kudu logs** to monitor job behavior.
 - Keep job logic **separate from main app logic** when possible.
-- Use **storage-based triggers** (e.g., Azure Queues) for reliable, decoupled communication.
-
+- Use **storage-based triggers**, such as Azure Queues, for reliable, decoupled communication.
 
 ## Choose your scenario
 
 | Goal | Article |
 |------|---------|
-| Quickly run a scheduled WebJob | [Quickstart: Create a scheduled WebJob](quickstart-webjobs.md) |
+| Quickly run a scheduled WebJob | [Create a scheduled WebJob](quickstart-webjobs.md) |
 | Build a WebJob manually using scripts or code | [Create a WebJob in Azure App Service](webjobs-create.md) |
-| Follow a tutorial using a practical use case | [Tutorial: Run background tasks with WebJobs](tutorial-webjobs.md) |
+| Follow a tutorial using a practical use case | [Build a scheduled WebJob](tutorial-webjobs.md) |
 
-## <a name="NextSteps"></a> Next steps
+## <a name="NextSteps"></a> Related content
 
-- [Review background jobs best practices – Azure Architecture Center](/azure/architecture/best-practices/background-jobs)
-- [Develop WebJobs using Visual Studio](webjobs-dotnet-deploy-vs.md)
+- [Review background jobs best practices](/azure/architecture/best-practices/background-jobs)
+- [Develop and deploy WebJobs using Visual Studio](webjobs-dotnet-deploy-vs.md)
 - [Get started with the WebJobs SDK](webjobs-sdk-get-started.md)
-- [Use the WebJobs SDK to build advanced jobs](webjobs-sdk-how-to.md)
+- [Use the WebJobs SDK for background processing](webjobs-sdk-how-to.md)
 - [Review Kudu WebJobs reference on GitHub](https://github.com/projectkudu/kudu/wiki/WebJobs)

articles/app-service/overview-webjobs.md

@@ -5,7 +5,7 @@ author: msangapu-msft
 tags: app-service
 
 ms.topic: concept-article
-ms.date: 05/19/2025
+ms.date: 12/02/2025
 ms.update-cycle: 180-days
 ms.author: msangapu
 ms.collection: ce-skilling-ai-copilot
@@ -14,38 +14,38 @@ ms.custom:
   - build-2025
   - sfi-image-nochange
 
-# As an App Service user, I want to learn about routine planned maintenance so that I know what to expect.
+#customer intent: As an App Service user, I want to learn about routine planned maintenance so that I know what to expect.
 
 ---
 
 # Routine planned maintenance for Azure App Service
 
-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.
+Routine maintenance includes behind-the-scenes updates to Azure App Service. These updates can 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 part of routine maintenance. For more information, see [Modern Lifecycle Policy](/lifecycle/policies/modern).
 
-Microsoft's service quality and uptime guarantees continue to apply during maintenance periods. Notifications are provided to give customers visibility into platform changes.
+Microsoft's service quality and uptime guarantees continue to apply during maintenance periods. We notify customers to provide visibility into platform changes.
 
 ## What to expect
 
-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.
+Like personal computers, mobile phones, and other devices, computers 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, which allows updates to proceed without downtime.
 
-Maintenance typically occurs monthly but may vary depending on your organization's needs and other factors.
+Maintenance typically occurs monthly but might 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).
+Because a typical cloud solution consists of multiple applications, databases, storage accounts, functions, and other resources, parts of your solution might 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**.
+To find maintenance events, search for **Service Health** in the Azure portal. Under **ACTIVE EVENTS**, select **Planned maintenance**.
 
 :::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":::
 
-From top to bottom, the example shows:
+The Azure portal provides this information:
 
 - A descriptive title of the maintenance event.
 - Affected regions and subscriptions.
 - The expected maintenance window.
 
-The following screenshots show additional information available through the **Impacted Resources** tab:
+The following screenshots show information available through the **Impacted Resources** tab:
 
 :::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":::
 
@@ -55,20 +55,20 @@ From left to right, the example shows:
 - The **More info** option.
 
 > [!NOTE]
-> Manual initiation of maintenance is not supported for App Service Plans. However, App Service Environments (ASE) do support manual maintenance preferences.
+> Manual initiation of maintenance isn't supported for App Service Plans. App Service Environments (ASE) do support manual maintenance preferences.
 
 :::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":::
 
 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**.
+- After maintenance starts, you can view timestamps under **More info**.
 
 ## Frequently asked questions
 
 ### Why is the maintenance taking so long?
 
-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.
+Routine maintenance delivers the latest updates to the platform and service. It's difficult to predict how maintenance affects individual apps. 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 updated machines and continue to run. There's no downtime when requests and traffic aren't served.
 
 ### Why am I getting so many notifications?
 
@@ -78,7 +78,7 @@ Customers often have multiple applications that are upgraded at different times.
 
 Platform maintenance shouldn't affect application uptime or availability. Applications continue to stay online while platform maintenance occurs.
 
-Platform maintenance might cause applications to be cold started on new virtual machines, which can lead to delays. An application is still considered to be online while it's cold starting. To minimize or avoid cold starts, consider using [local cache for Windows apps](overview-local-cache.md) and [health check](monitor-instances-health-check.md).
+Platform maintenance might cause applications to be started cold on new virtual machines, which can lead to delays. An application is still considered to be online while it's cold-starting. To minimize or avoid cold starts, consider using [local cache for Windows apps](overview-local-cache.md) and [health check](monitor-instances-health-check.md).
 
 We don't expect sites to incur any service-level agreement (SLA) violations during the maintenance windows.
 
@@ -90,11 +90,13 @@ Maintenance operations upgrade machines iteratively while App Service monitors t
 
 ### 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 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.
+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. There's less stress on the system in customer applications and 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 attempt to pause before reaching critical phases. Some underlying instance movements might continue, but they're orchestrated to overlap safely and maintain site availability.
 
 ### What are my options to control routine maintenance?
 
-If you run your workloads in an isolated product via App Service Environment v3, you can schedule the upgrades if necessary. For more information about this capability, see the blog post [Control and automate planned maintenance for App Service Environment v3](https://azure.github.io/AppService/2022/09/15/Configure-automation-for-upgrade-preferences-in-App-Service-Environment.html).
+If you run your workloads in an isolated product by using App Service Environment v3, you can schedule the upgrades if necessary. For more information about this capability, see the blog post [Control and automate planned maintenance for App Service Environment v3](https://azure.github.io/AppService/2022/09/15/Configure-automation-for-upgrade-preferences-in-App-Service-Environment.html).
 
 ### Can I prepare my apps better for restarts?
 
@@ -104,7 +106,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 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.
+Updates and maintenance events have been happening to the platform since its inception. The frequency of updates decreased over time. 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.
 
 ## Related content