Phase 05: Cluster Deployment
DOCUMENT CATEGORY: Runbook
SCOPE: Azure Local cluster deployment
PURPOSE: Deploy the cluster through Azure Portal or ARM templates
MASTER REFERENCE: Microsoft Learn - Deploy Azure Local
Status: Active
Estimated Time: 1.5-3 hours (Learn gives 2.5-3 hours for the ARM deployment itself)
Last Updated: 2026-11-08 (verified against Microsoft Learn view=azloc-2610)
Overview
This stage deploys the Azure Local cluster using the configured infrastructure. Deployment can be performed through the Azure Portal (GUI-based) or ARM templates (infrastructure-as-code). Azure Local Cloud supports both Active Directory and Local Identity authentication methods.
Every machine needs its OS steps done first: OEM drivers and SBE, one static management address with one default gateway, DNS and time. Which ones you run yourself depends on your route; see the decision matrix. Check Microsoft Learn and your OEM's deployment guide for your build.
Simplified provisioning: pass each machine's arcMachineResourceId from Azure (named <device-id>-1), and read the known issue with Arc machine names at Deploy before you deploy.
Automated route. The toolkit's ARM run (Invoke-AzureLocalArmDeployment.ps1) refuses to Validate or Deploy without a passing, current result of the pre-cluster verification gate (Invoke-AzureLocalPreClusterVerification.ps1) for the same infrastructure file. Run the gate after the OS configuration, by hand or with its pipeline (pipelines/github-actions/pre-cluster-verification.yml, pipelines/gitlab/stages/pre-cluster-verification.yml, pipelines/azure-devops/pre-cluster-verification.yml). The pipeline fails when the verdict is not Pass.
Deployment Methods
Storage Spaces Direct (S2D) — Hyperconverged
| Method | Authentication | Use Case |
|---|---|---|
| Portal - Active Directory | Domain-joined | Standard enterprise deployment |
| ARM Template - Active Directory | Domain-joined | Automated/repeatable deployment |
| Portal - Local Identity | Local accounts | Edge/disconnected scenarios |
| ARM Template - Local Identity | Local accounts | Automated edge deployment |
Storage Area Network (SAN) — Disaggregated
| Method | Authentication | Use Case |
|---|---|---|
| Portal - Active Directory (SAN) | Domain-joined | SAN with enterprise AD |
| ARM Template - Active Directory (SAN) | Domain-joined | SAN with automated deployment |
| Portal - Local Identity (SAN) | Local accounts | SAN at edge without AD |
| ARM Template - Local Identity (SAN) | Local accounts | SAN with automated edge |
- S2D (Hyperconverged): Local NVMe/SSD/HDD in each node, up to 16 nodes. Compute and storage scale together.
- SAN (Disaggregated): External SAN via Fibre Channel or iSCSI, up to 64 nodes. Compute and storage scale independently. See SAN Deployment for prerequisites and network patterns.
- Hybrid (S2D + SAN): a SAN attached to a hyperconverged cluster after initial deployment (version 2604 or later). It is a day-2 operation, see Connect an external storage array to Azure Local.
For Azure Local Cloud Azure Local deployments, Active Directory with ARM Template is the recommended approach for consistency and repeatability.
Prerequisites
All Deployment Methods
| Requirement | Validation |
|---|---|
| Arc registration complete (Phase 04) | All nodes show "Connected" in Azure Portal |
| Network infrastructure configured | Management, storage, and compute networks ready |
| Required Azure permissions | Subscription: user access administrator and contributor. Resource group used for the Arc machines: Azure Stack HCI Administrator, Reader, Key Vault Data Access Administrator, Key Vault Secrets Officer, Key Vault Contributor, Storage Account Contributor, plus Azure Connected Machine Onboarding and Azure Connected Machine Resource Administrator |
| Storage infrastructure ready | S2D: physical disks clean and enclosures configured. SAN: infrastructure LUN (250 GB or more) and performance history LUN (20 GB or more) visible and RAW |
Active Directory Deployments Only
| Requirement | Validation |
|---|---|
AD pre-created with New-HciAdObjectsPreCreation | OU exists, LCM user created in OU, GPO inheritance blocked at OU level |
| Nodes in workgroup (default) or domain-joined before deployment (optional, 2604 and later) | (Get-WmiObject Win32_ComputerSystem).Domain returns WORKGROUP, or the domain name if you joined first. If domain-joined, the deployment user is in the local Administrators group. If not joined, the wizard joins the machines to the domain during deployment |
| DNS resolves the AD domain FQDN from all nodes | Resolve-DnsName <domain.fqdn> succeeds on each node |
Local Identity Deployments Only
| Requirement | Validation |
|---|---|
| Non-built-in local admin account with identical credentials on ALL nodes | Account is NOT the built-in Administrator; login succeeds on each node |
| Nodes remain in workgroup | (Get-WmiObject Win32_ComputerSystem).Domain returns WORKGROUP |
| Azure Key Vault available | Existing KV accessible (an existing Key Vault with Private Endpoints is not supported), or will be created during portal deployment |
| DNS server with zone configured for cluster nodes | Resolve-DnsName <node-fqdn> succeeds for each node |
Deployment Workflow
graph TD
A[Start Deployment] --> B{Authentication Type?}
B -->|Active Directory| C[AD Pre-checks]
B -->|Local Identity| D[Local Admin Setup]
C --> E{Deployment Method?}
D --> E
E -->|Portal| F[Portal Wizard]
E -->|ARM Template| G[ARM Deployment]
F --> H[Validation]
G --> H
H --> I{Deployment Successful?}
I -->|Yes| J[Phase 16: Post-Deployment]
I -->|No| K[Troubleshooting]
K --> E
Azure Portal Deployment Overview
The Azure Portal deployment wizard guides you through:
- Basics - Subscription, resource group, cluster name, region
- Configuration - Node configuration, witness, and storage settings
- Networking - Management, compute, and storage network settings
- Management - Update settings, key vault integration
- Tags - Resource tagging for governance
- Validation - Pre-deployment checks
- Review + Create - Final review and deployment
ARM Template Deployment Overview
ARM template deployments provide:
- Repeatability - Consistent deployments across environments
- Version Control - Track infrastructure changes in Git
- Automation - Integrate with CI/CD pipelines
- Compliance - Audit trail of infrastructure changes
The Azure Local Toolkit keeps no parameter file to fill in by hand. The parameters of a deployment are built from infrastructure.yml: New-AzureLocalArmParameters.ps1 writes the full parameter file for the design of the file (Active Directory or local identity, Storage Spaces Direct or a SAN, rack aware), and Invoke-AzureLocalArmDeployment.ps1 builds the same parameters and runs the deployment. parameter-sources.md in the report directory shows which key fed each parameter.
Toolkit location: config/azure/arm-templates/
template-parameters.json— the parameters of each Microsoft quickstart template the toolkit can selectparameter-sources.json— whichinfrastructure.ymlkeys feed which ARM parameterexamples/*.parameters.json— example parameter files generated from the toolkit's example infrastructure files byconfig/variables/scripts/New-ArmParameterExample.ps1(do not edit them)
The earlier hand-filled parameter files are gone. Microsoft's copy of the create-cluster template is now a test fixture (tests/fixtures/arm/microsoft-create-cluster/), read only by the tests.
Microsoft official templates: Pull at deploy time from the Azure Quickstart Templates repository. Do not modify the main template — customize only via the parameters file. Template per scenario (Learn 2610):
| Scenario | Quickstart template |
|---|---|
| S2D, Active Directory | azurestackhci/create-cluster |
| Local identity (hyperconverged) | azurestackhci/create-adless-cluster-external-dns-public-preview |
| Disaggregated, Fibre Channel | azurestackhci/create-cluster-san |
| Disaggregated, iSCSI | azurestackhci/create-cluster-san-iscsi |
Learn documents no ARM template for SAN plus local identity.
Starting with software version 12.2512, new deployments no longer create a Microsoft Entra ID application (service principal). The cluster authenticates to Azure with a system-assigned managed identity.
Estimated Deployment Time
| Phase | Duration |
|---|---|
| Pre-deployment validation | 15-30 minutes |
| Cluster deployment | 45-90 minutes |
| Extension installation | 15-30 minutes |
| Post-deployment validation | 15-30 minutes |
| Total | 1.5-3 hours |
Next Steps
Select your deployment method:
S2D (Hyperconverged)
| Authentication | Method | Link |
|---|---|---|
| Active Directory | Portal | Portal Instructions |
| Active Directory | ARM Template | ARM Template Instructions |
| Local Identity | Portal | Portal Instructions |
| Local Identity | ARM Template | ARM Template Instructions |
SAN (Disaggregated)
| Authentication | Method | Link |
|---|---|---|
| Active Directory | Portal | Portal Instructions (SAN) |
| Active Directory | ARM Template | ARM Template Instructions (SAN) |
| Local Identity | Portal | Portal Instructions (SAN) |
| Local Identity | ARM Template | ARM Template Instructions (SAN) |
After completing cluster deployment, proceed to Phase 16: Post Deployment.
Navigation
| Previous | Up | Next |
|---|---|---|
| Phase 14: Arc Registration | Cluster Deployment Index | Phase 16: Post-Deployment |
References: