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

Author: halkazwini

articles/app-service/app-service-configure-premium-v4-tier.md

@@ -3,7 +3,7 @@ title: Configure Premium V4 Tier
 description: Learn how to better performance for your web, mobile, and API app in Azure App Service by scaling to the new Premium V4 pricing tier.
 keywords: app service, azure app service, scale, scalable, app service plan, app service cost
 ms.topic: how-to
-ms.date: 07/17/2025
+ms.date: 08/22/2025
 ms.author: msangapu
 author: msangapu-msft
 ms.custom:
@@ -104,6 +104,7 @@ Premium V4 is available in the following regions:
 - East US 2
 - France Central
 - Japan East
+- Korea Central
 - North Central US
 - North Europe
 - Norway East

articles/app-service/overview-local-cache.md

@@ -6,7 +6,7 @@ tags: optional
 ms.assetid: e34d405e-c5d4-46ad-9b26-2a1eda86ce80
 ms.topic: conceptual
 ms.date: 04/17/2025
-ms.update-cycle: 1095-days
+ms.update-cycle: 180-days
 ms.custom: UpdateFrequency3
 ms.author: msangapu
 author: msangapu-msft

articles/app-service/overview-tls.md

@@ -4,7 +4,7 @@ description: Learn how TLS and SSL work in Azure App Service, including TLS vers
 keywords: Azure App Service, SSL, TLS, HTTPS, certificate management, TLS mutual authentication, secure bindings, SSL certificates, App Service Certificates, SSL in code, TLS versions
 ms.topic: overview
 ms.date: 04/17/2025
-ms.update-cycle: 1095-days
+ms.update-cycle: 180-days
 ms.author: msangapu
 author: msangapu-msft
 ms.service: azure-app-service

articles/application-gateway/for-containers/overview.md

@@ -6,7 +6,7 @@ author: mbender-ms
 ms.custom: references_regions
 ms.service: azure-appgw-for-containers
 ms.topic: overview
-ms.date: 7/21/2025
+ms.date: 8/21/2025
 ms.author: mbender
 # Customer intent: "As a cloud architect, I want to understand how Application Gateway for Containers functions, so that I can effectively implement it for load balancing and traffic management within my Kubernetes cluster."
 ---
@@ -114,6 +114,8 @@ Application Gateway for Containers is currently offered in the following regions
 - UAE North
 - UK South
 - West US
+- West US 2
+- West US 3
 - West Europe
 
 ### Implementation of Gateway API

articles/application-gateway/quick-create-bicep.md

@@ -38,6 +38,9 @@ The Bicep file used in this quickstart is from [Azure Quickstart Templates](http
 > [!TIP]
 > You can modify values of the `Name` and `Tier` parameters under `resource\applicationGateWay\properties\sku` to use a different SKU. For example: `Basic`.
 
+> [!NOTE]
+> In regions that support availability zones, if you don't specify zones during creation via CLI, PowerShell, ARM/Bicep, or the REST API—Azure Application Gateway automatically enables zone redundancy, distributing instances across multiple availability zones for enhanced resiliency
+
 Multiple Azure resources are defined in the Bicep file:
 
 - [**Microsoft.Network/applicationgateways**](/azure/templates/microsoft.network/applicationgateways)

articles/application-gateway/quick-create-cli.md

@@ -44,7 +44,7 @@ az group create --name myResourceGroupAG --location eastus
 
 ## Create network resources
 
-For Azure to communicate between the resources that you create, it needs a virtual network.  The application gateway subnet can contain only application gateways. No other resources are allowed.  You can either create a new subnet for Application Gateway or use an existing one. In this example, you create two subnets: one for the application gateway, and another for the backend servers. You can configure the Frontend IP of the Application Gateway to be Public or Private as per your use case. In this example, you'll choose a Public Frontend IP address.
+For Azure to communicate between the resources that you create, it needs a virtual network. The application gateway subnet can contain only application gateways. No other resources are allowed.  You can either create a new subnet for Application Gateway or use an existing one. In this example, you create two subnets: one for the application gateway, and another for the backend servers. You can configure the Frontend IP of the Application Gateway to be Public or Private as per your use case. In this example, you'll choose a Public Frontend IP address.
 
   > [!NOTE]
   > Application Gateway frontend now supports dual-stack IP addresses (Public Preview). You can now create up to four frontend IP addresses: Two IPv4 addresses (public and private) and two IPv6 addresses (public and private).
@@ -175,6 +175,9 @@ It can take up to 30 minutes for Azure to create the application gateway. After
 - **appGatewayFrontendIP**: Located on the **Frontend IP configurations** page. It assigns *myAGPublicIPAddress* to **appGatewayHttpListener**.
 - **rule1**: Located on the **Rules** page. It specifies the default routing rule that's associated with **appGatewayHttpListener**.
 
+> [!NOTE]
+> In regions that support availability zones, if you don't specify zones during creation via CLI, PowerShell, ARM/Bicep, or the REST API—Azure Application Gateway automatically enables zone redundancy, distributing instances across multiple availability zones for enhanced resiliency
+
 ## Test the application gateway
 
 Although Azure doesn't require an NGINX web server to create the application gateway, you installed it in this quickstart to verify whether Azure successfully created the application gateway. To get the public IP address of the new application gateway, use `az network public-ip show`.

articles/application-gateway/quick-create-powershell.md

@@ -171,6 +171,9 @@ New-AzApplicationGateway `
 > [!TIP]
 > You can modify values of the `Name` and `Tier` parameters to use a different SKU. For example: `Basic`.
 
+> [!NOTE]
+> In regions that support availability zones, if you don't specify zones during creation via CLI, PowerShell, ARM/Bicep, or the REST API—Azure Application Gateway automatically enables zone redundancy, distributing instances across multiple availability zones for enhanced resiliency
+
 ### Backend servers
 
 Now that you have created the Application Gateway, create the backend virtual machines which will host the websites. A backend can be composed of NICs, virtual machine scale sets, public IP address, internal IP address, fully qualified domain names (FQDN), and multitenant backends like Azure App Service. 

articles/application-gateway/quick-create-template.md

@@ -47,6 +47,9 @@ The template used in this quickstart is from [Azure Quickstart Templates](https:
 > [!TIP]
 > You can modify values of the `Name` and `Tier` parameters under `resource\applicationGateWay\properties\sku` to use a different SKU. For example: `Basic`. For information about deploying custom templates, see [Create and deploy ARM templates](../azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md).
 
+> [!NOTE]
+> In regions that support availability zones, if you don't specify zones during creation via CLI, PowerShell, ARM/Bicep, or the REST API—Azure Application Gateway automatically enables zone redundancy, distributing instances across multiple availability zones for enhanced resiliency
+
 Multiple Azure resources are defined in the template:
 
 - [**Microsoft.Network/applicationgateways**](/azure/templates/microsoft.network/applicationgateways)

articles/application-gateway/tutorial-autoscale-ps.md

@@ -13,7 +13,7 @@ ms.custom: mvc, devx-track-azurepowershell
 ---
 # Tutorial: Create an application gateway that improves web application access
 
-If you're an IT admin concerned with improving web application access, you can optimize your application gateway to scale based on customer demand and span multiple [availability zones](../reliability/availability-zones-overview.md). This tutorial helps you configure Azure Application Gateway v2 features that do that: autoscaling, zone redundancy, and static VIPs. You'll use Azure PowerShell cmdlets and the Azure Resource Manager deployment model to solve the problem.
+If you're an IT administrator aiming to improve web application access, you can optimize your application gateway to scale dynamically based on customer demand and span multiple [availability zones](../reliability/availability-zones-overview.md). This tutorial helps you configure key Azure Application Gateway v2 features, including autoscaling, zone redundancy, and static VIPs, to achieve those improvements. You'll use Azure PowerShell cmdlets and the Azure Resource Manager deployment model to solve the problem.
 
 In this tutorial, you learn how to:
 
@@ -28,7 +28,7 @@ In this tutorial, you learn how to:
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
-For more information on availability zone support in Application Gateway v2, see [Reliability for Application Gateway v2](../reliability/reliability-application-gateway-v2.md).
+For more information about availability zone support in Application Gateway v2, see [Reliability for Application Gateway v2](../reliability/reliability-application-gateway-v2.md).
 
 ## Prerequisites
 

articles/azure-functions/functions-bindings-event-grid-trigger.md

@@ -2,7 +2,7 @@
 title: Azure Event Grid trigger for Azure Functions
 description: Learn to run code when Event Grid events in Azure Functions are dispatched.
 ms.topic: reference
-ms.date: 04/02/2023
+ms.date: 08/20/2025
 ms.devlang: csharp
 # ms.devlang: csharp, java, javascript, powershell, python
 ms.custom: devx-track-csharp, fasttrack-edit, devx-track-python, devx-track-extended-java, devx-track-js, devx-track-ts
@@ -44,11 +44,11 @@ The type of the input parameter used with an Event Grid trigger depends on these
 
 When running your C# function in an isolated worker process, you need to define a custom type for event properties. The following example defines a `MyEventType` class.
 
-:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/EventGrid/EventGridFunction.cs" range="35-48":::
+:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/EventGrid/EventGridFunction.cs" range="33-45":::
 
 The following example shows how the custom type is used in both the trigger and an Event Grid output binding:
 
-:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/EventGrid/EventGridFunction.cs" range="11-33":::
+:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/EventGrid/EventGridFunction.cs" range="11-29":::
 
 # [In-process model](#tab/in-process)
 
@@ -342,7 +342,7 @@ Both [in-process](functions-dotnet-class-library.md) and [isolated worker proces
 
 Here's an `EventGridTrigger` attribute in a method signature:
 
-:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/EventGrid/EventGridFunction.cs" range="13-16":::
+:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/EventGrid/EventGridFunction.cs" range="11-14":::
 
 # [In-process model](#tab/in-process)