Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: Create an Azure Compute Fleet using an ARM template description: Learn how to create an Azure Compute Fleet using an ARM template. author: fitzgeraldsteele ms.author: fisteele ms.topic: how-to ms.service: azure-compute-fleet ms.date: 07/20/2026 ms.reviewer: wwilliams ms.custom: devx-track-arm-template, build-2024 # Customer intent: "As a cloud engineer, I want to create an Azure Compute Fleet using an ARM template, so that I can automate the deployment and management of scalable virtual machine resources." --- # Create an Azure Compute Fleet using an ARM template This article steps through using an ARM template to create an Azure Compute Fleet. [!INCLUDE [About Azure Resource Manager](~/reusable-content/ce-skilling/azure/includes/resource-manager-quickstart-introduction.md)] ## Prerequisites - If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn) 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 PowerShell or Azure portal. Registration can take up to 30 minutes to successfully show as registered. ### [PowerShell](#tab/powershell-1) ```azurepowershell-interactive Register-AzResourceProvider -ProviderNamespace Microsoft.AzureFleet ``` ### [Azure portal](#tab/portal-1) 1. In the [Azure portal](https://portal.azure.com), navigate to your subscriptions. 1. Select the subscription you want to enable Azure Compute Fleet on. 1. Under **Settings**, select **Resource providers**. 1. Search for *Microsoft.AzureFleet* and register the provider. --- ## Role-based access control permissions Assign the appropriate RBAC permissions to use Azure Compute Fleet. 1. In the [Azure portal](https://portal.azure.com), navigate to your subscriptions. 1. Select the subscription you want to adjust RBAC permissions. 1. Select **Access Control (IAM)**. 1. Select *Add*, then **Add Role Assignment**. 1. Search for **Virtual Machine Contributor** and highlight it. Select **Next**. 1. Click on **+ Select Members**. 1. Search for *Azure Fleet Resource Provider* role. 1. Select the *Azure Fleet Resource Provider* and select **Review + Assign**. 1. Repeat the previous steps for the *Network Contributor* role and the *Managed Identity Operator* role. If you're using images stored in Compute Gallery when deploying your Compute Fleet, also repeat the previous steps for the *Compute Gallery Sharing Admin* role. For more information on assigning roles, see [assign Azure roles using the Azure portal](../role-based-access-control/quickstart-assign-role-user-portal.md). ## ARM template [!INCLUDE [About Azure Resource Manager](~/reusable-content/ce-skilling/azure/includes/resource-manager-quickstart-introduction.md)] ARM templates let you deploy groups of related resources. In a single template, you can create the Virtual Machine Scale Set, install applications, and configure autoscale rules. With the use of variables and parameters, this template can be reused to update existing, or create extra scale sets. You can deploy templates through the Azure portal, Azure CLI, or Azure PowerShell, or from continuous integration / continuous delivery (CI/CD) pipelines. ## Review the template ```armasm { "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#", "contentVersion": "1.0.0.0", "parameters": { "fleetName": { "type": "string", "metadata": { "description": "String used as a base for naming resources. Must be 3-61 characters in length and globally unique across Azure. A hash is prepended to this string for some resources, and resource-specific information is appended." } }, "adminUsername": { "type": "string", "defaultValue": "testusername", "metadata": { "description": "Admin username on all VMs." } }, "adminPassword": { "type": "string", "metadata": { "description": "Admin password on all VMs." } }, "location": { "type": "string", "defaultValue": "[resourceGroup().location]", "metadata": { "description": "Location for all resources." } } }, "variables": { "vnName": "[format('{0}-vnet', parameters('fleetName'))]", "lbName": "[format('{0}-lb', parameters('fleetName'))]", "imageReference": { "publisher": "MicrosoftWindowsServer", "offer": "WindowsServer", "sku": "2019-DataCenter-GS", "version": "latest" } }, "resources": [ { "type": "Microsoft.Network/virtualNetworks", "apiVersion": "2022-07-01", "name": "[variables('vnName')]", "location": "[parameters('location')]", "properties": { "addressSpace": { "addressPrefixes": [ "10.0.0.0/16" ] }, "subnets": [ { "name": "default", "properties": { "addressPrefix": "10.0.0.0/24" } } ] } }, { "type": "Microsoft.Network/loadBalancers", "apiVersion": "2022-07-01", "name": "[variables('lbName')]", "location": "[parameters('location')]", "sku": { "name": "Standard" }, "properties": { "frontendIPConfigurations": [ { "name": "[variables('lbName')]", "properties": { "privateIPAddress": "10.0.0.4", "privateIPAllocationMethod": "Dynamic", "subnet": { "id": "[reference(resourceId('Microsoft.Network/virtualNetworks', variables('vnName'))).subnets[0].id]" } } } ], "backendAddressPools": [ { "name": "[variables('lbName')]" } ] }, "dependsOn": [ "[resourceId('Microsoft.Network/virtualNetworks', variables('vnName'))]" ] }, { "type": "Microsoft.AzureFleet/fleets", "apiVersion": "2024-05-01-Preview", "name": "[toLower(parameters('fleetName'))]", "location": "[parameters('location')]", "properties": { "vmSizesProfile": [ { "name": "Standard_F2s_v2" }, { "name": "Standard_DS1_v2" }, { "name": "Standard_DS2_v2" } ], "spotPriorityProfile": { "capacity": 10, "evictionPolicy": "Delete", "allocationStrategy": "CapacityOptimized", "maintain": false }, "regularPriorityProfile": { "capacity": 50, "minCapacity": 30, "allocationStrategy": "LowestPrice" }, "computeProfile": { "platformFaultDomainCount": 1, "computeApiVersion": "2024-03-01", "baseVirtualMachineProfile": { "storageProfile": { "osDisk": { "osType": "Windows", "createOption": "fromImage", "caching": "ReadWrite", "managedDisk": { "storageAccountType": "Standard_LRS" } }, "imageReference": "[variables('imageReference')]" }, "osProfile": { "computerNamePrefix": "[parameters('fleetName')]", "adminUsername": "[parameters('adminUsername')]", "adminPassword": "[parameters('adminPassword')]" }, "networkProfile": { "networkApiVersion": "2022-07-01", "networkInterfaceConfigurations": [ { "name": "[variables('vnName')]", "properties": { "primary": true, "enableIPForwarding": true, "enableAcceleratedNetworking": false, "ipConfigurations": [ { "name": "[variables('vnName')]", "properties": { "subnet": { "id": "[reference(resourceId('Microsoft.Network/virtualNetworks', variables('vnName'))).subnets[0].id]" }, "primary": true, "applicationGatewayBackendAddressPools": [], "loadBalancerBackendAddressPools": [ { "id": "[format('{0}/backendAddressPools/{1}', resourceId('Microsoft.Network/loadBalancers', variables('lbName')), variables('lbName'))]" } ] } } ] } } ] } } } }, "dependsOn": [ "[resourceId('Microsoft.Network/virtualNetworks', variables('vnName'))]", "[resourceId('Microsoft.Network/loadBalancers', variables('lbName'))]" ] } ] } ``` These resources are defined in the template: - [**Microsoft.Network/virtualNetworks**](/azure/templates/microsoft.network/virtualnetworks) - [**Microsoft.Network/loadBalancers**](/azure/templates/microsoft.network/loadbalancers) ## Create a fleet in Launch mode (Preview) To create a fleet in [Launch mode (Preview)](launch-mode.md), set `mode` to `Launch` in the fleet `properties` and use the `2026-04-01-preview` API version. In Launch mode, the fleet provisions the VMs and then hands off control; the fleet object self-deletes a few hours later while the VMs persist. The following snippet shows the Launch mode additions to the `Microsoft.AzureFleet/fleets` resource. The `vmNamePrefix` property gives the provisioned VMs orchestrator-friendly names and requires the `2026-04-01-preview` API version. ```json { "type": "Microsoft.AzureFleet/fleets", "apiVersion": "2026-04-01-preview", "name": "[toLower(parameters('fleetName'))]", "location": "[parameters('location')]", "zones": [ "1", "2", "3" ], "properties": { "mode": "Launch", "vmNamePrefix": "myapp", "vmSizesProfile": [ { "name": "Standard_D2s_v3" }, { "name": "Standard_D4s_v3" }, { "name": "Standard_E2s_v3" } ], "regularPriorityProfile": { "capacity": 50, "allocationStrategy": "LowestPrice" }, "spotPriorityProfile": { "capacity": 50, "allocationStrategy": "CapacityOptimized" }, "computeProfile": { "computeApiVersion": "2024-03-01", "baseVirtualMachineProfile": { "storageProfile": { "...": "..." }, "osProfile": { "...": "..." }, "networkProfile": { "...": "..." } } } } } ``` In Launch mode, don't set the `spotPriorityProfile.maintain` preference - it applies only to Managed mode. Because provisioning is asynchronous, use the [List VMs API](launch-mode.md#retrieve-and-monitor-vms) to retrieve the VM resource IDs and monitor provisioning status after the deployment is submitted. > [!IMPORTANT] > Launch mode for Azure Compute Fleet is currently in preview. For more information, see [Launch mode for Azure Compute Fleet (Preview)](launch-mode.md). ## Clean up resources When no longer needed, you can use [az group delete](/cli/azure/group) to remove the resource group, scale set, and all related resources as follows. 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. ```azurecli-interactive az group delete --name myResourceGroup --yes --no-wait ``` ## Next steps > [!div class="nextstepaction"] > [Create an Azure Compute Fleet with Azure portal.](quickstart-create-portal.md)