Merge pull request #307431 from MicrosoftDocs/main

Auto Publish – main to live - 2025-10-28 05:00 UTC

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

articles/app-service/app-service-hybrid-connections.md

@@ -4,7 +4,7 @@ description: Learn how to create and use hybrid connections in Azure App Service
 author: seligj95
 ms.assetid: 66774bde-13f5-45d0-9a70-4e9536a4f619
 ms.topic: how-to
-ms.date: 10/15/2025
+ms.date: 10/27/2025
 ms.update-cycle: 1095-days
 ms.author: jordanselig
 #customer intent: As an app developer, I want to understand the usage of Hybrid Connections to provide access to apps in Azure App Service.
@@ -140,6 +140,9 @@ The Hybrid Connections feature requires a relay agent in the network that hosts
 
 This tool runs on both Windows and Linux. On Windows, the Hybrid Connection Manager requires Windows Server 2012 and later. The Hybrid Connection Manager runs as a service and connects outbound to Azure Relay on port 443.
 
+> [!NOTE]
+> As of October 20, 2025, [Azure Service Bus no longer supports TLS 1.0 and TLS 1.1][ServiceBus]. The minimum TLS version is now 1.2 for all Service Bus deployments. Hybrid Connections use Service Bus for connectivity. App Service Hybrid Connection Manager version 0.7.7 and later supports TLS 1.2. If you are on a previous version, **you must update to the new version of the Hybrid Connection Manager as soon as possible to prevent service disruption.**
+
 ### Installation instructions
 
 # [Windows](#tab/windows)
@@ -400,3 +403,4 @@ If you have a command-line client for your endpoint, you can test connectivity f
 [Azure portal]: https://portal.azure.com/
 [sbpricing]: https://azure.microsoft.com/pricing/details/service-bus/
 [install-azure-cli]: /cli/azure/install-azure-cli/
+[ServiceBus]: /azure/service-bus-messaging/transport-layer-security-configure-minimum-version/

articles/application-gateway/for-containers/how-to-header-rewrite-gateway-api.md

@@ -5,7 +5,7 @@ services: application gateway
 author: mbender-ms
 ms.service: azure-appgw-for-containers
 ms.topic: how-to
-ms.date: 11/5/2024
+ms.date: 10/27/2025
 ms.author: mbender
 # Customer intent: As a cloud engineer, I want to implement HTTP header rewrites in Application Gateway for Containers, so that I can modify request and response headers for backend services to better handle client requests.
 ---
@@ -213,6 +213,9 @@ spec:
 EOF
 ```
 
+>[!Note]
+>Modifying the `Host` header is not supported with a `requestHeaderModifier` rule. To override the `Host` value specified to the backend target, use a [URLRewrite](how-to-url-rewrite-gateway-api.md#deploy-the-required-gateway-api-resources) filter.
+
 Once the HTTPRoute resource is created, ensure the route is _Accepted_ and the Application Gateway for Containers resource is _Programmed_.
 
 ```bash

articles/application-gateway/for-containers/how-to-header-rewrite-ingress-api.md

@@ -5,7 +5,7 @@ services: application gateway
 author: mbender-ms
 ms.service: azure-appgw-for-containers
 ms.topic: how-to
-ms.date: 10/23/2025
+ms.date: 10/27/2025
 ms.author: mbender
 # Customer intent: "As a cloud architect, I want to implement header rewriting in the Ingress API for Application Gateway for Containers, so that I can modify request and response headers for backend services to meet application requirements and facilitate better control over traffic management."
 ---
@@ -197,6 +197,9 @@ spec:
 EOF
 ```
 
+>[!Note]
+>Modifying the `Host` header is not supported with a `requestHeaderModifier` rule. To override the `Host` value specified to the backend target, use a [URLRewrite](how-to-url-rewrite-ingress-api.md#deploy-the-required-ingress-api-resources) filter.
+
 Once the IngressExtension resource is created, ensure the resource returns _No validation errors_ and is valid.
 
 ```bash

articles/azure-resource-manager/templates/deploy-to-resource-group.md

@@ -1,12 +1,12 @@
 ---
-title: Deploy resources to resource groups
-description: Describes how to deploy resources in an Azure Resource Manager template. It shows how to target more than one resource group.
+title: Use Azure Resource Manager templates to deploy resources to resource groups
+description: Learn how to deploy resources in an Azure Resource Manager template and how to target more than one resource group.
 ms.topic: how-to
 ms.custom: devx-track-arm-template
-ms.date: 08/01/2025
+ms.date: 10/27/2025
 ---
 
-# Resource group deployments with ARM templates
+# Use Azure Resource Manager templates to deploy resources to resource groups
 
 This article describes how to scope your deployment to a resource group. You use an Azure Resource Manager template (ARM template) for the deployment. The article also shows how to expand the scope beyond the resource group in the deployment operation.
 
@@ -43,7 +43,7 @@ To deploy to a resource group, use the resource group deployment commands.
 
 # [Azure CLI](#tab/azure-cli)
 
-For Azure CLI, use [az deployment group create](/cli/azure/deployment/group#az-deployment-group-create). The following example deploys a template to create a resource group. The resource group you specify in the `--resource-group` parameter is the **target resource group**:
+For the Azure CLI, use [`az deployment group create`](/cli/azure/deployment/group#az-deployment-group-create). The following example deploys a template to create a resource group. The resource group you specify in the `--resource-group` parameter is the **target resource group**:
 
 ```azurecli-interactive
 az deployment group create \
@@ -53,9 +53,9 @@ az deployment group create \
   --parameters storageAccountType=Standard_GRS
 ```
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
-For the PowerShell deployment command, use [New-AzResourceGroupDeployment](/powershell/module/az.resources/new-azresourcegroupdeployment). The following example deploys a template to create a resource group. The resource group you specify in the `-ResourceGroupName` parameter is the **target resource group**:
+For the Azure PowerShell deployment command, use [`New-AzResourceGroupDeployment`](/powershell/module/az.resources/new-azresourcegroupdeployment). The following example deploys a template to create a resource group. The resource group you specify in the `-ResourceGroupName` parameter is the **target resource group**:
 
 ```azurepowershell-interactive
 New-AzResourceGroupDeployment `
@@ -69,11 +69,11 @@ New-AzResourceGroupDeployment `
 
 For more detailed information about deployment commands and options for deploying ARM templates, see:
 
-* [Deploy resources with ARM templates and Azure portal](deploy-portal.md)
-* [Deploy resources with ARM templates and Azure CLI](deploy-cli.md)
+* [Deploy resources with ARM templates and the Azure portal](deploy-portal.md)
+* [Deploy resources with ARM templates and the Azure CLI](deploy-cli.md)
 * [Deploy resources with ARM templates and Azure PowerShell](deploy-powershell.md)
 * [Deploy resources with ARM templates and Azure Resource Manager REST API](deploy-rest.md)
-* [Use a deployment button to deploy templates from GitHub repository](deploy-to-azure-button.md)
+* [Use a deployment button to deploy templates from a GitHub repository](deploy-to-azure-button.md)
 * [Deploy ARM templates from Cloud Shell](deploy-cloud-shell.md)
 
 ## Deployment scopes
@@ -263,14 +263,68 @@ For more information, see [Management group](deploy-to-management-group.md#manag
 
 To deploy resources in the target resource group, define those resources in the `resources` section of the template. The following template creates a storage account in the resource group that's specified in the **deployment** operation:
 
-:::code language="json" source="~/resourcemanager-templates/get-started-with-templates/add-outputs/azuredeploy.json":::
+```json
+{
+  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
+  "contentVersion": "1.0.0.0",
+  "parameters": {
+    "storagePrefix": {
+      "type": "string",
+      "minLength": 3,
+      "maxLength": 11
+    },
+    "storageSKU": {
+      "type": "string",
+      "defaultValue": "Standard_LRS",
+      "allowedValues": [
+        "Standard_LRS",
+        "Standard_GRS",
+        "Standard_RAGRS",
+        "Standard_ZRS",
+        "Premium_LRS",
+        "Premium_ZRS",
+        "Standard_GZRS",
+        "Standard_RAGZRS"
+      ]
+    },
+    "location": {
+      "type": "string",
+      "defaultValue": "[resourceGroup().location]"
+    }
+  },
+  "variables": {
+    "uniqueStorageName": "[concat(parameters('storagePrefix'), uniqueString(resourceGroup().id))]"
+  },
+  "resources": [
+    {
+      "type": "Microsoft.Storage/storageAccounts",
+      "apiVersion": "2021-09-01",
+      "name": "[variables('uniqueStorageName')]",
+      "location": "[parameters('location')]",
+      "sku": {
+        "name": "[parameters('storageSKU')]"
+      },
+      "kind": "StorageV2",
+      "properties": {
+        "supportsHttpsTrafficOnly": true
+      }
+    }
+  ],
+  "outputs": {
+    "storageEndpoint": {
+      "type": "object",
+      "value": "[reference(variables('uniqueStorageName')).primaryEndpoints]"
+    }
+  }
+}
+```
 
 ## Deploy to multiple resource groups
 
 You can deploy to more than one resource group in a single ARM template. To target a resource group that's different from the one for the parent template, use a [nested or linked template](linked-templates.md). Within the deployment resource type, specify values for the subscription ID and resource group to which you want to deploy the nested template.
 
 > [!NOTE]
-> You can deploy to **800 resource groups** in a single deployment. Typically, this limitation means you can deploy to one resource group specified for the parent template, and up to 799 resource groups in nested or linked deployments. However, if your parent template contains only nested or linked templates and doesn't deploy any resources, then you can include up to 800 resource groups in nested or linked deployments.
+> You can deploy to **800 resource groups** in a single deployment. Typically, this limitation means you can deploy to one resource group specified for the parent template and up to 799 resource groups in nested or linked deployments. However, if your parent template contains only nested or linked templates and doesn't deploy any resources, then you can include up to 800 resource groups in nested or linked deployments.
 
 The following example deploys two storage accounts. The first storage account is deployed to the resource group specified in the deployment operation. The second storage account is deployed to the resource group specified in the `secondResourceGroup` and `secondSubscriptionID` parameters:
 
@@ -349,9 +403,9 @@ The following example deploys two storage accounts. The first storage account is
 
 If you set `resourceGroup` to the name of a resource group that doesn't exist, the deployment fails.
 
-To test the preceding template and see the results, use PowerShell or Azure CLI.
+To test the preceding template and see the results, use PowerShell or the Azure CLI.
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 To deploy two storage accounts to two resource groups in the **same subscription**, use: