Skip to main content

Prerequisites and Assumptions

Runbook Azure

DOCUMENT CATEGORY: Runbook
SCOPE: Pre-deployment requirements
PURPOSE: Validate all prerequisites before implementation
MASTER REFERENCE: Microsoft Learn - Prerequisites

Status: Active

This document outlines all requirements that must be met before beginning Azure Local deployment. All prerequisites must be validated before proceeding to implementation stages.

Executive Summary​

Azure Local deployment requires completion of comprehensive planning activities, properly configured hardware and software environments, and appropriate Azure permissions. This document serves as your pre-deployment checklist.

Critical Path: Planning Phase → Prerequisites Validation → Implementation Stages


1. Planning Phase Prerequisites​

All planning documents must be completed and approved before implementation begins.

Required Planning Documents​

DocumentStatusPurposeLink
Discovery Checklist✅ RequiredCustomer environment assessment and requirements gatheringDiscovery Checklist
Site Assessment✅ RequiredPhysical infrastructure and network evaluationSite Assessment
Naming Standards✅ RequiredResource naming conventions and patternsNaming Standards
Landing Zone Strategy✅ RequiredAzure foundation architecture and governanceLanding Zone Strategy

Planning Deliverables​

  • infrastructure.yml populated with environment-specific values
  • Variable schema aligned with customer requirements
  • Network architecture documented and approved
  • Security and compliance requirements identified

2. Hardware Prerequisites​

Critical Assumption

Hardware must be racked, powered, and cabled per vendor guidance before beginning provisioning stages. This includes:

  • All Dell AX servers physically installed in racks
  • Power cables connected to redundant PDUs
  • Network cables installed per cabling design specifications
  • iDRAC/BMC interfaces accessible and configured
  • Console access available for all servers

The provisioning runbook assumes physical infrastructure is complete and validated.

Server Requirements​

Hyperconverged (Storage Spaces Direct) deployments support 1 to 16 machines per instance. Disaggregated deployments (external SAN, no Storage Spaces Direct) support up to 64 machines. A hybrid instance is a hyperconverged instance with an external SAN attached after deployment.

ComponentMinimumRecommendedNotes
CPUIntel Xeon Gold/Platinum or AMD EPYC 7000 seriesLatest generation enterprise CPUsMust support virtualization
RAM256GB per server512GB+ per serverECC memory required
Storage1TB SSD/NVMe (OS boot) + 2TB+ across 2+ data drivesAll-NVMe configurationControllers must be HBA/passthrough mode — RAID not supported
Network2x 10GbE NICs minimum2x 25GbE or higherRDMA-capable adapters for the storage intent (see Section 5)
Design standard versus Microsoft minimum

The Minimum column is this runbook's production design standard. Microsoft's published minimums in System requirements for Azure Local are lower: ECC memory of at least 32 GB, a boot drive of at least 200 GB (400 GB or more for machines with more than 768 GB of memory), at least two data drives of at least 500 GB each, TPM 2.0 and Secure Boot turned on, and Intel VT or AMD-V turned on. Hardware must be in the Azure Local catalog for Microsoft Support. Storage controllers must pass drives through (HBA pass-through mode): RAID controllers and shared SAS enclosures are not supported for Storage Spaces Direct. External Fibre Channel or iSCSI SAN storage is supported only as the SAN configurations described in Storage Planning.

Physical Infrastructure​

  • Rack Mounting: Servers properly racked per vendor specifications
  • Power: Redundant power supplies connected to separate PDUs
  • Cooling: Adequate rack cooling and environmental controls
  • Cable Management: Clean cable routing with proper labeling
  • Access: Physical security controls for server room/rack access

Management Access​

  • iDRAC/BMC: All servers accessible via out-of-band management
  • Console Access: Direct console access available for troubleshooting
  • Network Access: Management interfaces reachable from administration workstations

Hardware Vendor Solution Builder Extension (SBE) Package​

The SBE package is a requirement

Download your hardware vendor's Solution Builder Extension package for your model and the Azure Local version you deploy, before you start. It is a requirement: you need it to update the cluster, and the automation reads it from a share and checks it before the cluster is created. To install it during the build, switch on the side-load in the file; it is off by default.

Put the package on a share or folder that the automation can read. You need it either way. A vendor whose package has no automatic download for your cluster leaves the first update in the AdditionalContentRequired state until you import the files (Dell, for example, without support credentials on the cluster). The later update reuses the same share: Add-SolutionUpdate imports the files, then Start-SolutionUpdate installs them. See Import and rediscover updates on Microsoft Learn and Update management and Solution Builder Extension.

The share holds the three files as the vendor delivers them:

FilePurpose
SBE_Discovery_<Vendor>.xmlThe discovery manifest
SBE_<Vendor>_<Family>_<Version>.xmlThe payload manifest
SBE_<Vendor>_<Family>_<Version>.zipThe payload

What stays optional is only the build-time side-load: hardware.sbe.delivery is off unless you set it, and the toolkit never side-loads a package you did not ask for.

What the automation checks​

The pre-cluster verification gate checks the package on the share with six checks. Each one blocks the cluster creation when it fails.

CheckWhat it verifies
SB-001The package source is configured (or you declared it not applicable, with a reason)
SB-002The share is reachable (read only)
SB-003The three files are present
SB-004The files are unmodified: the hashes match the manifest and, when you set them, package_sha256 and package_size_bytes
SB-005The hardware model of every node is listed in the package's own supported models. A package for the wrong hardware family fails: a 17G Intel package fails on AX-760 nodes, and the right one is 16G-45n0c-Intel 5.0.2609.1611
SB-006The package version is validated for the target solution version (for Dell on 2610, 12.2610.1004.x)

Keys in infrastructure.yml​

KeyMeaning
hardware.sbe.requirementrequired, not_applicable when the hardware has no SBE or the cluster downloads it with the vendor credential, or vendor (the default, also when the key is absent; since schema 5.6.28): the vendor catalog config/oem/<hardware.vendor>.json (sbe.requiredByDefault) decides, required for Dell, HPE and DataON, a Warning that asks you to state it for Lenovo Premier, Skipped for a vendor the catalog does not know
hardware.sbe.not_applicable_reasonRequired with not_applicable: why, in one sentence
hardware.sbe.source_pathThe share or folder that holds the three files
hardware.sbe.source_usernameOptional account that reads the share, if the account running the automation cannot
hardware.sbe.source_passwordA Key Vault reference (keyvault://<vault>/<secret>) for that account. Never the password itself
hardware.sbe.package_sha256, hardware.sbe.package_size_bytesOptional. The payload's SHA-256 and size as the vendor publishes them
hardware.sbe.deliveryThe build-time side-load: winrm_copy, node_pull or skip. Default skip

Vendors differ: check your vendor's page​

The table is a summary from Microsoft Learn (release 2610) and vendor pages. It is not yet verified cell by cell, so check your vendor's own page, and do not assume "download first" applies in the same way to every vendor. See Solution Builder Extension updates on Microsoft Learn.

VendorWhat to expect
Dell (AX, MC)An SBE package. The download is behind a login. You side-load it unless the cluster has Dell support credentials
HPEA Standard SBE from HPE's licence portal on some Gen11 models. Other models use a Minimal SBE plus a Windows Admin Center extension
Lenovo ThinkAgile MX PremierAutomatic download and staging
DataONAn SBE on S2D6, S2D7, AZS6 and AZS7. Otherwise a Windows Admin Center extension
Older hardware, Validated NodesHardware older than 2311.2, and Validated Nodes, may have no SBE

Where your hardware has no SBE, or the cluster downloads it itself, set hardware.sbe.requirement to not_applicable and give the reason.


3. Software Prerequisites​

Operating System​

  • This runbook targets the Azure Local 12.x release train (OS build 26100). The latest release is 12.2610 (solution version 12.2610.1004.50, October 2026). In the 2610 release all new and existing deployments run OS version 26100.33650, so network adapter and other drivers must be compatible with that OS version or with Windows Server 2025. See Releases and Support Lifecycle. Azure Stack HCI 23H2 (OS build 25398) is out of support
  • Core installation (no Desktop Experience available; management via Windows Admin Center or remote tools)
  • Identity: Active Directory (the default; domain recommended for production) or local identity with Azure Key Vault. With Active Directory, the machines can either stay in a workgroup until the deployment joins them to the domain, or be joined to the domain before deployment (optional, supported starting with version 2604; add the deployment user to the local Administrators group). With local identity the machines stay in a workgroup
  • Inbox network drivers are not supported: an adapter whose DriverProvider is Microsoft uses the inbox driver. Install the OEM driver first

Management Tools​

ToolVersionPurposeInstallation
Windows Admin Center2311+Dell hardware health telemetry (optional)Download
Azure CLI2.50+Azure resource managementwinget install Microsoft.AzureCLI
Azure PowerShell10.0+Azure automationInstall-Module -Name Az -Force
Azure Stack HCI PowerShellLatestHCI-specific cmdlets (module names still use the Az.StackHCI and AzStackHci prefixes)Included with Azure Local
Windows Admin Center is Optional

Windows Admin Center is not required for Azure Local deployment or day-to-day cluster management — Microsoft recommends the Azure Portal as the primary management interface.

However, WAC is recommended for Dell environments because it hosts the Dell OpenManage Integration with Microsoft Windows Admin Center (OMIMSWAC) extension. OMIMSWAC collects Dell-specific hardware telemetry (fans, power supplies, temperatures, drive health) via iDRAC and pushes it to Azure Monitor Insights, enabling proactive hardware alerting and centralized visibility in the Azure Portal.

If you are not using Dell hardware, or do not require hardware health telemetry in Azure Monitor, WAC can be skipped entirely.

Development Tools​

  • Git for repository access
  • PowerShell 7+ for advanced scripting
  • VS Code with PowerShell extension (recommended)
  • GitLab access for CI/CD pipelines

4. Azure Prerequisites​

Subscription Requirements​

  • Azure subscription with sufficient quota for Azure Local resources
  • Billing account configured and accessible
  • Support plan (Standard or higher recommended for production)

Required Permissions​

Detailed Role Assignment Procedures

This section summarizes the required permissions. Step-by-step role assignment procedures are covered in Part 2: Azure Foundation — Phase 03: RBAC Permissions.

The deployment user (or the identity a pipeline signs in with) requires the following roles, per Microsoft Learn — Assign required permissions for Azure Local deployment and the deployment checklist:

Subscription-level roles (Learn: the deploying user must be a user access administrator and a contributor on the subscription):

RolePurposeReference
ContributorCreate and manage Azure resources, register resource providersDeployment checklist
User Access AdministratorManage access to Azure resources, specifically to Arc-enable each machineDeployment checklist

Resource group-level roles (the resource group the machines are registered in):

RolePurposeReference
Azure Stack HCI AdministratorAzure Local instance management; assigned to the user who deploysAssign permissions
ReaderView resources in the Azure portal; assigned to the user who deploysAssign permissions
Key Vault Data Access AdministratorManage data plane permissions to deployment Key VaultAssign permissions
Key Vault Secrets OfficerRead and write secrets in deployment Key VaultAssign permissions
Key Vault ContributorCreate and manage Key Vault resources for deploymentAssign permissions
Storage Account ContributorCreate storage accounts for deploymentAssign permissions
Azure Connected Machine OnboardingRegister machines with Azure ArcArc prerequisites
Azure Connected Machine Resource AdministratorManage Arc-enabled machine resourcesArc prerequisites

Required Resource Providers​

Register these 13 resource providers before deployment. Registration requires Owner or Contributor on the subscription and is performed in Part 2: Azure Foundation — Phase 02: Resource Providers.

#Provider NamespacePurpose
1Microsoft.HybridComputeAzure Arc-enabled servers
2Microsoft.GuestConfigurationAzure Policy guest configuration
3Microsoft.HybridConnectivityAzure Arc connectivity
4Microsoft.AzureStackHCIAzure Local cluster management (core)
5Microsoft.KubernetesArc-enabled Kubernetes
6Microsoft.KubernetesConfigurationKubernetes configuration
7Microsoft.ExtendedLocationCustom locations for Arc
8Microsoft.ResourceConnectorAzure Arc Resource Bridge
9Microsoft.HybridContainerServiceHybrid container workloads
10Microsoft.AttestationSecurity attestation
11Microsoft.StorageStorage accounts for deployment
12Microsoft.InsightsMonitoring and logging (required for Key Vault audit logging validation)
13Microsoft.KeyVaultKey Vault for the deployment secrets, local administrator credentials and BitLocker recovery keys

Source: the register-resource-providers step of Assign required permissions for Azure Local deployment. Simplified machine provisioning (preview) registers a different set: the shared providers plus Microsoft.DeviceOnboarding, Microsoft.Edge, Microsoft.ManagedIdentity and Microsoft.PolicyInsights (see Simplified provisioning).

Microsoft.Insights Required

If Microsoft.Insights is not registered, the diagnostic account and Key Vault audit logging fails during deployment validation.

Azure Arc Prerequisites​

  • Azure Stack HCI OS installed on all cluster nodes (see Section 3: Software Prerequisites)
  • Outbound internet connectivity to required Azure Arc endpoints (see Section 5: Network Prerequisites)
  • Arc Gateway configured if deploying through a proxy environment (optional)
  • RBAC roles for Arc registration (Azure Connected Machine Onboarding + Azure Connected Machine Resource Administrator) assigned per the permissions table above
  • Since software version 12.2512 a new deployment no longer creates a Microsoft Entra application or service principal for the instance; the instance uses a system-assigned managed identity. A Key Vault that uses Private Endpoints is not supported as the deployment Key Vault, and the Key Vault must allow public network access

5. Network Prerequisites​

Detailed Network Implementation

This section covers prerequisites only. Full network design and switch configuration procedures are in Part 3: On-Prem Readiness — Phase 03: Network Infrastructure.

IP and Subnet Planning​

The following must be defined before deployment begins (from the Microsoft Learn deployment checklist and Network considerations for cloud deployments):

RequirementDetails
Management network subnetMinimum 6 contiguous IPs for infrastructure services (first IP assigned to failover clustering)
Storage VLAN IDsTwo unique VLAN IDs for storage networks (Network ATC defaults: 711 and 712; a third storage network, when present, uses 713). Custom storage IPs and VLANs are possible only with an ARM template deployment
DNS serverMust resolve the Active Directory domain and public endpoints. Cannot be changed after deployment. The same servers on every node and on the infrastructure IP range; at least one outside the instance; no public resolvers such as 8.8.8.8. See DNS decisions
Reserved Kubernetes rangesNo node IP, cluster IP, infrastructure IP pool, DNS server, proxy, gateway or VM logical network may fall in the Azure Resource Bridge ranges. Plan around 10.96.0.0/12 and 10.244.0.0/16. New deployments created on 2610 or later (Arc resource bridge 1.8.0) use a smaller service range, 10.96.0.0/24, but deployments created before 2610 (including after an update) keep 10.96.0.0/12, and AKS on Azure Local keeps 10.96.0.0/12 and its pod range 10.244.0.0/16. The wider range is the safe planning rule
NTP sourceTime synchronization for all nodes (domain controllers or dedicated NTP appliance). The node must not use the local CMOS clock as its time source; once domain joined, a node synchronizes from the PDC emulator
Node IP assignmentStatic or DHCP (with reservations) is supported for node and cluster IPs, and the management IP pool is needed either way. This runbook's design standard is static management IPs. Local identity deployments require static IPs and do not support DHCP. Use only one default gateway across the node's physical adapters; the portal fails network validation when more than one adapter has a default gateway

Outbound Internet Connectivity​

All cluster nodes require outbound access on ports 80 (HTTP) and 443 (HTTPS) for:

  • Azure Arc registration and ongoing management
  • Windows Update and security patches
  • Azure marketplace and extension downloads
  • Telemetry, monitoring, and diagnostics
HTTPS Inspection Not Supported

Azure Local does not support HTTPS inspection. Ensure HTTPS inspection is disabled along the entire networking path. This includes Entra ID tenant restrictions v1, which are not supported for Azure Local management network communication.

Firewall Requirements​

Microsoft publishes region-specific consolidated endpoint lists that include Azure Local, Arc-enabled servers, Azure Resource Bridge, and AKS endpoints. Do not maintain a manual URL allowlist — use the official lists:

RegionConsolidated Endpoint List
East USeastus-hci-endpoints.md
West Europewesteurope-hci-endpoints.md
Canada Centralcanadacentral-hci-endpoints.md
South Central USsouthcentralus-hci-endpoints.md
Other regionsSee Firewall requirements for Azure Local

OEM-specific endpoints (required in addition to the above):

OEMEndpoint List
DellDell Azure Local endpoints
HPEHPE Azure Local endpoints
LenovoLenovo Azure Local endpoints

Additional service endpoints may be required depending on enabled features (Azure Monitor Agent, Azure Site Recovery, Microsoft Defender, etc.). See Firewall requirements for additional Azure services.

DNS decisions are permanent​

DNS cannot be changed after the deployment completes, so settle these before the OS is configured (from Network considerations for cloud deployments):

  1. The same DNS servers on every node, and the same servers as the infrastructure IP address range (the Azure Resource Bridge and AKS control planes use them).
  2. At least one configured DNS server runs outside the Azure Local instance. Running all of them as VMs on the instance is not supported.
  3. Every configured server resolves the on-premises domains the infrastructure needs; public DNS servers such as 8.8.8.8 are not supported.
  4. DNS server IPs do not overlap the Azure Resource Bridge ranges (see the table above).
  5. When an ARM template lists several servers, each is a quoted string separated by commas.

Network Architecture​

Azure Local uses Network ATC intents to define traffic types. Traffic types are management (to and from outside the system), compute (VM traffic) and storage (SMB, which includes Storage Spaces Direct and SMB-based live migration; layer 2, not routable). The following network segments are required:

NetworkPurposeVLANRDMA
ManagementCluster management, Arc connectivity, DNS, ADCustomer-assignedNo. RDMA is for host storage traffic
Storage 1Storage Spaces Direct replication (East-West)711 (default)Yes (storage intent)
Storage 2Storage Spaces Direct replication (East-West)712 (default)Yes (storage intent)
Compute/VMTenant VM trafficCustomer-assignedNo. Guest RDMA is not supported on Azure Local

RDMA, a jumbo MTU, and DCB priorities belong to the storage intent. Learn lists the following as overridable Network ATC settings: storage VLANs, jumbo packets (portal options 1514, 4088 or 9014), Network Direct (set false to disable RDMA), Network Direct technology (RoCEv2 or iWarp) and DCB traffic priorities, and recommends the defaults. Learn does not publish the management and compute defaults. The toolkit's ARM parameter generation states them explicitly: storage intent RDMA on with jumbo frames, management and compute intents RDMA off with the 1514 default. Treat that as the runbook's policy, and confirm it on a 2610 instance after deployment (Get-NetAdapterRdma, Get-NetAdapterAdvancedProperty -RegistryKeyword *JumboPacket, Get-NetIntent). This is lab-verified only until Learn states it.

Supported intent patterns (hyperconverged) follow the number of network adapter ports per node (2, 4, 6 or 8), using at least two ports per intent for redundancy:

PortsIntentsNotes
2One intent for all trafficNeeds a network switch for storage; 10 Gb minimum, 25 GbE or higher recommended
4Management and compute on Port 1 and Port 2 (SET); storage on Port 3 and Port 4The storage intent is not a SET team; it uses SMB Multichannel. Works switched or switchless
6Management on Port 1 and Port 2 (SET); compute on Port 3 and Port 4 (SET); storage on Port 5 and Port 6Management and compute separated
8As 6 ports, plus a second compute or backup intent on the remaining portsCustom configuration, up to three intents, one of which includes management

"Group compute and storage, separate management" is also available with a switch. Switchless storage needs at least two intents (management and compute, plus storage); the portal removes the all-traffic and compute-plus-storage options for switchless. On hyperconverged clusters the storage intent shares the same ToR switch pair as management and compute; a separate storage-only switch pair is not supported and can cause split-brain.

Hybrid (Storage Spaces Direct plus SAN): the Storage Spaces Direct network stays as above. SAN connectivity uses separate fabrics and adapters (FC HBAs, or dedicated physical NICs for iSCSI) that Network ATC does not manage; plan those ports up front even though the SAN is attached after deployment.

Disaggregated (SAN only, up to 64 machines): no Storage Spaces Direct and no RDMA storage intent. Two ports carry the management and compute intent (SET, Network ATC); a separate pair of standalone ports carries the cluster networks (default VLANs 1711 and 1712) and is not managed by Network ATC. Fibre Channel uses a 4-port layout (or 6 with a guest backup intent); iSCSI uses the 6-port dedicated-path pattern with two more standalone ports for iSCSI paths A and B. PFC, host ETS and lossless Ethernet are not required because all of this traffic runs over TCP. See Storage Planning.

Physical switch requirements (per Microsoft Learn — Physical network requirements and the network considerations article):

  • IEEE 802.1Q (VLANs): required for all traffic types
  • IEEE 802.1Qbb (Priority Flow Control) and 802.1Qaz (Enhanced Transmission Selection): required for the storage traffic of switched hyperconverged deployments (RDMA). Disaggregated deployments do not require them
  • IEEE 802.1AB (LLDP): required, with the Learn custom TLVs
  • Jumbo frames: Learn recommends an MTU of 9216 bytes for RDMA storage traffic, configured the same on the physical switches (host portal options 1514, 4088 or 9014; Learn gives 9000 on the host with 9216 on the switch as a common pairing for disaggregated deployments). The range 1514 to 9174 in the physical network article is the SDN encapsulation requirement, not the storage MTU. For external SAN (iSCSI) networks use the MTU your storage vendor specifies, end to end
  • ECN for RoCEv2 deployments, and MLAG for redundant ToR pairs
  • Switchless (direct connect) storage: 1 to 4 nodes, a hard upper limit, with no scale-out. The portal supports switchless for 1 or 2 nodes; 3 and 4 node switchless clusters deploy only with an ARM template and need Storage Auto IP turned off with every storage IP defined explicitly

Arc Gateway (Optional)​

If cluster nodes cannot reach Azure endpoints directly, deploy an Arc Gateway to proxy Arc traffic. Arc Gateway configuration is defined in infrastructure.yml under deployment.arc_gateway.


6. Security & Identity Prerequisites​

Prerequisites (Required Before Deployment)​

RequirementDetailsVerified By
Microsoft Entra ID tenantActive tenant with the Azure Local subscription associatedPlanning & Discovery
Identity providerActive Directory: functional AD DS domain with DNS resolution, prepared with the Azure Local OU (used for cluster node identity). Or local identity with Azure Key Vault: no AD, a DNS zone, static node IPs and a Key Vault per cluster. Decide which before discovery endsPart 3: On-Prem Readiness — Phase 01: Active Directory
LCM deployment user account (Active Directory only)Dedicated AD account with appropriate permissions; password must be 14+ characters with complexity requirementsPart 3: On-Prem Readiness — Phase 01: Task 04
Local administrator credentialsIdentical username/password across all cluster nodes; 14+ character complexity requirementOS installation (Part 4, Phase 02)

Assumptions (Customer-Managed, Not Deployed by This Runbook)​

The following are customer responsibilities and are assumed to be in place. They are not configured as part of the Azure Local deployment:

  • MFA — Enabled for all administrative accounts accessing the Azure portal (customer tenant policy)
  • Conditional Access — Policies configured per customer security requirements (requires Entra ID P2)
  • HTTPS inspection disabled — Along the entire networking path for Azure Local management traffic (see Section 5)

Configured During Deployment (Not Prerequisites)​

The following security components are created during the implementation, not beforehand:

ComponentDeployed InReference
Azure Key VaultPart 2: Azure Foundation — Phase 04Task 08: Key Vault
PIM & Conditional AccessPart 2: Azure Foundation — Phase 05Task 01: PIM & Conditional Access (optional, requires Entra ID P2)
Defender for Cloud (free level only)Part 5: Operational Foundations — Phase 04Task 01: Enable Defender for Cloud
Azure Policy assignmentsPart 5: Operational Foundations — Phase 02Microsoft cloud security benchmark, required tags
Backup & DRPart 5: Operational Foundations — Phase 03Phase 03: Backup & DR
Security monitoring & alertingPart 5: Operational Foundations — Phase 02Azure Monitor, alert rules, OMIMSWAC

7. Validation Checklist​

Use this checklist to verify all prerequisites before proceeding to implementation.

☐ Planning Phase​

  • Discovery checklist completed and approved
  • Site assessment completed and approved
  • Naming standards documented and approved
  • Landing zone strategy documented and approved
  • infrastructure.yml populated with environment values

☐ Hardware Validation​

  • All servers racked, powered, and cabled
  • iDRAC/BMC accessible for all servers
  • Network connectivity verified (management interfaces)
  • Hardware specifications meet Azure Local system requirements
  • Firmware/BIOS versions current per OEM solution builder extension
  • Hardware vendor Solution Builder Extension (SBE) package for your model and Azure Local version downloaded and available on a share the automation can read, or hardware.sbe.requirement: not_applicable with a reason (see the SBE package)
  • Storage controllers in HBA/passthrough mode (RAID not supported)
  • Minimum 2 data drives per node for Storage Spaces Direct

☐ Software Validation​

  • Azure CLI installed and authenticated
  • Azure PowerShell modules installed
  • GitLab access configured
  • PowerShell execution policy allows scripts
  • Windows Admin Center installed (optional — required only for Dell OMIMSWAC hardware monitoring)

☐ Azure Validation​

  • Subscription active with sufficient quota
  • 10 required RBAC roles assigned to deployment account: 2 on the subscription and 8 on the resource group (see Section 4)
  • All 13 required resource providers registered, including Microsoft.KeyVault (see Section 4)
  • Azure Arc prerequisites met (TLS 1.2, Windows firewall disabled/configured, proxy configured if applicable)

☐ Network Validation​

  • Outbound HTTPS (443) access confirmed from all nodes
  • DNS resolution working for all nodes
  • NTP synchronization configured
  • Firewall/proxy rules allow required Azure endpoints (see Section 5)
  • HTTPS inspection disabled along the entire networking path
  • Static IPs allocated: management, storage VLANs, and 6+ contiguous management IPs for Azure services
  • Physical switches configured (VLANs, jumbo MTU 9216 on the storage ports or the storage vendor's MTU for SAN, IEEE 802.1Q/Qbb/Qaz for RDMA storage)
  • DNS servers final: same on all nodes, at least one outside the instance, none public, none in the Azure Resource Bridge ranges

☐ Security & Identity Validation​

  • Microsoft Entra ID tenant active and associated with the Azure subscription
  • Active Directory domain functional with DNS resolution
  • LCM deployment user account created with required permissions
  • Local administrator credentials set identically across all cluster nodes
  • MFA enabled for administrative accounts (customer responsibility)

Supported Builds​


References​

Microsoft Documentation​

Planning Documents​

Implementation Documents​

Internal Standards​


Next Steps​

Once all prerequisites are validated:

  1. Proceed to Authentication → Configure deployment credentials
  2. Begin Implementation → Start with Part 2: Azure Foundation (Landing Zones, RBAC, Management Infrastructure)
  3. Monitor Progress → Use validation checklists in each stage
  4. Document Issues → Update this document if new prerequisites are discovered

🚨 Do not proceed to implementation until all prerequisites are met and validated.


PreviousUpNext
Key Inputs and VariablesImplementation GuideAuthentication

Version Control

  • Created: 2026-01-15 by Azure Local Cloud
  • Last Updated: 2026-11-08 by Azure Local Cloud
  • Version: 2.1.0
  • Tags: azure-local, prerequisites, requirements
  • Keywords: prerequisites, assumptions, requirements
  • Author: Azure Local Cloud