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

---

Overview

This runbook deploys a disaggregated Azure Local cluster using ARM templates with:

• Storage: External SAN (Fiber Channel)
• Identity: Active Directory

ARM template deployment provides repeatability, version control, and CI/CD integration. The disaggregated ARM template includes SAN-specific parameters not present in the S2D template.

---

Prerequisites

Complete all items from the SAN Prerequisites and the AD Prerequisites sections.

---

Key Parameter Differences (SAN vs S2D)

The disaggregated ARM template includes parameters specific to SAN deployments:

Parameter	Description
intentList	List of deployment intents — no storage intent (only management + compute)
sanNetworkList	List of SAN networks for the FC fabric
storageConnectivitySwitchless	Set to false — SAN always uses switched connectivity
sbeVersion	Solution Builder Extension version for your hardware
sbeFamily	SBE package family
sbePublisher	SBE publisher/vendor

---

Step-by-Step

Step 1: Obtain the ARM Template

Download the disaggregated ARM template from:

• Microsoft Learn — ARM Template (Disaggregated)
• Or use the Azure Quickstart Templates

Step 2: Create the Parameters File

Create a parameters file with SAN-specific values:

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "clusterName": { "value": "<cluster-name>" },
    "location": { "value": "<azure-region>" },
    "domainFqdn": { "value": "<domain.fqdn>" },
    "adouPath": { "value": "OU=<ou>,DC=<domain>,DC=<tld>" },
    "storageConfiguration": { "value": "SAN" },
    "networkingPattern": { "value": "managementAndCompute" }
  }
}

Storage Configuration

Set storageConfiguration to "SAN" to deploy with external SAN storage. This is the key differentiator from S2D deployments.

Step 3: Deploy via Azure CLI

az deployment group create \
  --resource-group <resource-group> \
  --template-file azuredeploy.json \
  --parameters @azuredeploy.parameters.san.ad.json

Step 4: Monitor Deployment

az deployment group show \
  --resource-group <resource-group> \
  --name <deployment-name> \
  --query "properties.provisioningState" -o tsv

---

Post-Deployment

After cluster deployment completes:

1. Connect workload LUNs — see Connect External Storage
2. Proceed to Phase 06: Post-Deployment

---

Troubleshooting

Issue	Resolution
Template validation fails	Verify all SAN-specific parameters are included. Check storageConfiguration is set to "SAN".
Deployment fails on storage	Ensure LUNs are visible and in RAW state on all nodes. Verify MPIO is enabled.
SBE parameters invalid	Contact your hardware vendor for correct SBE version, family, and publisher values.

---

Navigation

← AD — Portal (SAN)	↑ SAN Deployment	Local Identity — Portal (SAN) →

---

Version	Date	Author	Changes
1.0	2026-05-01	Azure Local Cloud	Initial release