Resolve merge conflict; move permissions

Author: kgremban

articles/application-gateway/proxy-buffers.md

@@ -5,36 +5,36 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 08/03/2022
+ms.date: 09/25/2024
 ms.author: greglin
 #Customer intent: As a user, I want to know how can I disable/enable proxy buffers.
 ---
 
 # Configure Request and Response Proxy Buffers
 
-Azure Application Gateway Standard v2 SKU supports buffering Requests (from clients) or Responses (from the backend servers). Based on the processing capabilities of the clients that interact with your Application Gateway, you can use these buffers to configure the speed of packet delivery.
+Azure Application Gateway Standard v2 SKU supports buffering Requests from clients or Responses (from the backend servers). Based on the processing capabilities of the clients that interact with your application gateway, you can use these buffers to configure the speed of packet delivery.
 
 ## Response Buffer 
 
-Application Gateway's Response buffer can collect all or parts of the response packets sent by the backend server, before delivering them to the clients. By default, the Response buffering is enabled on Application Gateway which is useful to accommodate slow clients. This setting allows you to conserve the backend TCP connections as they can be closed once Application Gateway receives complete response and work according to the client's processing speed. This way, your Application Gateway will continue to deliver the response as per client’s pace. 
+Application Gateway's response buffer can collect all or parts of the response packets sent by the backend server, before delivering them to the clients. By default, the Response buffering is enabled on Application Gateway which is useful to accommodate slow clients. This setting allows you to conserve the backend TCP connections as they can be closed once Application Gateway receives complete response and work according to the client's processing speed. This way, your Application Gateway continues to deliver the response as per the client’s pace. 
 
 
 ## Request Buffer 
 
-In a similar way, Application Gateway's Request buffer can temporarily store the entire or parts of the request body, and then forward a larger upload request at once to the backend server. By default, Request buffering setting is enabled on Application Gateway and is useful to offload the processing function of re-assembling the smaller packets of data on the backend server.
+In a similar way, Application Gateway's Request buffer can temporarily store the entire or parts of the request body, and then forward a larger upload request at once to the backend server. By default, Request buffering setting is enabled on Application Gateway and is useful to offload the processing function of reassembling the smaller packets of data on the backend server.
 
 
 >[!NOTE]
->By default, both Request and Response buffers are enabled on your Application Gateway resource but you can choose to configure them separately. Further, the settings are applied at a resource level and cannot be managed separately for each listener.
+>By default, both Request and Response buffers are enabled on your Application Gateway resource but you can choose to configure them separately. Further, the settings are applied at a resource level and can't be managed separately for each listener.
  
 </br>
 
-You can keep either the Request or Response buffer, enabled or disable, based on your requirements and/or the observed performance of the client systems that communicate with your Application Gateway. 
+You can keep either the Request or Response buffer, enabled or disabled, based on your requirements and the observed performance of the client systems that communicate with your Application Gateway. 
 
 </br>
 
 > [!WARNING]
->We strongly recommend that you test and evaluate the performance before rolling this out on the production gateways. 
+> We strongly recommend that you test and evaluate the performance before rolling this out on the production gateways. 
 
 ## How to change the buffer settings? 
 
@@ -51,6 +51,20 @@ az network application-gateway update --name <gw-name> --resource-group <rg-name
  az network application-gateway update --name <gw-name> --resource-group <rg-name> --set globalConfiguration.enableRequestBuffering=false
 ```
 
+### PowerShell method
+
+**New application gateway**
+```PowerShell
+$AppGw02 = New-AzApplicationGateway -Name "ApplicationGateway02" -ResourceGroupName "ResourceGroup02" -Location $location -BackendAddressPools $pool -BackendHttpSettingsCollection $poolSetting01 -FrontendIpConfigurations $fipconfig -GatewayIpConfigurations $gipconfig -FrontendPorts $fp01 -HttpListeners $listener01 -RequestRoutingRules $rule01 -Sku $sku -EnableRequestBuffering:$false -EnableResponseBuffering:$false
+```
+**Update an existing application gateway**
+```PowerShell
+$appgw = Get-AzApplicationGateway -Name $appgwName -ResourceGroupName $rgname
+$appgw.EnableRequestBuffering = $false
+$appgw.EnableResponseBuffering = $false
+Set-AzApplicationGateway -ApplicationGateway $appgw
+```
+
 ### ARM template method
 
 ```json
@@ -85,5 +99,5 @@ For reference, visit [Azure SDK for .NET](/dotnet/api/microsoft.azure.management
 
 ## Limitations
 - API version 2020-01-01 or later should be used to configure buffers.
-- Currently, these changes are not supported through Portal and PowerShell.
-- Request buffering cannot be disabled if you are running the WAF SKU of Application Gateway. The WAF requires the full request to buffer as part of processing, therefore, even if you disable request buffering within Application Gateway the WAF will still buffer the request. Response buffering is not impacted by the WAF.
+- Currently, these changes aren't supported through Portal and PowerShell.
+- Request buffering can't be disabled if you're running the WAF SKU of Application Gateway. The WAF requires the full request to buffer as part of processing, therefore, even if you disable request buffering within Application Gateway the WAF still buffers the request. Response buffering isn't impacted by the WAF.

articles/azure-app-configuration/concept-experimentation.md

@@ -98,7 +98,7 @@ Benefits:
 
 ### For intelligent applications (for example, AI-based features)
 
-Objective: Accelerate General AI (Gen AI) adoption and optimize AI models and use cases through rapid experimentation.
+Objective: Accelerate Generative AI (Gen AI) adoption and optimize AI models and use cases through rapid experimentation.
 
 Approach: Use experimentation to iterate quickly on AI models, test different scenarios, and determine effective approaches.
 

articles/azure-functions/flex-consumption-plan.md

@@ -136,18 +136,13 @@ In Flex Consumption, many of the standard application settings and site configur
 
 Keep these other considerations in mind when using Flex Consumption plan during the current preview:
 
-+ ** Host ** There is a 30 seconds timeout for the app initialization. If your function app takes longer than 30 seconds to start you will see gRPC related System.TimeoutException entries. This will be configurable and a more clear exception will be implemented as part of [this host work item](https://github.com/Azure/azure-functions-host/issues/10482).
-+ ** Durable Functions Performance ** Due to the per function scaling nature of Flex Consumption, to ensure the best performance for Durable Functions we recommend setting the [Always Ready instance count](./flex-consumption-how-to.md#set-always-ready-instance-counts) for the `durable` group to `1`. Also, with the Azure Storage provider, consider reducing the [queue polling interval](./durable/durable-functions-azure-storage-provider.md#queue-polling) to 10 seconds or less.  
++ **Host**: There is a 30 seconds timeout for the app initialization. If your function app takes longer than 30 seconds to start you will see gRPC related System.TimeoutException entries. This timeout will be configurable and a more clear exception will be implemented as part of [this host work item](https://github.com/Azure/azure-functions-host/issues/10482).
++ **Durable Functions Performance**: Due to the per function scaling nature of Flex Consumption, to ensure the best performance for Durable Functions we recommend setting the [Always Ready instance count](./flex-consumption-how-to.md#set-always-ready-instance-counts) for the `durable` group to `1`. Also, with the Azure Storage provider, consider reducing the [queue polling interval](./durable/durable-functions-azure-storage-provider.md#queue-polling) to 10 seconds or less.  
 + **VNet Integration** Ensure that the `Microsoft.App` Azure resource provider is enabled for your subscription by [following these instructions](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider). The subnet delegation required by Flex Consumption apps is `Microsoft.App/environments`.
 + **Triggers**: All triggers are fully supported except for Kafka and Azure SQL triggers. The Blob storage trigger only supports the [Event Grid source](./functions-event-grid-blob-trigger.md). Non-C# function apps must use version `[4.0.0, 5.0.0)` of the [extension bundle](./functions-bindings-register.md#extension-bundles), or a later version. 
-+ **Regions**:
-  + Not all regions are currently supported. To learn more, see [View currently supported regions](flex-consumption-how-to.md#view-currently-supported-regions).
-  + There is a temporary limitation where App Service quota limits for creating new apps are also being applied to Flex Consumption apps. If you see the following error "This region has quota of 0 instances for your subscription. Try selecting different region or SKU." please raise a support ticket so that your app creation can be unblocked.
-+ **Deployments**: These deployment-related features aren't currently supported:
-  + Deployment slots
-  + Continuous deployment using Azure DevOps Tasks (`AzureFunctionApp@2`)
-  + Continuous deployment using GitHub Actions (`functions-action@v1`) 
-+ **Scale**: The lowest maximum scale in preview is `40`. The highest currently supported value is `1000`.
++ **Regions**: Not all regions are currently supported. To learn more, see [View currently supported regions](flex-consumption-how-to.md#view-currently-supported-regions).
++ **Deployments**: Deployment slots are not currently supported.
++ **Scale**: The lowest maximum scale in preview is `40`. The highest currently supported value is `1000`. 
 + **Managed dependencies**: [Managed dependencies in PowerShell](functions-reference-powershell.md#dependency-management) aren't supported by Flex Consumption. You must instead [define your own custom modules](functions-reference-powershell.md#custom-modules).
 + **Diagnostic settings**: Diagnostic settings are not currently supported.
 

articles/azure-netapp-files/configure-customer-managed-keys-hardware.md

@@ -37,6 +37,7 @@ Azure NetApp Files volume encryption with customer-managed keys with the managed
 * Australia East
 * Brazil South
 * Canada Central
+* Central India
 * Central US
 * East Asia
 * East US
@@ -51,6 +52,7 @@ Azure NetApp Files volume encryption with customer-managed keys with the managed
 * Qatar Central
 * South Africa North
 * South Central US
+* South India
 * Southeast Asia
 * Spain Central
 * Sweden Central

articles/azure-resource-manager/bicep/variables.md

@@ -3,7 +3,7 @@ title: Variables in Bicep
 description: Describes how to define variables in Bicep
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 08/20/2024
+ms.date: 09/25/2024
 ---
 
 # Variables in Bicep
@@ -12,7 +12,7 @@ This article describes how to define and use variables in your Bicep file. You u
 
 Resource Manager resolves variables before starting the deployment operations. Wherever the variable is used in the Bicep file, Resource Manager replaces it with the resolved value.
 
-You're limited to 256 variables in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
+You're limited to 512 variables in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
 
 ## Define variables
 

articles/azure-resource-manager/templates/best-practices.md

@@ -3,7 +3,7 @@ title: Best practices for templates
 description: Describes recommended approaches for authoring Azure Resource Manager templates (ARM templates). Offers suggestions to avoid common problems when using templates.
 ms.topic: best-practice
 ms.custom: devx-track-arm-template
-ms.date: 09/22/2023
+ms.date: 09/25/2024
 ---
 # ARM template best practices
 
@@ -16,7 +16,7 @@ Limit the size of your template to 4 MB, and each resource definition to 1 MB. T
 You're also limited to:
 
 * 256 parameters
-* 256 variables
+* 512 variables
 * 800 resources (including [copy count](copy-resources.md))
 * 64 output values
 * 10 unique locations per subscription/tenant/management group scope