Active Directory — ARM Template Deployment (SAN)
DOCUMENT CATEGORY: Runbook SCOPE: ARM template SAN cluster deployment with Active Directory PURPOSE: Deploy Azure Local with external SAN storage and AD authentication via ARM MASTER REFERENCE: Microsoft Learn — Deploy via ARM (Disaggregated)
Status: Active
Verified against: Microsoft Learn view=azloc-2610
Overview
This runbook deploys a disaggregated Azure Local cluster using ARM templates with:
- Storage: External SAN (Fibre Channel or iSCSI)
- Identity: Active Directory
ARM template deployment provides repeatability, version control, and CI/CD integration. Microsoft states that ARM template deployment is targeted at deployments at scale and recommends deploying once through the Azure portal first. The disaggregated templates include SAN-specific parameters that are not in the S2D create-cluster template.
Prerequisites
Complete all items from the SAN Prerequisites and the AD Prerequisites sections. Also confirm, per Learn, that all machines run the same OS version and have the same network adapter configuration.
Get the object ID of the Azure Local Resource Provider service principal (unique per tenant) by looking it up by application ID:
(Get-AzADServicePrincipal -ApplicationId "1412d89f-b8a8-4111-b4fd-e82905cbd85d").Id
az ad sp list --filter "appId eq '1412d89f-b8a8-4111-b4fd-e82905cbd85d'" --query "[0].id" -o tsv
Use the result for the hciResourceProviderObjectID parameter.
Choose the Template
There is no storageConfiguration parameter and no generic azuredeploy.json for SAN. Choose the quickstart template by storage protocol:
| Protocol | Quickstart template | Parameter file example |
|---|---|---|
| Fibre Channel | azurestackhci/create-cluster-san | azuredeploy.parameters.json |
| iSCSI | azurestackhci/create-cluster-san-iscsi | azuredeploy.parameters.json |
"Ensure that all parameters in the JSON file are filled out, including placeholders that appear as [""], which indicate that the parameter expects an array structure. Replace these with actual values based on your deployment environment, or validation will fail." Copy parameter names exactly from the sample file for your template version (the Learn parameter table spells the LCM password parameter AzureStackLCMAdminPasssword).
Key Parameter Differences (SAN vs S2D)
| Parameter | Description (Learn 2610) |
|---|---|
infraVolLunId | LUN serial number or unique ID for the infrastructure volume. Minimum size 250 GB. |
infraPerfLunId | LUN serial number or unique ID for the performance history volume. Minimum size 20 GB. |
sanNetworkList | List of SAN networks. |
intentList | List of deployment intents. For a disaggregated cluster the portal offers only management and compute traffic (no storage intent). |
nodes | iSCSI template only. Array of nodes for per-node configuration (additional to the FC parameters). |
storageConnectivitySwitchless, enableStorageAutoIp | Take the values from Microsoft's sample parameter file for your template. |
networkingType, networkingPattern | Learn shows switchedMultiServerDeployment and hyperConverged only as examples. Take the values from the sample parameter file; Learn doesn't document a separate disaggregated value list. |
configurationMode | "The storage volume configuration mode." Take the value from the sample parameter file (Learn lists Express, InfraOnly and KeepStorage for the local identity template only). |
domainFqdn, adouPath, AzureStackLCMAdminUsername, AzureStackLCMAdminPasssword | Active Directory inputs. The OU can't be at the top level of the domain. |
deploymentMode | Validate first, then Deploy. |
The sbeVersion, sbeFamily, sbePublisher, sbeManifestSource and sbeManifestCreationDate parameters exist in the template. Per Learn, an SBE is used "only if your hardware partner provides" one. Leave the SBE parameters empty or omitted by default. Fill them in only when a hardware partner's SBE is explicitly in scope (Azure Local Cloud decision D46).
Step-by-Step
Step 1: Obtain the Template and Parameter File
Download the sample parameter file for your protocol from the links above and fill in every value.
Step 2: Sketch of the Parameters File
The skeleton below shows the shape only. It is not a complete parameter file; start from Microsoft's sample.
{
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"deploymentMode": { "value": "Validate" },
"clusterName": { "value": "<cluster-name>" },
"location": { "value": "<azure-region>" },
"arcNodeResourceIds": { "value": ["<arc-machine-resource-id-1>", "<arc-machine-resource-id-2>"] },
"hciResourceProviderObjectID": { "value": "<rp-object-id>" },
"domainFqdn": { "value": "<domain.fqdn>" },
"adouPath": { "value": "OU=<ou>,DC=<domain>,DC=<tld>" },
"infraVolLunId": { "value": "<infrastructure-lun-id>" },
"infraPerfLunId": { "value": "<performance-history-lun-id>" },
"sanNetworkList": { "value": [] },
"intentList": { "value": [] }
}
}
Step 3: Deploy in the Azure Portal (Validate, then Deploy)
This is the flow Learn documents.
- In the Azure portal select + Create a resource, then Create under Template deployment (deploy using custom templates)
- Under Start with a quickstart template or template spec choose Quickstart template and filter for
azurestackhci/create-cluster-san(orcreate-cluster-san-iscsi). Select the template - On Basics, select Edit parameters and load your parameters file, or enter the values. Save
- Choose the resource group and confirm Deployment Mode = Validate, then Review + create and Create. Validation takes about 10 minutes
- When validation completes, select Redeploy, reload your saved parameters, change the mode from Validate to Deploy, then Review + create and Create
You can run the same template with Azure CLI after downloading it:
az deployment group create \
--resource-group <resource-group> \
--template-file <downloaded-create-cluster-san-azuredeploy.json> \
--parameters @<your-parameters-file>.json
Step 4: Monitor Deployment
In a new browser window open the resource group, select the cluster resource, then Deployments, and watch the progress from the seed machine. Deployment takes between 2.5 and 3 hours; Deploy Moc and ARB Stack takes 40 to 45 minutes.
az deployment group show \
--resource-group <resource-group> \
--name <deployment-name> \
--query "properties.provisioningState" -o tsv
Post-Deployment
After cluster deployment completes:
- Connect workload LUNs — see Post-Deployment: Connect External Storage and Connect External Storage
- Proceed to Phase 06: Post-Deployment
Troubleshooting
| Issue | Resolution |
|---|---|
| Template validation fails | Confirm every parameter is filled, including array placeholders. Confirm you used create-cluster-san (FC) or create-cluster-san-iscsi (iSCSI), and infraVolLunId and infraPerfLunId are set. |
| Deployment fails on storage | Ensure the two system LUNs are visible and RAW on all nodes. Verify MPIO is enabled, the array is registered with MSDSM and claimed. |
| SBE parameters invalid | SBE is opt-in. Remove the SBE values unless your hardware partner supplied an SBE, and place its content at C:\SBE on each machine. |
| "Role assignment already exists" | Occurs when a portal deployment was tried first in the same resource group. Delete the equivalent role assignment named on the failed resource (Resource Group > Access Control (IAM) > Role Assignments) and redeploy. |
| "Tenant ID, application ID, principal ID, and scope aren't allowed to be updated" | Zombie role assignments from an earlier deployment. Delete assignments of type Unknown ("Identity not found") in the resource group and retry. |
| License sync issue | Don't start another Validate deployment while the system is in the Deployment failed state; this resets system properties. |
Navigation
| ← AD — Portal (SAN) | ↑ SAN Deployment | Local Identity — Portal (SAN) → |
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.1 | 2026-11-08 | Azure Local Cloud | Updated to Azure Local 2610: real templates (create-cluster-san, create-cluster-san-iscsi), removed non-existent storageConfiguration, added infraVolLunId, infraPerfLunId, iSCSI nodes, SBE opt-in only, Learn troubleshooting items |
| 1.0 | 2026-05-01 | Azure Local Cloud | Initial release |