Active Directory - ARM Template Deployment (SAN)
Deploy a disaggregated Azure Local cluster with Active Directory authentication and SAN storage using ARM templates
Deploy a disaggregated Azure Local cluster with Active Directory authentication and SAN storage using ARM templates
Deploy a disaggregated Azure Local cluster with Active Directory authentication and SAN storage using the Azure Portal
Deploy Azure Local cluster with Active Directory authentication using the Azure Portal
Fibre Channel fabric configuration reference — Brocade and Cisco MDS zoning, alias creation, zoneset activation
Fibre Channel fabric maintenance reference — firmware update, port replacement, fabric merge/split
ARM template-based Azure Local cluster deployment options for Active Directory and Local Identity environments.
One command, from a jump server or a pipeline, that checks readiness, validates, waits for approval, deploys the Azure Local instance with Microsoft's ARM template and explains failures; where the pre-cluster verification gate sits before it.
Authentication options for Azure Local deployment — Azure PowerShell and Azure CLI session setup.
Configure every node's OS in one run with the azurelocal-toolkit: standalone or from a GitHub or GitLab pipeline, with method detection, plan, approval, apply and verify, the master-file keys it reads, clear_storage, exit codes and troubleshooting.
What you need before running the azurelocal-ztp automation: Azure subscription settings and roles, hardware and BMC, network paths, and the Windows management host.
Complete guide for deploying Azure Local infrastructure — from Azure foundation through cluster deployment, validation, and handover.
Two routes lead to the same Azure Local cluster deployment. A flow chart and a decision matrix show which OS installation, OS configuration and Arc registration steps each route needs before Validate.
Runbook for deploying Azure Local clusters, covering OS installation, Arc registration, cluster creation, and post-deployment configuration.
Overview of Azure Local cluster deployment methods including Portal and ARM Template options for Active Directory and Local Identity environments.
Watch Azure Local cluster validation and deployment progress with Azure Local Sonar
Overview of the full CAF/WAF landing zone deployment — enterprise-scale management group hierarchy, dedicated subscriptions, and multi-resource-group organization following Azure Landing Zone architecture.
Every step of the automated OS configuration run in the order it executes: what is read first, what counts as a change, the idempotent re-run, the restart points, the three management address modes, the SAN-only steps, the SBE route, the retry on state Unknown, per-node continue on failure and the plan, approval, apply and verify stages.
Explain how to navigate the automation guide and combine it with the implementation guide.
Detailed provisioning instructions with tabbed execution options for each step.
How Azure Local deployments are configured: one infrastructure.yml (schema 5), defined by the master registry, validated by a schema.
Status of ARM template deployment for a disaggregated Azure Local cluster with local identity and SAN storage: not documented by Microsoft for 2610
Deploy a disaggregated Azure Local cluster with local identity authentication and SAN storage using the Azure Portal
Deploy Azure Local cluster with local identity authentication using the Azure Portal and Key Vault
Management server definitions — domain controllers, jumpbox, WAC, and syslog server. Deployment-agnostic variable capture.
Manual step-by-step deployment procedures for Azure Local management infrastructure components
Install the Azure Stack HCI OS from the ISO or your OEM's image on each node through the BMC console: prepare the boot disk, mount the image, install, and verify.
Watch Azure Local cluster deployment progress with Azure Local Sonar
Follow a zero-touch provisioning run live and read-only with azurelocal-sonar, from the virtual USB boot to ready for Validate, and on through cluster Validate and Deploy.
Watch Azure Local cluster validation progress with Azure Local Sonar
On-Premises Readiness for Azure Local Deployments
The two things the operator supplies to the azurelocal-ztp automation: the environment file and the folder of OEM Solution Builder Extension files.
What the azurelocal-ztp automation produces at the Handoff, and what to give OS configuration and cluster deployment, including each machine's arcMachineResourceId and the management address result.
Prepare Active Directory domain infrastructure including OU structure, service accounts, and group policies for Azure Local deployment
Discover cluster node hardware, configure DHCP reservations, validate and remediate BIOS/iDRAC settings against Dell Azure Local validated baselines before OS installation.
Phase 01: Landing Zones — choose your deployment model and deploy management groups, subscriptions, and resource groups following Azure CAF/WAF and Azure Landing Zone architecture.
Validate customer network infrastructure prerequisites before Azure Local deployment
Install the Azure Stack HCI OS on cluster nodes by one of two paths: manual installation from an ISO or OEM image, or simplified machine provisioning (preview), by hand or automated with azurelocal-ztp.
Phase 02: Register required Azure resource providers for Azure Local deployment.
Configure network infrastructure including OpenGear, switches, and firewall endpoints for Azure Local deployment
Configure RBAC permissions and create deployment service principal for Azure Local
Deploy Azure management infrastructure for Azure Local including networking, VPN connectivity, management VMs, and monitoring resources.
Configure Privileged Identity Management and Conditional Access policies to protect administrative access to the Azure Local deployment.
Portal-based Azure Local cluster deployment options for Active Directory and Local Identity environments.
Requirements and assumptions for Azure Local deployment.
Define the scope, deployment paths, and reader expectations for the automation guide.
Comprehensive guidance for deploying Azure Local infrastructure with multiple implementation approaches.
Run the day 2 scripts of Part 8 by hand, or in the day 2 pipelines on GitHub Actions, GitLab CI or Azure DevOps: a scheduled check for updates, the update, node maintenance and cluster operations, each change behind one approval
Run the azurelocal-ztp zero-touch automation from a pipeline on a self-hosted Windows runner: why self-hosted, identity and roles, Key Vault secrets, a manual approval before the Boot stage, and resume with -From.
Plan, run, watch and resume the azurelocal-ztp zero-touch automation from a Windows management host.
Run the four validation checks of Part 7 by hand, or in the validation pipeline on GitHub Actions, GitLab CI or Azure DevOps, with the storage load test behind an approval
Deploy Azure Local using Storage Area Network (SAN) external storage — disaggregated architecture with independent scaling of compute and storage.
Install the OS and register Azure Local machines using simplified machine provisioning — an alternative to manual ISO installation that automates OS deployment from Azure.
Overview of the single subscription landing zone deployment — single management group, single subscription, single resource group.
Storage architecture decision guide for Azure Local deployments: Storage Spaces Direct, hybrid (Storage Spaces Direct plus SAN) and disaggregated SAN over Fibre Channel or iSCSI
Create the CI/CD service principal and configure Azure access
Check what updates the cluster has discovered and what Azure shows for it, after the deployment and on a schedule. Read only
Validate the cluster service, the nodes, Storage Spaces Direct, the cluster networks, the quorum and the Arc agent from the cluster, read only
Commit Terraform configuration to Git and trigger pipeline
Configure Azure Backup for Azure Local VM protection
Define customer and CI/CD Infrastructure integration variables
Create and configure the Log Analytics workspace for Azure Local monitoring and observability
Create the landing zone management group under the existing root management group.
Create the full CAF/WAF management group hierarchy under the existing root management group.
Configure OpenGear OM1208-8E-L console server for out-of-band management access
Create the Azure Local deployment service principal for Azure Local automation
Create DHCP reservations for iDRAC out-of-band management interfaces using MAC addresses and planned IPs from infrastructure.yml before hardware arrives on site.
Create a bootable USB drive containing the maintenance environment ISO for simplified machine provisioning
Delete and recreate virtual disks on Dell BOSS cards via iDRAC Storage Management or Redfish API for a clean OS installation target.
Enable Software Defined Networking (SDN) on Azure Local via Arc integration — Network Controller as Failover Cluster service, enabling logical network NSG management
Enable Azure Hybrid Benefit on Azure Local cluster to reduce Windows VM compute costs
Turn on the free level of Microsoft Defender for Cloud that Azure Local needs: Foundational CSPM and the Microsoft cloud security benchmark
Enable Windows Remote Management on all Azure Local nodes via iDRAC Virtual Console. Must run locally on each node — WinRM cannot be enabled remotely before it exists.
Comprehensive infrastructure health validation including Test-Cluster, Health Service, and Arc connectivity
Create Azure Local OU and required AD objects using AsHciADArtifactsPreCreationTool
Configure Privileged Identity Management and Entra ID Conditional Access policies to protect administrative access to Azure Local.
Validate identity, permissions, and connectivity before Arc registration
Register the 13 required Azure resource providers for Azure Local deployment.
Verify network intent compatibility and requirements before enabling SDN on Azure Local
Verify all Azure resources exist and are configured correctly
Create the Azure Virtual Network and subnets for Azure Local management infrastructure.
Physical verification of servers, network equipment, and cabling
Activate Windows Server Subscription for Azure Local to enable automatic VM licensing
Apply Azure Policy initiatives including Azure Local security baseline and compliance policies
Check from every node that the Azure Arc agent is connected, its extensions are healthy and the Arc endpoints are reachable on 443, read only
Assign required RBAC roles to the deployment service principal and deployment user for Azure Local
Configure cluster quorum — validate and provision the cloud witness storage account, then set quorum via Cloud Witness, File Share Witness, or Disk Witness
Deploy Azure Monitor Agent to cluster nodes and configure Data Collection Rules
Configure Dell PowerSwitch TOR switches with QoS/DCB, VLT, and VLANs for Azure Local
Define network configuration for management infrastructure deployment
Configure Azure Site Recovery for Azure Local VM disaster recovery to Azure
Create the deployment source control project
Create a single subscription for the single subscription deployment and associate it with the landing zone management group.
Create dedicated subscriptions for the full CAF/WAF deployment and associate them with management groups.
Verify customer-provided DNS and NTP services are operational
Enable Remote Desktop Protocol on all Azure Local nodes for graphical remote access during configuration and troubleshooting.
Discover all cluster node hardware using Dell iDRAC Redfish API, collecting hardware inventory, BIOS configuration, and iDRAC settings for use in subsequent tasks.
Day 2 management of Network Security Groups — add/remove rules, associate/dissociate, and troubleshoot
Watch validation stage perform syntax and security checks
Mount the Dell Azure Stack HCI OS gold image ISO to all cluster nodes via iDRAC virtual media or USB drive, and verify mount status before BOSS card preparation.
Boot servers from the USB maintenance environment to generate FIDO Device Onboarding ownership vouchers
Arc-enable each Azure Local cluster node using Invoke-AzStackHciArcInitialization
Step 2 - Security Groups (task-02-security-groups.mdx)
Start the Azure Local solution update after the deployment or for the monthly update, with the safety checks of Microsoft Learn, and return without waiting
Test network connectivity including VPN, Bastion, and DNS
Verify all 13 required Azure resource providers are registered before proceeding to RBAC configuration.
Deploy VMFleet for comprehensive storage performance testing and baseline documentation
Deploy the Azure VPN Gateway for site-to-site connectivity between Azure and on-premises infrastructure.
Define cluster-specific resources including VPN connection and node DNS
Configure diagnostic level, streaming data client, and EU location settings for Azure Local telemetry
Configure source control project settings for branch protection, merge approvals, and security
Review and remediate Defender for Cloud security recommendations for Azure Local
Configure static IP addresses on the management network adapter for each Azure Local cluster node using explicit values from infrastructure.yml.
Create DHCP reservations for in-band management network interfaces using MAC addresses from Task 02 hardware discovery and planned IPs from infrastructure.yml.
Create resource groups in each subscription for the full CAF/WAF deployment.
Create the single resource group for the simplified deployment Azure Local cluster.
Step 3 - DNS Node A Records (task-03-dns-node-a-records.mdx)
Enable Azure Local (HCI) Insights for cluster health monitoring and performance analytics
Manually install Azure Stack HCI OS on each cluster node using iDRAC Virtual Console. The ISO was mounted in Task 02 — nodes boot directly into Windows Setup after the BOSS recreation reboot.
Monitor Arc registration bootstrap status and handle OEM image updates
Validate network connectivity, RDMA configuration, and DCB settings for Azure Local cluster
Check the network adapters, virtual switches, Network ATC intents, RDMA, cluster networks, DNS and the endpoints from the nodes, read only
Take one Azure Local node through maintenance: check it is safe, drain it, reboot it, resume it and wait for the storage repair jobs before the next node
Verify OpenGear console server is registered with Lighthouse
Use the Azure portal to create a site, upload ownership vouchers, and provision Azure Local machines remotely
Review Terraform execution plan showing resource changes
Apply Active Directory security groups to the local groups on each cluster node for least-privilege administrative and remote management access
Create the Local Network Gateway and Site-to-Site VPN connection between Azure and on-premises infrastructure.
Validate disaster recovery procedures with test failovers and failback testing
Validate Key Vault access, Log Analytics, and monitoring setup
Verify firewall rules for required Azure and Dell endpoints
Approve the deployment to proceed with infrastructure provisioning
Validate BIOS and iDRAC settings against Azure Local requirements using Task 02 discovery data. Generates a per-node compliance report for use in Task 05 remediation.
Day to day operations on an Azure Local cluster: health check, maintenance mode of a node, live migration, volume ownership, capacity and alerts
Create deployment environments for CI/CD pipelines
Disable DHCP on all network adapters except virtual and management adapters to lock in static IP configuration across all Azure Local cluster nodes.
Configure security event collection via Data Collection Rules for Azure Local
Test cluster high availability, failover scenarios, and live migration capabilities
Track the automated OS installation and configuration progress using the Configurator app
Run comprehensive network validation and Microsoft Environment Checker
Configure Point-to-Site VPN for remote administrative access to the Azure management network.
Step 4 - Service & Admin Accounts (task-04-service-admin-accounts.mdx)
Configure alert rules and action groups for Azure Local monitoring and notifications
Install the WindowsOpenSSH Arc extension on cluster nodes and enable Azure Arc SSH tunneled access via HybridConnectivity
Check the storage pools, virtual disks, physical disks and cluster shared volumes, and optionally measure disk latency, from the cluster
Complete validation sign-off and document readiness
Verify that Azure Arc registration is successful and connectivity is established for all cluster nodes
Verify that Azure Stack HCI OS has been successfully installed on all cluster nodes before proceeding to Phase 03: OS Configuration.
Deploy Azure Bastion for secure browser-based RDP/SSH access to management VMs without public IP exposure.
Remediate non-compliant BIOS and iDRAC settings identified in Task 04 using Dell Redfish API. Handles reboots, re-collects configuration, and re-runs Task 04 validation to confirm 100% compliance.
Configure primary and secondary DNS server addresses on the management NIC of each Azure Local cluster node using explicit values from infrastructure.yml.
Configure CI/CD environment variables for Azure authentication
Deploy Dell OpenManage Integration for Windows Admin Center (OMIMSWAC) for hardware monitoring
Deploy and configure Windows Admin Center (WAC) on a dedicated management server for Azure Local cluster management, monitoring, and Azure integration.
Write the deployment documentation package of an Azure Local instance from infrastructure.yml and from what the cluster reports
Run the standalone Azure Local Environment Checker (connectivity, hardware, software, Active Directory, network and Arc integration validators) before deployment, and uninstall it from the machines before deployment starts.
Step 5 - Group Assignments (task-05-group-assignments.mdx)
Monitor infrastructure deployment during apply stage
Validate security configuration, Defender for Cloud, RBAC, and compliance posture
Create the Storage Spaces Direct volumes and the Azure storage paths of the Azure Local instance from the master infrastructure.yml
Confirm all provisioned machines are connected to Azure Arc and ready for cluster deployment
Validate backup operations, restore procedures, and disaster recovery capabilities
Configure syslog and SNMP forwarding from network devices to the syslog Linux server
Give the customer administrator access to the Azure Local resources in Azure and write the transfer record
Plan and deploy CI/CD runners for Azure Local automation
Create and associate Network Security Groups for the management subnet and AzureBastionSubnet.
After simplified machine provisioning, install the OEM drivers and SBE, set one static management address with one default gateway, DNS and time, and check every machine before cluster Validate.
Verify that DNS servers are correctly configured on the management NIC of each Azure Local node and that critical Azure endpoints resolve successfully.
Verify automated tests confirm successful deployment
Download Azure Marketplace VM images to the Azure Local cluster for Arc VM deployment
Create Azure Local NSGs for logical network micro-segmentation before network provisioning
Configure the NTP time source on each Azure Local node using w32tm — required for Kerberos authentication and AD domain operations.
Deploy a NAT Gateway for outbound internet connectivity from the management subnet.
Deploy an Azure Arc Gateway to enable Arc-enabled server connectivity through a centralized gateway endpoint.
Enable ICMPv4 and ICMPv6 inbound firewall rules on each Azure Local node to allow ping for network diagnostics and connectivity validation.
Create Azure Local logical networks for Arc VM network connectivity
Disable network adapters not used for management to prevent configuration issues during cluster deployment
Create a Log Analytics workspace for centralized monitoring and log collection across management infrastructure.
Verify all Phase 06 post-deployment tasks completed successfully
Set the computer hostname for each node according to naming standards
Attach a Fibre Channel or iSCSI SAN to a deployed hyperconverged Azure Local cluster so SAN volumes run beside Storage Spaces Direct, following Microsoft Learn 2610
Deploy the management Key Vault for storing deployment secrets, certificates, and credentials.
Clear previous Storage Spaces Direct configuration if redeploying on existing hardware
Deploy all management virtual machines — Domain Controllers, Utility Server, NDM Server, and Lighthouse Server.
Import the OEM Solution Builder Extension files into the cluster's update service when an update reports AdditionalContentRequired
Install Fibre Channel HBA drivers (or the dedicated iSCSI adapter drivers) on Azure Local nodes for SAN disaggregated deployments, and get the zoning timing right for disaggregated versus hybrid
Verify Windows Multipath I/O, register the SAN vendor with MSDSM and claim the array's disks, for Fibre Channel and iSCSI SAN disaggregated deployments on Azure Local 2610
Verify SAN LUN presentation (Fibre Channel or iSCSI) and confirm the infrastructure and performance history LUNs are RAW before Azure Local disaggregated deployment
Optional combined script that runs Tasks 02–10 in a single execution for faster deployment
Read-only verification of all Phase 03 OS Configuration tasks (01–15) across all cluster nodes
Known issues found on live runs of the azurelocal-ztp zero-touch automation, with the recovery steps Microsoft Learn documents for simplified machine provisioning.
How variables are managed in the Azure Local toolkit: one registry, one infrastructure file, one template per tool.
A decision flow from the way the OS was installed (azurelocal-ztp simplified provisioning, or a manual ISO install) to OS configuration, method detection, the two paths, the converge check, ARM Validate and ARM Deploy, and how to tell which method you used.
How the azurelocal-ztp scripts take Azure Local machines from bare metal to Provisioned and Arc-connected, ending at the Handoff, with no one in the rack: stages, gates, management address modes, what runs where, parallel nodes, and resume. OS configuration follows.