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

Author: v-thepet

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

@@ -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/app-service/webjobs-execution.md

@@ -6,14 +6,26 @@ ms.service: azure-app-service
 author: msangapu-msft
 ms.author: msangapu
 ms.date: 05/01/2025
+ms.collection: ce-skilling-ai-copilot
 ---
 
 # How WebJobs run in Azure App Service
 
-Azure WebJobs allow you to run background tasks within your App Service app, without needing separate infrastructure. These tasks are discovered and managed by the **Kudu engine**, which handles execution, monitoring, and log collection.
+Azure WebJobs allow you to run background tasks within your App Service app, without needing separate infrastructure. These tasks are discovered and managed by the Kudu engine, the built-in App Service deployment and runtime management service. Kudu handles WebJob execution, file system access, diagnostics, and log collection behind the scenes.
 
 This article explains how WebJobs are discovered, how the runtime decides what to execute, and how you can configure behavior using the optional `settings.job` file.
 
+## Platform-specific notes
+
+WebJobs support a variety of script and executable formats, depending on the App Service hosting environment. The types of files you can run—and the runtimes available—vary slightly based on whether you're using Windows code, Linux code, or custom containers. In general, built-in runtimes are available for common scripting languages, and additional file types are supported when they match the language runtime of your app or container.
+
+[!INCLUDE [webjob-types](./includes/webjobs-create/webjob-types.md)]
+
+>[!IMPORTANT]
+> WebJobs that are continuous, scheduled, or event-driven may stop running if the web app hosting them becomes idle. Web apps can time out after 20 minutes of inactivity, and only direct requests to the app reset this idle timer. Actions like viewing the portal or accessing the Kudu tools do not keep the app active.
+> To ensure WebJobs run reliably, enable the Always on setting in the Configuration pane of your App Service.
+> This setting is available only in the Basic, Standard, and Premium pricing tiers.
+
 ## Job discovery and folder structure
 
 WebJobs are stored in the `site/wwwroot/App_Data/jobs/` folder of your App Service app. There are two subfolders:
@@ -34,10 +46,7 @@ Inside the job folder, the Kudu engine looks for a file to execute. This file ca
 
 The WebJobs runtime uses a file named `run.*` (such as `run.py`, `run.sh`, or `run.js`) as the explicit entry point for a job. This file tells the platform which script or binary to execute first, ensuring consistent and predictable behavior across environments.
 
-> [!NOTE]  
-> The filename must be exactly `run.*` to be autodetected. Files like `start.sh` or `job.py` will be ignored unless manually triggered.
-
-If no `run.*` file is found, the platform attempts to detect a fallback entry point by selecting the first supported file based on the language platform of the WebJob. For example:
+The filename must be exactly `run.*` to be autodetected. Files like `start.sh` or `job.py` will be ignored unless manually triggered. If no `run.*` file is found, the platform attempts to detect a fallback entry point by selecting the first supported file based on the language platform of the WebJob. For example:
 - A Python WebJob with multiple `.py` files (for example, `file1.py`, `file2.py`) will execute the first `.py` file it finds in the archive.
 - A Node.js WebJob looks for the first `.js` file.
 - A Bash-based WebJob looks for the first `.sh` script.
@@ -82,10 +91,6 @@ For more advanced monitoring and querying capabilities, consider integrating wit
 
 Triggered WebJobs include a full history of executions. Continuous WebJobs stream logs in real time.
 
-## Platform-specific notes
-
-[!INCLUDE [webjobs-always-on-note](../../includes/webjobs-always-on-note.md)]
-
 ## Troubleshooting tips
 
 - **WebJob not starting:** Check for a missing or misnamed `run.*` file. Ensure it's in the correct job folder (`triggered` or `continuous`).

articles/application-gateway/for-containers/alb-controller-helm-chart.md

@@ -0,0 +1,78 @@
+---
+title: ALB Controller Helm Chart
+description: This article documents the latest helm chart for Application Gateway for Containers' ALB Controller.
+services: application-gateway
+author: greg-lindsay
+ms.service: azure-appgw-for-containers
+ms.topic: release-notes
+ms.date: 5/2/2025
+ms.author: greglin
+---
+<!-- Custom Resource Definitions (CRDs) -->
+
+# ALB Controller Helm Chart
+
+![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)
+
+A Helm chart to install the ALB Controller on Kubernetes.
+
+The following parameters are supported for configuration during installation:
+
+- tolerations
+- name
+- installGatewayApiCRDs
+- logLevel
+- namespace
+- seucrityPolicyFeatureFlag
+
+## Values
+
+| Key | Type | Default | Description |
+| ----- | ------ | --------- | ------------- |
+| albController.controller | object | `{"replicaCount":2,"resource":{"limits":{"cpu":"400m","memory":"400Mi"},"requests":{"cpu":"100m","memory":"200Mi"}},"tolerations":[]}` | ALB Controller parameters |
+| albController.controller.replicaCount | int | `2` | ALB Controller's replica count. |
+| albController.controller.resource | object | `{"limits":{"cpu":"400m","memory":"400Mi"},"requests":{"cpu":"100m","memory":"200Mi"}}` | ALB Controller's container resource parameters. |
+| albController.controller.tolerations | list | `[]` | Tolerations for ALB Controller |
+| albController.env | list | `[{"name":"","value":""}]` | Environment variables for ALB Controller. |
+| albController.image | object | `{"name":{"CRDs":"application-lb/images/alb-controller-crds","bootstrap":"application-lb/images/alb-controller-bootstrap","controller":"application-lb/images/alb-controller"},"pullPolicy":"IfNotPresent","registry":"mcr.microsoft.com"}` | ALB Controller image parameters. |
+| albController.image.name | object | `{"CRDs":"application-lb/images/alb-controller-crds","bootstrap":"application-lb/images/alb-controller-bootstrap","controller":"application-lb/images/alb-controller"}` | Image name defaults. |
+| albController.image.name.CRDs | string | `"application-lb/images/alb-controller-crds"` | ALB Controller CRDs' image name |
+| albController.image.name.bootstrap | string | `"application-lb/images/alb-controller-bootstrap"` | alb-controller bootstrap's init container image name. |
+| albController.image.name.controller | string | `"application-lb/images/alb-controller"` | ALB Controller's image name. |
+| albController.image.pullPolicy | string | `"IfNotPresent"` | Container image pull policy for ALB Controller containers. |
+| albController.image.registry | string | `"mcr.microsoft.com"` | Container image registry for ALB Controller. |
+| albController.imagePullSecrets | list | `[]` |  |
+| albController.installGatewayApiCRDs | bool | `true` | A flag to enable/disable installation of Gateway API CRDs. |
+| albController.logLevel | string | `"info"` | Log level of ALB Controller. |
+| albController.namespace | string | `"azure-alb-system"` | Namespace to deploy ALB Controller components in. |
+| albController.securityPolicyFeatureFlag | bool | `false` | Enable Application Load Balancer Security Policy Resource (WAF Preview). |
+
+## Tolerations
+
+Tolerations follow Kubernetes' implementation as defined [here](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/).
+
+Tolerations are added to each of the ALB Controller pods, supporting the following format:
+
+```yaml
+tolerations:
+- key: "key1"
+  operator: "Equal"
+  value: "value1"
+  effect: "NoSchedule"
+```
+
+If desired, you can specify the toleration inline via the helm install command using the following example:
+
+```bash
+HELM_NAMESPACE='<namespace for deployment>'
+CONTROLLER_NAMESPACE='azure-alb-system'
+VERSION='<latest_version>'
+az aks get-credentials --resource-group $RESOURCE_GROUP --name $AKS_NAME
+helm install alb-controller oci://mcr.microsoft.com/application-lb/charts/alb-controller \
+     --namespace $HELM_NAMESPACE \
+     --version $VERSION \
+     --set albController.namespace=$CONTROLLER_NAMESPACE \
+     --set albController.podIdentity.clientID=$(az identity show -g $RESOURCE_GROUP -n azure-alb-identity --query clientId -o tsv)
+     --set tolerations.key=key1 --set tolerations.operator=Equal --set tolerations.value=value1 --set tolerations.effect=NoExecute --set tolerations.tolerationSeconds=3600
+     --set tolerations.key=key2 --set tolerations.operator=Exists --set tolerations.effect=NoSchedule
+```

articles/application-gateway/for-containers/alb-controller-release-notes.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-appgw-for-containers
 ms.topic: release-notes
-ms.date: 3/31/2025
+ms.date: 5/2/2025
 ms.author: greglin
 ---
 
@@ -24,19 +24,20 @@ Instructions for new or existing deployments of ALB Controller are found in the
 
 ## Latest Release (Recommended)
 
-| ALB Controller Version | Gateway API Version | Kubernetes Version | Release Notes |
+| ALB Controller Version | Gateway API Version | Minimum Kubernetes Version | Release Notes |
 | ---------------------- | ------------------- | ------------------ | ------------- |
-| 1.5.2 | v1.1.1 | v1.26, v1.27, v1.28, v1.29, v1.30 | Support for Azure CNI Overlay |
+| 1.6.7 | v1.1.1 | v1.27 | [Fix for SSE timeout value of 0](https://aka.ms/qa2153620), [Overlay CNI fix](https://github.com/Azure/AKS/issues/4950), [support readinessProbe port by name](https://github.com/Azure/AKS/issues/4861), leverage init container during bootstrap, misc. bug fixes and improvements |
 
 ## Release history
 
-| ALB Controller Version | Gateway API Version | Kubernetes Version | Release Notes |
+| ALB Controller Version | Gateway API Version | Minimum Kubernetes Version | Release Notes |
 | ---------------------- | ------------------- | ------------------ | ------------- |
-| 1.4.12 | v1.1.1 | v1.26, v1.27, v1.28, v1.29, v1.30 | Updated to Gateway API version 1.1.1, Regex match support for path and header match in HTTP and GRPC routes, [Wildcard hostname fix](https://github.com/Azure/AKS/issues/4713), Misc. bug fixes and improvements |
-| 1.3.7| v1.1 | v1.26, v1.27, v1.28, v1.29, v1.30 | Minor fixes and improvements |
-| 1.2.3| v1.1 | v1.26, v1.27, v1.28, v1.29, v1.30 | Gateway API v1.1, gRPC support, frontend mutual authentication, readiness probe fixes, custom health probe port and TLS mode  |
-| 1.0.2| v1 | v1.26, v1.27, v1.28, v1.29 | ECDSA + RSA certificate support for both Ingress and Gateway API, Ingress fixes, Server-sent events support |
-| 1.0.0| v1 | v1.26, v1.27, v1.28 | General Availability! URL redirect for both Gateway and Ingress API, v1beta1 -> v1 of Gateway API, quality improvements<br/>Breaking Changes: TLS Policy for Gateway API [PolicyTargetReference](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io%2fv1alpha2.PolicyTargetReferenceWithSectionName)<br/>Listener is now referred to as [SectionName](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.SectionName)<br/>Fixes: Request timeout of 3 seconds, [HealthCheckPolicy interval](https://github.com/Azure/AKS/issues/4086), [pod crash for missing API fields](https://github.com/Azure/AKS/issues/4087) |
+| 1.5.2 | v1.1.1 | v1.26 | Support for Azure CNI Overlay |
+| 1.4.12 | v1.1.1 | v1.26 | Updated to Gateway API version 1.1.1, Regex match support for path and header match in HTTP and GRPC routes, [Wildcard hostname fix](https://github.com/Azure/AKS/issues/4713), Misc. bug fixes and improvements |
+| 1.3.7| v1.1 | v1.26 | Minor fixes and improvements |
+| 1.2.3| v1.1 | v1.26 | Gateway API v1.1, gRPC support, frontend mutual authentication, readiness probe fixes, custom health probe port and TLS mode  |
+| 1.0.2| v1 | v1.26 | ECDSA + RSA certificate support for both Ingress and Gateway API, Ingress fixes, Server-sent events support |
+| 1.0.0| v1 | v1.26 | General Availability! URL redirect for both Gateway and Ingress API, v1beta1 -> v1 of Gateway API, quality improvements<br/>Breaking Changes: TLS Policy for Gateway API [PolicyTargetReference](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io%2fv1alpha2.PolicyTargetReferenceWithSectionName)<br/>Listener is now referred to as [SectionName](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.SectionName)<br/>Fixes: Request timeout of 3 seconds, [HealthCheckPolicy interval](https://github.com/Azure/AKS/issues/4086), [pod crash for missing API fields](https://github.com/Azure/AKS/issues/4087) |
 | 0.6.3 | v1beta1 | v1.25 | Hotfix to address handling of Application Gateway for Containers frontends during controller restart in managed scenario |
 | 0.6.2 | - | - | Skipped release |
 | November 6, 2023 - 0.6.1 | v1beta1 | v1.25 | Gateway / Ingress API - Header rewrite support, Ingress API - URL rewrite support, Ingress multiple-TLS listener bug fix, two certificates maximum per host, adopting [semantic versioning (semver)](https://semver.org/), quality improvements |