Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into avesanRefresh

Author: roygara

articles/active-directory-b2c/media/analytics-with-application-insights/app-insights.png

@@ -190,7 +190,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 221 | Senegal | 10 | 30 |
 | 223 | Mali | 20 | 100 |
 | 224 | Guinea | 20 | 100 |
-| 225 |	Ivory Coast|	10	| 30 |
+| 225 |	Côte d’Ivoire |	10	| 30 |
 | 226 |  Burina Faso   | 10  |  30  |
 | 228 |  Togo  | 10  |  30  |
 | 233 |	Ghana|	10	| 30 |
@@ -219,7 +219,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 60 | Malaysia | 50 | 200 |
 | 62 |  Indonesia | 50  |  200 |
 | 63 |  Philippines   | 50  |  200 |
-| 670 |	East Timor (Timor-Leste)  |	10	| 30 |
+| 670 |	Timor-Leste  |	10	| 30 |
 | 7 |  Russia | 100  |  1000 |
 | 84 |  Vietnam   | 150  |  500 |
 | 855 |  Cambodia  | 50  |  200 |
@@ -228,7 +228,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 92 |  Pakistan| 100  |  1000 |
 | 93 |	Afghanistan  |	10	| 30 |
 | 94 |  Sri Lanka | 100  |  500 |
-| 95 |	Myanmar (Burma) | 10	| 30 |
+| 95 |	Myanmar | 10	| 30 |
 | 961 |	Lebanon  |	10	| 30 |
 | 967 |	Yemen	|10	| 30 |
 | 970 |  State of Palestine| 10  |  30  |

articles/active-directory-b2c/service-limits.md

@@ -81,7 +81,7 @@ After the files are updated, prepare your environment variables to work with Ope
 
 ### API keys and endpoints
 
-To make calls to OpenAI with your client, you need to first get the keys and endpoint values from Azure OpenAI or OpenAI, and add them as secrets for use in your application. Save the values for later use.
+To make calls to OpenAI with your client, first get the keys and endpoint values from Azure OpenAI or OpenAI, and add them as secrets for use in your application. Save the values for later use.
 
 For Azure OpenAI, see [this documentation](/azure/ai-services/openai/quickstart?pivots=programming-language-csharp&tabs=command-line%2Cpython#retrieve-key-and-endpoint) to retrieve the following values. If you're planning to use a [managed identity](../../overview-managed-identity.md) to secure your app, you don't need the API key value.
 

articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-python-pivot.md

@@ -0,0 +1,47 @@
+---
+author: msangapu-msft
+ms.service: azure-app-service
+ms.topic: include
+ms.date: 05/01/2025
+ms.author: msangapu
+---
+
+### <a name="acceptablefiles"></a>Supported file types for scripts or programs
+
+### [Windows code](#tab/windowscode)
+
+The following file types are supported:
+
+- Using Windows cmd: *.cmd*, *.bat*, *.exe*
+- Using PowerShell: *.ps1*
+- Using Bash: *.sh*
+- Using Node.js: *.js*
+- Using Java: *.jar*
+
+The necessary runtimes to run these file types are already installed on the web app instance.
+
+### [Windows container](#tab/windowscontainer)
+
+The following file types are supported using Windows cmd: *.cmd*, *.bat*, *.exe*
+
+In addition to these file types, WebJobs written in the language runtime of the Windows container app are supported.
+
+- Example: *.jar* and *.war* scripts are supported if the container is a Java app.
+
+### [Linux code](#tab/linuxcode)
+
+*.sh* scripts are supported.
+
+In addition to shell scripts, WebJobs written in the language of the selected runtime are also supported.
+
+- Example: Python (*.py*) scripts are supported if the main site is a Python app.
+
+### [Linux container](#tab/linuxcontainer)
+
+*.sh* scripts are supported.
+
+In addition to shell scripts, WebJobs written in the language runtime of the Linux container app are also supported.
+
+- Example: Node (*.js*) scripts are supported if the site is a Node.js app.
+
+---

articles/app-service/includes/webjobs-create/webjob-types.md

@@ -3,40 +3,107 @@ 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."
 keywords: "Azure WebJobs, App Service, background processing, triggered jobs, continuous jobs, NCRONTAB, deployment, Azure, technical overview"
 ms.topic: overview
-ms.date: 5/1/2025
+ms.date: 5/2/2025
 author: msangapu-msft
 ms.author: msangapu
 ms.reviewer: ggailey
-#Customer intent: As a web developer, I want to leverage background tasks to keep my application running smoothly.
+ms.collection: ce-skilling-ai-copilot
+#Customer intent: I want to understand what WebJobs are, how they work with Azure App Service, and whether they’re the right solution for running background tasks in my app. I'm looking for guidance on supported platforms, types of jobs, deployment options, and how to get started or go deeper based on my use case.
 ---
 
 # App Service WebJobs overview
 
-## Introduction
-Azure WebJobs is a built-in feature of Azure App Service that enables you to run background tasks, scripts, and programs alongside your web, API, or mobile applications without needing separate infrastructure. This integration simplifies the automation of routine or resource-intensive operations—such as data processing, file cleanups, or queue monitoring—by leveraging the same scalable, managed environment as your primary 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—such as data processing, image resizing, queue handling, or file cleanup—by running in the same scalable, managed environment as your application.
+
+## Choosing WebJobs
+
+WebJobs are a good fit when:
+- You're already hosting 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.
+
+For more scalable, independently hosted, or event-driven workloads, consider using [Azure Functions](../azure-functions/functions-overview.md).
+
+## Key capabilities
+
+- Run background tasks without provisioning separate infrastructure
+- Trigger jobs on demand, on a schedule, or continuously
+- Use multiple languages and scripting platforms
+- Deploy using the Azure portal, Visual Studio, zip deployment, or automation pipelines
+- Monitor and troubleshoot using Kudu or App Service diagnostics
+- Integrate with other Azure services such as Azure Storage, Event Hubs, or Service Bus
 
 ## WebJob types
-WebJobs come in two primary types:
-- **Triggered WebJobs:** Run on demand, on a schedule, or in response to specific events.
-- **Continuous WebJobs:** Operate perpetually, ensuring that critical background processes are always active.
 
-For scheduled tasks, NCRONTAB expressions are used to define precise execution intervals, giving you fine-grained control over when the jobs run.
+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.
+
+
+:::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.":::
 
 ## Supported platforms and file types
-Azure WebJobs is fully supported on Windows code, Windows containers, Linux code, and Linux containers.
 
-Supported file types include:
-- Windows command scripts (`.cmd`, `.bat`, `.exe`)
-- PowerShell scripts (`.ps1`)
-- Bash scripts (`.sh`)
-- Scripting languages such as Python (`.py`), PHP (`.php`), Node.js (`.js`), and F# (`.fsx`)
+WebJobs are supported on the following App Service hosting options:
+
+- Windows code
+- Windows containers
+- Linux code
+- Linux containers
+
+Supported file/script types include:
+
+- Windows executables and scripts: `.exe`, `.cmd`, `.bat`
+- PowerShell scripts: `.ps1`
+- Bash scripts: `.sh`
+- Scripting languages: Python (`.py`), Node.js (`.js`), PHP (`.php`), F# (`.fsx`)
+- Any language runtime included in your container app
+
+This versatility enables you to integrate WebJobs into a wide range of application architectures using the tools and languages you're already comfortable with.
+
+## Deployment options
+
+You can deploy WebJobs using several methods:
+
+- **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.
+- **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.
+
+## Scaling considerations
+
+WebJobs scale together with your App Service plan. If your app is configured to scale out to multiple instances, your WebJobs will run on each instance as appropriate:
+- **Triggered WebJobs** will run 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.
+
+## Best practices
+
+- Use **triggered** WebJobs for ad hoc 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 **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.
+
+
+## Choose your scenario
 
-This versatility enables integration of WebJobs into a wide range of application architectures.
+| Goal | Article |
+|------|---------|
+| Quickly run a scheduled WebJob | [Quickstart: 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) |
 
-## Benefits and deployment
-By incorporating WebJobs into your App Service, you reduce operational overhead while gaining robust capabilities for background processing. Deployment options are flexible and include:
-- **Visual Studio Integration:** Seamlessly deploy WebJobs alongside your ASP.NET applications.
-- **Azure Portal and ZIP Deployment:** Easily upload and deploy your WebJob packages.
-- **Automated Pipelines:** Use ARM templates or Git for automated deployments.
+## <a name="NextSteps"></a> Next steps
 
-Additionally, WebJobs provide built-in logging and monitoring, as well as seamless integration with other Azure services, making them a cost-effective and efficient solution for automating background tasks.
+- [Background jobs best practices – Azure Architecture Center](/azure/architecture/best-practices/background-jobs)
+- [Develop 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)
+- [Kudu WebJobs reference on GitHub](https://github.com/projectkudu/kudu/wiki/WebJobs)

articles/app-service/media/overview-webjobs/webjob-types-app-service.png

@@ -2,7 +2,7 @@
 title: 'Create a scheduled WebJob using a prebuilt script'
 description: Quickly schedule a time-based WebJob in Azure App Service using a prebuilt script for Windows or Linux.
 ms.topic: quickstart
-ms.date: 4/24/2025
+ms.date: 5/2/2025
 author: msangapu-msft
 ms.author: msangapu
 ms.reviewer: glenga
@@ -22,7 +22,7 @@ WebJobs in Azure App Service let you run scripts or programs as background tasks
 - Enable **Always On** in the App Service settings: [Configure Always On](configure-common.md?tabs=portal#configure-general-settings)
 - For Windows containers and all Linux apps, set the app setting `WEBSITE_SKIP_RUNNING_KUDUAGENT = false`
 
-## Step 1: Download a sample WebJob
+## Download a sample WebJob
 
 Choose the version that matches your App Service OS:
 
@@ -33,7 +33,7 @@ Choose the version that matches your App Service OS:
 
 Each zip contains a single script that prints the current system date and time.
 
-## Step 2: Add the WebJob in the Azure portal
+## Add the WebJob in the Azure portal
 
 1. In the [Azure portal](https://portal.azure.com), go to your **App Service** app.
 2. In the left menu, select **WebJobs** > **+ Add**.
@@ -49,13 +49,13 @@ Each zip contains a single script that prints the current system date and time.
 
 4. Select **OK** to create the WebJob.
 
-## Step 3: Monitor WebJob logs
+## Verify the WebJob
 
 1. Go to the **WebJobs** tab.
 2. Select your WebJob and open **Logs**.
 3. Confirm that it runs every minute and prints the system time.
 
-## Step 4: Clean up
+## Clean up
 
 To remove the WebJob, select the WebJob in the portal and select `Delete`.
 

articles/app-service/overview-webjobs.md

@@ -41,7 +41,7 @@ The following environment variables are related to the app environment in genera
 | `WEBSITE_PROACTIVE_AUTOHEAL_ENABLED` | By default, a VM instance is proactively corrected when it uses more than 90% of allocated memory for more than 30 seconds, or when 80% of the total requests in the last two minutes take longer than 200 seconds. If a VM instance triggers one of these rules, the recovery process is an overlapping restart of the instance.<br/><br/>Set to `false` to disable this recovery behavior. The default is `true`.<br/><br/>For more information, see the [Introducing Proactive Auto Heal](https://azure.github.io/AppService/2017/08/17/Introducing-Proactive-Auto-Heal.html) blog post. |
 | `WEBSITE_PROACTIVE_CRASHMONITORING_ENABLED` | Whenever the w3wp.exe process on a VM instance of your app crashes due to an unhandled exception for more than three times in 24 hours, a debugger process is attached to the main worker process on that instance. The debugger process collects a memory dump when the worker process crashes again. This memory dump is then analyzed, and the call stack of the thread that caused the crash is logged in your App Service logs.<br/><br/>Set to `false` to disable this automatic monitoring behavior. The default is `true`.<br/><br/>For more information, see the [Proactive Crash Monitoring in Azure App Service](https://azure.github.io/AppService/2021/03/01/Proactive-Crash-Monitoring-in-Azure-App-Service.html) blog post. |
 | `WEBSITE_DAAS_STORAGE_SASURI` | During crash monitoring (proactive or manual), the memory dumps are deleted by default. To save the memory dumps to a storage blob container, specify the shared access signature (SAS) URI. |
-| `WEBSITE_CRASHMONITORING_ENABLED` | Set to `true` to enable [crash monitoring](https://azure.github.io/AppService/2020/08/11/Crash-Monitoring-Feature-in-Azure-App-Service.html) manually. You must also set `WEBSITE_DAAS_STORAGE_SASURI` and `WEBSITE_CRASHMONITORING_SETTINGS`. The default is `false`.<br/><br/>This setting has no effect if remote debugging is enabled. Also, if this setting is set to `true`, [proactive crash monitoring](https://azure.github.io/AppService/2021/03/01/Proactive-Crash-Monitoring-Feature-in-Azure-App-Service.html) is disabled. |
+| `WEBSITE_CRASHMONITORING_ENABLED` | Set to `true` to enable [crash monitoring](https://azure.github.io/AppService/2020/08/11/Crash-Monitoring-Feature-in-Azure-App-Service.html) manually. You must also set `WEBSITE_DAAS_STORAGE_SASURI` and `WEBSITE_CRASHMONITORING_SETTINGS`. The default is `false`.<br/><br/>This setting has no effect if remote debugging is enabled. Also, if this setting is set to `true`, [proactive crash monitoring](https://azure.github.io/AppService/2021/03/01/Proactive-Crash-Monitoring-in-Azure-App-Service.html) is disabled. |
 | `WEBSITE_CRASHMONITORING_SETTINGS` | JSON with the following format:`{"StartTimeUtc": "2020-02-10T08:21","MaxHours": "<elapsed-hours-from-StartTimeUtc>","MaxDumpCount": "<max-number-of-crash-dumps>"}`. Required to configure [crash monitoring](https://azure.github.io/AppService/2020/08/11/Crash-Monitoring-Feature-in-Azure-App-Service.html) if `WEBSITE_CRASHMONITORING_ENABLED` is specified. To log the call stack without saving the crash dump in the storage account, add `,"UseStorageAccount":"false"` in the JSON. |
 | `REMOTEDEBUGGINGVERSION` | Remote debugging version. |
 | `WEBSITE_CONTENTAZUREFILECONNECTIONSTRING` | By default, App Service creates a shared storage for you at app creation. To use a custom storage account instead, set to the connection string of your storage account. For functions, see [App settings reference for Azure Functions](../azure-functions/functions-app-settings.md#website_contentazurefileconnectionstring).<br/><br/>Example: `DefaultEndpointsProtocol=https;AccountName=<name>;AccountKey=<key>` |
@@ -180,6 +180,7 @@ This section shows the configurable runtime settings for each supported language
 | `WEBSITE_JAVA_MAX_HEAP_MB` | Java maximum heap, in megabytes. This setting is effective only when you use an experimental Tomcat version. |
 | `WEBSITE_DISABLE_JAVA_HEAP_CONFIGURATION` | Manually disable `WEBSITE_JAVA_MAX_HEAP_MB` by setting this variable to `true` or `1`. |
 | `WEBSITE_AUTH_SKIP_PRINCIPAL` | By default, the following Tomcat [HttpServletRequest interfaces](https://tomcat.apache.org/tomcat-5.5-doc/servletapi/javax/servlet/http/HttpServletRequest.html) are hydrated when you enable the built-in [authentication](overview-authentication-authorization.md): `isSecure`, `getRemoteAddr`, `getRemoteHost`, `getScheme`, `getServerPort`, `getLocalPort`, `getRequestURL`. To disable it, set the value to `1`. |
+| `WEBSITE_AUTH_EXPIRED_SESSION_LOGOFF` | If a webapp uses EasyAuth, set this to `true` or `1` to force a redirect to the EasyAuth logout page if the session associated to a request has expired (e.g. for webapps running on Tomcat, this is defined by the element `session-timeout` in the file `web.xml`). |
 | `WEBSITE_SKIP_FILTERS` | To disable all servlet filters that App Service added, set to `1`. |
 | `IGNORE_CATALINA_BASE` | By default, App Service checks if the Tomcat variable `CATALINA_BASE` is defined. If not, it looks for the existence of `%HOME%\tomcat\conf\server.xml`. If the file exists, it sets `CATALINA_BASE` to `%HOME%\tomcat`. To disable this behavior and remove `CATALINA_BASE`, set this variable to `1` or `true`. |
 | `PORT` | Read-only. For Linux apps, the port that the Java runtime listens to in the container. |

articles/app-service/quickstart-webjobs.md

@@ -463,23 +463,27 @@ items:
       href: invoke-openapi-web-app-from-azure-ai-agent-service.md
 - name: WebJobs
   items:
-    - name: Overview 
-      href: overview-webjobs.md 
+    - name: Overview
+      href: overview-webjobs.md
+    - name: Background jobs best practices
+      href: /azure/architecture/best-practices/background-jobs?toc=/azure/app-service/toc.json&bc=/azure/app-service/breadcrumb/toc.json
       displayName: WebJobs overview
     - name: WebJobs Quickstart
       href: quickstart-webjobs.md
       displayName: Create a scheduled WebJob
     - name: WebJobs Tutorial
-      href: tutorial-webjobs.md      
-      displayName: Prepare and schedule a WebJob
-    - name: WebJobs How-to
+      href: tutorial-webjobs.md
+      displayName: Prepare and schedule a WebJob      
+    - name: How to create WebJobs
       href: webjobs-create.md
+    - name: How WebJobs work
+      href: webjobs-execution.md
     - name: Develop WebJobs using VS
       href: webjobs-dotnet-deploy-vs.md
     - name: Get started with WebJobs SDK
       href: webjobs-sdk-get-started.md
     - name: Use WebJobs SDK
-      href: webjobs-sdk-how-to.md          
+      href: webjobs-sdk-how-to.md
 - name: Reliability
   items:
   - name: Reliability in Azure App Service