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

Author: paulth1

.openpublishing.redirection.json

@@ -227,7 +227,7 @@
     },
     {
       "source_path": "articles/databox-online/azure-stack-edge-2301-release-notes.md",
-      "redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-2301-release-notes",
+      "redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-2301-release-notes"
     },
     {
       "source_path": "articles/network-watcher/nsg-flow-logs-rest.md",
@@ -2393,7 +2393,7 @@
       "source_path_from_root": "/articles/app-service/manage-disaster-recovery.md",
       "redirect_url": "/azure/architecture/web-apps/guides/multi-region-app-service/multi-region-app-service",
       "redirect_document_id": false
-    },       
+    },
     {
       "source_path_from_root": "/articles/public-multi-access-edge-compute-mec/tutorial-create-vm-using-python-sdk.md",
       "redirect_url": "/previous-versions/azure/public-multi-access-edge-compute-mec/tutorial-create-vm-using-python-sdk",
@@ -6875,49 +6875,49 @@
       "redirect_document_id": false
     },
     {
-         "source_path": "articles/storage/files/storage-files-enable-soft-delete.md",
+      "source_path": "articles/storage/files/storage-files-enable-soft-delete.md",
       "redirect_url": "/azure/storage/files/storage-files-prevent-file-share-deletion",
       "redirect_document_id": false
-     },
-     {
+    },
+    {
       "source_path": "articles/defender-for-iot/organizations/release-notes-archive.md",
       "redirect_url": "/azure/defender-for-iot/organizations/release-notes-ot-monitoring-sensor-archive",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/nat-gateway/quickstart-create-nat-gateway-portal.md",
       "redirect_url": "/azure/nat-gateway/quickstart-create-nat-gateway",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/nat-gateway/quickstart-create-nat-gateway-powershell.md",
       "redirect_url": "/azure/nat-gateway/quickstart-create-nat-gateway",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/nat-gateway/quickstart-create-nat-gateway-cli.md",
       "redirect_url": "/azure/nat-gateway/quickstart-create-nat-gateway",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/nat-gateway/quickstart-create-nat-gateway-template.md",
       "redirect_url": "/azure/nat-gateway/quickstart-create-nat-gateway",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/nat-gateway/quickstart-create-nat-gateway-terraform.md",
       "redirect_url": "/azure/nat-gateway/quickstart-create-nat-gateway",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/nat-gateway/quickstart-create-nat-gateway-bicep.md",
       "redirect_url": "/azure/nat-gateway/quickstart-create-nat-gateway",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/defender-for-iot/organizations/eiot-sensor.md",
       "redirect_url": "/azure/defender-for-iot/organizations/concept-enterprise",
       "redirect_document_id": false
     }
   ]
-}
+}

articles/application-gateway/configuration-http-settings.md

@@ -16,7 +16,7 @@ The Backend Settings enable you to manage the configurations for backend connect
 ## Types of Backend Settings in Application Gateway
 While Portal users will only see the "Backend Settings" option, API users will have access to two types of settings. You must utilize the correct configuration, according to the protocol.
 
-* Backend HTTP settings - It is for Layer 7 proxy configurations that support HTTP, HTTPS, and WebSockets protocols.
+* Backend HTTP settings - It is for Layer 7 proxy configurations that support HTTP and HTTPS protocols.
 * Backend settings - It is for Layer 4 proxy (Preview) configurations that support TLS and TCP protocols.
 
 ---

articles/application-gateway/monitor-application-gateway-reference.md

@@ -1,7 +1,7 @@
 ---
 title: Monitoring data reference for Azure Application Gateway
 description: This article contains important reference material you need when you monitor Azure Application Gateway.
-ms.date: 03/28/2025
+ms.date: 05/12/2025
 ms.custom: horz-monitor
 ms.topic: reference
 author: greg-lindsay
@@ -109,7 +109,9 @@ https://management.azure.com/subscriptions/subid/providers/Microsoft.Network/loc
 
 ### TLS/TCP proxy metrics
 
-Application Gateway supports TLS/TCP proxy monitoring. With layer 4 proxy feature now available with Application Gateway, there are some Common metrics that apply to both layer 7 and layer 4. There are some layer 4 specific metrics. The following list summarizes the metrics are the applicable for layer 4 usage.
+The following metrics are available for monitoring Application Gateway's TLS/TCP proxy. In addition to Layer 4-specific metrics, there are several common metrics with Layer 7 (HTTP/S). For details of each, visit the complete [metrics listing](#supported-metrics-for-microsoftnetworkapplicationgateways).
+
+**Metrics that also apply to L4 proxy**
 
 - Current Connections
 - New Connections per second
@@ -118,14 +120,16 @@ Application Gateway supports TLS/TCP proxy monitoring. With layer 4 proxy featur
 - Unhealthy host count
 - Client RTT
 - Backend Connect Time
-- Backend First Byte Response Time. `BackendHttpSetting` dimension includes both layer 7 and layer 4 backend settings.
-
-For more information, see previous descriptions and the [metrics table](#supported-metrics-for-microsoftnetworkapplicationgateways).
+- Backend First Byte Response Time (`BackendHttpSetting` dimension applies to both Layer 7 and 4 backend settings).
+- Bytes Sent
+- Bytes Received
+- Compute Units
+- Capacity Units
 
-These metrics apply to layer 4 only.
+**L4 proxy-specific metrics**
 
-- **Backend Session Duration**. The total time of a backend connection. The average time duration from the start of a new connection to its termination. `BackendHttpSetting` dimension includes both layer 7 and layer 4 backend settings.
-- **Connection Lifetime**. The total time of a client connection to application gateway. The average time duration from the start of a new connection to its termination in milliseconds.
+- Backend Session Duration - The total time of a backend connection. The average time duration from the start of a new connection to its termination. `BackendHttpSetting` dimension includes both layer 7 and layer 4 backend settings.
+- Connection Lifetime - The total time of a client connection to application gateway. The average time duration from the start of a new connection to its termination in milliseconds.
 
 ### TLS/TCP proxy backend health
 

articles/automation/extension-based-hybrid-runbook-worker-install.md

@@ -4,7 +4,7 @@ description: This article provides information about deploying the extension-bas
 services: automation
 ms.subservice: process-automation
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-bicep, linux-related-content
-ms.date: 05/08/2025
+ms.date: 05/12/2025
 ms.topic: how-to
 #Customer intent: As a developer, I want to learn about extension so that I can efficiently deploy Hybrid Runbook Workers.
 ms.service: azure-automation
@@ -123,7 +123,7 @@ If you use a proxy server for communication between Azure Automation and machine
 
    The API call will provide the value with the key: `AutomationHybridServiceUrl`. Use the URL in the next step to enable extension on the VM.
 
-1. Install the Hybrid Worker Extension on the VM by running the following PowerShell cmdlet (Required module: Az.Compute). Use the `properties.automationHybridServiceUrl` provided by the above API call  
+1. Install the Hybrid Worker Extension on the VM by running the following PowerShell cmdlet (Required module: Az.Compute). Use the `properties.automationHybridServiceUrl` provided by the above API call. Ensure ProxyServer URL does not contain any blank spaces. 
 
 # [Windows](#tab/windows)
 

articles/azure-compute-fleet/TOC.yml

@@ -6,6 +6,8 @@
     href: quickstart-create-portal.md
   - name: Create with ARM template
     href: quickstart-create-rest-api.md
+  - name: Create using Azure CLI
+    href: quickstart-create-azure-cli.md
   expand: true 
 - name: Allocation strategies
   href: allocation-strategies.md

articles/azure-compute-fleet/quickstart-create-azure-cli.md

@@ -0,0 +1,111 @@
+---
+title: Create an Azure Compute Fleet using Azure CLI
+description: Learn how to create an Azure Compute Fleet using Azure CLI.
+author: ykh015
+ms.author: yakhande
+ms.topic: how-to
+ms.service: azure-compute-fleet
+ms.date: 05/09/2025
+ms.reviewer: jushiman
+ms.custom: devx-track-azurecli
+---
+
+# Create an Azure Compute Fleet using Azure CLI
+
+This article steps through using the Azure CLI to create and deploy a Compute Fleet resource
+
+Make sure that you've installed the latest [Azure CLI](/cli/azure/install-az-cli2) and are logged in to an Azure account with [az login](/cli/azure/reference-index).
+
+## Launch Azure Cloud Shell
+
+The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled and configured to use with your account.
+
+To open the Cloud Shell, select **Open Cloud Shell** from the upper right corner of a code block. You can also launch Cloud Shell in a separate browser tab by going to [https://shell.azure.com/cli](https://shell.azure.com/cli). Select **Copy** to copy the blocks of code, paste it into the Cloud Shell, and press enter to run it.
+
+## Prerequisites
+
+- If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
+- Before using Compute Fleet, complete the feature registration and configure role-based access controls (RBAC). 
+
+## Feature registration
+
+Register the Azure Compute Fleet resource provider with your subscription using Azure CLI. Registration can take up to 30 minutes to successfully show as registered.
+
+```azurecli-interactive
+az provider register --namespace 'Microsoft.AzureFleet'
+```
+
+## Define environment variables
+
+Define environment variables as follows.
+
+```bash
+export RANDOM_ID="$(openssl rand -hex 3)"
+export MY_RESOURCE_GROUP_NAME="myFleetResourceGroup$RANDOM_ID"
+export REGION=EastUS
+export MY_FLEET_NAME="myFleet$RANDOM_ID"
+export MY_USERNAME=azureuser
+export MY_VNET_NAME="myVNet$RANDOM_ID"
+export NETWORK_PREFIX="$(($RANDOM % 254 + 1))"
+export MY_VNET_PREFIX="10.$NETWORK_PREFIX.0.0/16"
+export MY_VM_SN_NAME="myVMSN$RANDOM_ID"
+export MY_VM_SN_PREFIX="10.$NETWORK_PREFIX.0.0/24"
+```
+
+## Create a resource group
+
+A resource group is a logical container into which Azure resources are deployed and managed. All resources must be placed in a resource group. The following command creates a resource group with the previously defined `$MY_RESOURCE_GROUP_NAME` and `$REGION` parameters.
+
+```azurecli-interactive
+az group create --name $MY_RESOURCE_GROUP_NAME --location $REGION
+```
+
+## Create virtual network and subnet
+
+Now you'll create a virtual network using the previously defined `$MY_VNET_PREFIX`, `$MY_VM_SN_NAME`, and `$MY_VM_SN_PREFIX` parameters.
+
+```azurecli-interactive
+az network vnet create  --name $MY_VNET_NAME  --resource-group $MY_RESOURCE_GROUP_NAME --location $REGION  --address-prefix $MY_VNET_PREFIX  --subnet-name $MY_VM_SN_NAME --subnet-prefix $MY_VM_SN_PREFIX
+```
+
+The following command gets the subnet ARM ID.
+
+```azurecli-interactive
+export MY_SUBNET_ID="$(az network vnet subnet show \
+  --resource-group $MY_RESOURCE_GROUP_NAME \
+  --vnet-name $MY_VNET_NAME \
+  --name $MY_VM_SN_NAME \
+  --query id --output tsv)"
+```
+
+## Set up the admin password
+
+Set up a password that meets the [password requirements for Azure VMs](https://learn.microsoft.com/azure/virtual-machines/windows/faq#what-are-the-password-requirements-when-creating-a-vm-).
+
+```bash
+export ADMIN_PASSWORD="Azure compliant password"
+```
+
+## Create a Compute Fleet
+
+Set up the compute profile which is applied to the underlying VMs.
+
+```bash
+export COMPUTE_PROFILE="{ 'baseVirtualMachineProfile': { 'storageProfile': { 'imageReference': { 'publisher':'canonical', 'offer':'0001-com-ubuntu-server-focal', 'sku': '20_04-lts-gen2', 'version': 'latest' } }, 'osProfile': { 'computerNamePrefix': 'vm', 'adminUsername': '$MY_USERNAME', 'adminPassword': '$ADMIN_PASSWORD'}, 'networkProfile': { 'networkInterfaceConfigurations': [{ 'name': 'nic', 'primary': 'true', 'enableIPForwarding': 'true', 'ipConfigurations': [{ 'name': 'ipc', 'subnet': { 'id': '$MY_SUBNET_ID' } }] }], 'networkApiVersion': '2020-11-01'} } }"
+```
+ 
+```azurecli-interactive
+az compute-fleet create --name $MY_FLEET_NAME --resource-group $MY_RESOURCE_GROUP_NAME --location $REGION \
+    --spot-priority-profile "{ 'capacity': 5 }" \
+    --regular-priority-profile "{ 'capacity': 5 }" \
+    --compute-profile "$COMPUTE_PROFILE" \
+    --vm-sizes-profile "[{ 'name': 'Standard_F1s' }]"
+```
+
+## Clean up resources (optional)
+
+To avoid Azure charges, you should clean up unneeded resources. When you no longer need your Compute Fleet and other resources, delete the resource group and all its resources with [az group delete](/cli/azure/group). The `--no-wait` parameter returns control to the prompt without waiting for the operation to complete. The `--yes` parameter confirms that you wish to delete the resources without another prompt to do so.
+
+## Next steps
+> [!div class="nextstepaction"]
+> [Learn how to modify a Compute Fleet.](modify-fleet.md)

articles/azure-functions/durable/TOC.yml

@@ -116,7 +116,7 @@
     href: ./durable-task-scheduler/durable-task-scheduler.md
   - name: Choosing an orchestration framework
     href: ./durable-task-scheduler/choose-orchestration-framework.md
-  - name: Create Durable Task Scheduler resources
+  - name: Develop with Durable Task Scheduler
     href: ./durable-task-scheduler/develop-with-durable-task-scheduler.md
   - name: Identity
     href: ./durable-task-scheduler/durable-task-scheduler-identity.md

articles/azure-functions/durable/durable-functions-mssql-container-apps-hosting.md

@@ -5,7 +5,7 @@ ms.topic: how-to
 ms.date: 05/06/2025
 ---
 
-# Host a Durable Functions app in Azure Container Apps 
+# Host a Durable Functions app in Azure Container Apps (.NET isolated)
 
 Azure Functions provides integrated support for developing, deploying, and managing containerized Function Apps on Azure Container Apps. Use Azure Container Apps for your Functions apps when you need to run in the same environment as other microservices, APIs, websites, workflows, or any container hosted programs. Learn more about [running Azure Functions in Container Apps](../../container-apps/functions-overview.md). 
 
@@ -163,7 +163,6 @@ A [workload profile](../functions-container-apps-hosting.md#hosting-and-workload
       --resource-group $resourceGroup \
       --name $containerAppEnv \
       --location $location \
-      --infrastructure-subnet-resource-id $subnetId
     ```
 
 1. Create a container app based on the Durable Functions image.
@@ -178,7 +177,7 @@ A [workload profile](../functions-container-apps-hosting.md#hosting-and-workload
     --query properties.outputs.fqdn
     ```
 
-1. Make note of the app URL, which should look similar to `https://<APP_NAME>.victoriouswave-3866c33e.<REGION>.azurecontainerapps.io`.
+1. Make note of the app URL, which should look similar to `https://<APP_NAME>.<ENVIRONMENT_IDENTIFIER>.<REGION>.azurecontainerapps.io`.
 
 ### Create databases
 
@@ -235,22 +234,22 @@ In this section, you set up **user-assigned managed identity** for Azure Storage
     clientId=$(az identity show --name $identity --resource-group $resourceGroup --query 'clientId' --output tsv)
     ```
 
-1. Assign the role `Storage Blob Data Owner` role for access to the storage account. 
+1. Assign the role **Storage Blob Data Owner** role for access to the storage account. 
 
     ```azurecli
     echo "Assign Storage Blob Data Owner role to identity"
     az role assignment create --assignee "$clientId" --role "Storage Blob Data Owner" --scope "$scope"
     ```
 
 ### Set up app settings
-
-Authenticating to the MSSQL database using managed identity isn't supported when hosting a Durable Functions app in Azure Container Apps. For now, this guide authenticates using connection strings.
+> [!NOTE]
+> Authenticating to the MSSQL database using managed identity isn't supported when hosting a Durable Functions app in Azure Container Apps. For now, this guide authenticates using connection strings.
 
 1. From the SQL database resource in the Azure portal, navigate to **Settings** > **Connection strings** to find the connection string.
 
     :::image type="content" source="./media/quickstart-mssql/mssql-azure-db-connection-string.png" alt-text="Screenshot showing database connection string.":::
 
-    The connection string should be a format similar to: 
+    The connection string should have a format similar to: 
 
     ```bash
     dbserver=<SQL_SERVER_NAME>