Merge pull request #299625 from MicrosoftDocs/main

5/9/2025 PM Publish

Author: Taojunshen

articles/application-gateway/high-traffic-support.md

@@ -42,6 +42,9 @@ Make sure to check your subnet size and available IP address count in your subne
 
 :::image type="content" source="./media/application-gateway-covid-guidelines/v2-autoscaling-max-instances-inline.png" alt-text="V2 autoscaling configuration" lightbox="./media/application-gateway-covid-guidelines/v2-autoscaling-max-instances-exp.png":::
 
+> [!NOTE]
+> If your traffic requirement needs more than 125 instances, you can use Azure Traffic Manager or Azure Front Door in front of your Application Gateway. For more information, please see [Connect Azure Front Door Premium to an Azure Application Gateway with Private Link](../frontdoor/how-to-enable-private-link-application-gateway.md) and [Use Azure App Gateway with Azure Traffic Manager](../traffic-manager/traffic-manager-use-with-application-gateway.md)
+
 ### Set your minimum instance count based on your average Compute Unit usage
 
 For Application Gateway v2 SKU, autoscaling takes three to five minutes to scale out and provision additional set of instances ready to take traffic. Until then, if there are short spikes in traffic, your existing gateway instances might get under stress and this may cause unexpected latency or loss of traffic. 

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/durable-functions-mssql-container-apps-hosting.md

@@ -5,9 +5,12 @@ ms.topic: how-to
 ms.date: 05/06/2025
 ---
 
-# Host a Durable Functions app in Azure Container Apps (preview)
+# Host a Durable Functions app in Azure Container Apps (.NET isolated)
 
-While Durable Functions supports several [storage providers](./durable-functions-storage-providers.md) or *backends*, autoscaling apps hosted in Azure Container Apps is only available with the Microsoft SQL (MSSQL) backend. If another backend is used, you need to [manually set up scaling](../functions-container-apps-hosting.md#event-driven-scaling).
+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). 
+
+> [!NOTE] 
+> While Durable Functions supports several [storage providers](./durable-functions-storage-providers.md) or *backends*, autoscaling apps hosted in Azure Container Apps is only available with the [Microsoft SQL (MSSQL) backend](../../container-apps/functions-overview.md#event-driven-scaling). If another backend is used, you have to set minimum replica count to greater than zero. 
 
 In this article, you learn how to:
 
@@ -78,7 +81,7 @@ Build the Docker image. Find the complete list of supported base images for Azur
 
 1. When prompted, log in with your username and password. A "Login Succeeded" message confirms that you're signed in.
 
-1. Navigate to the `LocalFunctionProj` project folder. 
+1. Navigate to your project root directory. 
 
 1. Run the following command to build the image, replacing `<DOCKER_ID>` with your Docker Hub account ID:
 
@@ -87,7 +90,7 @@ Build the Docker image. Find the complete list of supported base images for Azur
     imageName=IMAGE_NAME>
     imageVersion=v1.0.0
 
-    docker build --platform linux --tag $dockerId/$imageName:$imageVersion .
+    docker build --tag $dockerId/$imageName:$imageVersion .
     ```
 
     > [!NOTE]
@@ -108,7 +111,6 @@ Create the Azure resources necessary for running Durable Functions on a containe
 - **Azure Container App environment:** Environment hosting the container app. 
 - **Azure Container App:** Image containing the Durable Functions app is deployed to this app. 
 - **Azure Storage Account:** Required by the function app to store app-related data, such as application code. 
-- **A virtual network:** Required by the Azure Container App environment. 
 
 ### Initial set up
 
@@ -117,7 +119,7 @@ Create the Azure resources necessary for running Durable Functions on a containe
     ```azurecli
     az login  
 
-    az account set -subscription | -s <subscription_name>
+    az account set -s <subscription_name>
     ```
 
 1. Run the required commands to set up the Azure Container Apps CLI extension:
@@ -153,34 +155,6 @@ A [workload profile](../functions-container-apps-hosting.md#hosting-and-workload
     az group create --name $resourceGroup --location $location
     ```
 
-1. Create a virtual network, which is required for a container app environment.
-
-    ```azurecli
-    az network vnet create --resource-group $resourceGroup --name $vnet --location $location --address-prefix 10.0.0.0/16
-    ```
-
-1. Create a subnet for the environment deployment.
-
-    ```azurecli
-    az network vnet subnet create \
-      --resource-group $resourceGroup \
-      --vnet-name $vnet \
-      --name infrastructure-subnet \
-      --address-prefixes 10.0.0.0/23
-    ```
-
-1. Run the following query to get the subnet ID.
-
-    ```azurecli
-    subnetId=$(az network vnet subnet show --resource-group $resourceGroup --vnet-name $vnet --name infrastructure-subnet --query "id" -o tsv | tr -d '[:space:]')
-    ```
-
-1. Delegate the subnet to `Microsoft.App/environments`.
-
-    ```azurecli
-    az network vnet subnet update --resource-group $resourceGroup --vnet-name $vnet --name infrastructure-subnet --delegations Microsoft.App/environments
-    ```
-
 1. Create the container app environment.
 
     ```azurecli
@@ -189,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.
@@ -200,14 +173,11 @@ A [workload profile](../functions-container-apps-hosting.md#hosting-and-workload
     --environment $containerAppEnv \
     --image $dockerId/$imageName:$imageVersion \
     --ingress external \
-    --allow-insecure \
-    --target-port 80 \
-    --transport auto \
     --kind functionapp \
     --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
 
@@ -264,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>
@@ -297,11 +267,9 @@ Authenticating to the MSSQL database using managed identity isn't supported when
 1. Store the SQL database's connection string as a [secret](../../container-apps/manage-secrets.md) called *sqldbconnection* in the container app.
 
     ```azurecli
-    az containerapp create \
+    az containerapp secret set \
     --resource-group $resourceGroup \
     --name $functionApp \
-    --environment $containerAppEnv \
-    --image $dockerId/$imageName:$imageVersion \
     --secrets sqldbconnection=$connStr
     ```
 
@@ -323,7 +291,7 @@ Authenticating to the MSSQL database using managed identity isn't supported when
 1. Use an HTTP test tool to send a `POST` request to the HTTP trigger endpoint, which should be similar to: 
 
     ```
-    https://<APP NAME>.victoriouswave-3866c33e.<REGION>.azurecontainerapps.io/api/DurableFunctionsOrchestrationCSharp1_HttpStart
+    https://<APP NAME>.<ENVIRONMENT_IDENTIFIER>.<REGION>.azurecontainerapps.io/api/DurableFunctionsOrchestrationCSharp1_HttpStart
     ```
 
    The response is the HTTP function's initial result letting you know that the Durable Functions orchestration started successfully. While the response includes a few useful URLs, it doesn't yet display the orchestration's end result.
@@ -348,6 +316,6 @@ Authenticating to the MSSQL database using managed identity isn't supported when
 ## Next steps
 
 Learn more about:
-- [Azure Container Apps hosting of Azure Functions](../functions-container-apps-hosting.md). 
+- [Azure Container Apps hosting of Azure Functions](../../container-apps/functions-overview.md). 
 - [MSSQL storage provider](https://microsoft.github.io/durabletask-mssql/) architecture, configuration, and workload behavior. 
 - The Azure-managed storage backend, [Durable Task Scheduler](./durable-task-scheduler/durable-task-scheduler.md).