Skip to main content

Requirements Workshops

Runbook Azure

DOCUMENT CATEGORY: Runbook SCOPE: Discovery sessions for requirements gathering PURPOSE: Gather technical and business requirements MASTER REFERENCE: Microsoft Learn - Azure Local Planning

Status: Active


Discovery workshops are structured sessions designed to gather all technical and business information required for successful Azure Local implementation.

Workshop Planning and Logistics​

Workshop Structure​

Day 1: Business and Technical Overview (4 hours)​

  • Hour 1: Business requirements and objectives
  • Hour 2: Current state architecture review
  • Hour 3: Application portfolio discussion
  • Hour 4: Compliance and security requirements

Day 2: Technical Deep Dive (6 hours)​

  • Hours 1-2: Infrastructure assessment
  • Hours 3-4: Network architecture workshop
  • Hours 5-6: Migration strategy session

Day 3: Design Validation (2 hours)​

  • Hour 1: Review preliminary design
  • Hour 2: Validate assumptions and next steps

Naming Standards Workshop​

Naming Convention Development​

During discovery, establish naming standards that will be used throughout the implementation.

Workshop Output - Naming Standards Document​

# Azure Local Naming Standards

## Organization: [Organization Name]
## Date Established: [Date]

### 1. On-Premises Infrastructure

#### Azure Local Cluster Nodes
Pattern: {CUSTOMER}AX{NN}
Examples:
- CONAX01 (Customer AX Node 01)
- CONAX02 (Customer AX Node 02)

#### Management Infrastructure
- Domain Controllers: {CUSTOMER}DC{NN}
- Certificate Servers: {CUSTOMER}CA{NN}
- WAC Gateway: {CUSTOMER}WACGW
- Tools Server: {CUSTOMER}TOOLS

### 2. Azure Resources

#### Resource Groups
Pattern: rg-{customer}-{component}-{environment}-{region}
Examples:
- rg-con-azlocal-prod-eus
- rg-con-network-prod-eus
- rg-con-management-prod-eus

#### Virtual Networks and Subnets
VNet Pattern: vnet-{customer}-{environment}-{region}
Subnet Pattern: snet-{purpose}-{environment}
Examples:
- vnet-con-prod-eus
- snet-management-prod
- snet-vms-prod

#### Storage and Key Vault
Storage: st{customer}azl{env}{region}
Key Vault: kv-{customer}-{env}-{region}
Examples:
- stconazlprodeus
- kv-con-prod-eus

### 3. Virtual Machines

Pattern: {customer}-{app}-{role}-{env}-{nn}
Examples:
- CON-SQL-DB-PROD-01
- CON-WEB-APP-PROD-01
- CON-APP-SVC-PROD-01

Network Requirements Discovery​

Network Planning Workshop Output​

VLAN Allocation Table (Site-Specific)​

VLAN IDPurposeIP RangeSubnet MaskGatewayNotes
100Management10.10.100.0/2410.10.100.1iDRAC, cluster management
711Storage 1Non-routed/24N/AStorage Spaces Direct
712Storage 2Non-routed/24N/AStorage Spaces Direct
200Production VMs10.10.200.0/2410.10.200.1Production workloads
201Development VMs10.10.201.0/2410.10.201.1Dev/Test workloads
300Backup10.10.300.0/2410.10.300.1Backup traffic isolation
400DMZ10.10.400.0/2410.10.400.1Internet-facing services

IP Address Planning (Management Network)​

Device/ServiceHostnameIP AddressPurpose
Cluster IPCONCLUS0110.10.100.10Cluster management
Node 1CONAX0110.10.100.11AX Node 1 management
Node 2CONAX0210.10.100.12AX Node 2 management
Node 3CONAX0310.10.100.13AX Node 3 management
Node 4CONAX0410.10.100.14AX Node 4 management
Reserved-10.10.100.15-20Future expansion
iDRAC Node 1CONAX01-iDRAC10.10.100.21Out-of-band management
iDRAC Node 2CONAX02-iDRAC10.10.100.22Out-of-band management
iDRAC Node 3CONAX03-iDRAC10.10.100.23Out-of-band management
iDRAC Node 4CONAX04-iDRAC10.10.100.24Out-of-band management

DNS and Active Directory Planning​

DNS Namespace Design​

External DNS Domain: customer.com
Internal AD Domain: azurelocal.mgmt
Azure Local Cluster: cluster.azurelocal.mgmt

DNS Zones:
├── azurelocal.mgmt (AD-integrated)
├── cluster.azurelocal.mgmt (for cluster resources)
├── vms.azurelocal.mgmt (for guest VMs)
└── _msdcs.azurelocal.mgmt (AD service records)

Active Directory OU Structure​

azurelocal.mgmt
└── MGMT
├── Admins
│ ├── Azure Local Cloud (Domain Admin)
│ └── Azure Local Cloud2 (Domain Admin)
├── Operations
│ ├── tpoperator
│ ├── Azure Local Cloud-backup
│ └── Azure Local Cloud-mos
├── Security Groups
│ ├── Azure Local Admins
│ ├── Network Controller Admins
│ └── Azure Local Cloud Admins
├── Servers
│ └── Clusters
│ └── AzureLocal
│ └── CONCLUS01 (OU for cluster)
└── Services
├── svc.ncadmin
├── tpdomainjoin
└── svc.migration

Storage Architecture Workshop​

Duration: 1 hour
Participants: Infrastructure architect, storage administrator, Azure Local deployment engineer
Output: Documented storage topology decision and SAN configuration requirements (if applicable)

Workshop Objectives​

  • Determine storage topology (S2D, hybrid S2D plus SAN, or disaggregated SAN)
  • Choose the SAN protocol (Fibre Channel or iSCSI) and document array and fabric details if SAN is selected
  • Define LUN layout and capacity requirements
  • Establish FC zoning policy and timing (it differs for hybrid and disaggregated)
  • Confirm the billing effect of a SAN (Azure Local L2, no Azure Hybrid Benefit)

Discussion Guide​

Topic 1: Storage Topology Decision (15 min)​

QuestionS2DSAN (hybrid or disaggregated)
Existing SAN investment?Not required✅ Leverages existing
Team has FC or iSCSI SAN expertise?Not required✅ Required
Workloads require specific IOPS/latency?Software-defined, NVMe-backedHardware-specific guarantees
Shared storage between workloads?Azure Local onlyMulti-platform possible

Key questions to ask:

  • Does the customer have an existing SAN that they want to use for Azure Local storage?
  • Is there an FC fabric already in place, or is the SAN iSCSI (dedicated physical ports, no vNICs)?
  • Should the SAN carry all storage (disaggregated, up to 64 machines) or sit beside S2D (hybrid, attached after the cluster is deployed)?
  • Is there an in-house storage admin who manages the SAN?
  • What are the workload IOPS and latency requirements?

Topic 2: SAN Array Details (if SAN selected — 20 min)​

  • Array vendor and model
  • Available capacity and number of available LUNs
  • FC port count per controller (or iSCSI target portal count)
  • Supported host operating systems (confirm the array model is on Microsoft's supported-SAN list for Azure Local)
  • MSDSM vendor and product IDs for the array (Azure Local uses the inbox Microsoft DSM, there is no vendor DSM package to install)

Topic 3: LUN Layout Planning (15 min)​

If SAN is selected, document the following LUN requirements:

LUNPurposeMin SizeNotes
Infrastructure VolumeAzure Local system250 GBMust remain RAW before deployment
Performance HistoryCluster metrics20 GBMust remain RAW before deployment
Workload LUNsVM storagePer capacity planSized based on workload assessment
Infra LUN state

Emphasize to the SAN admin: the infrastructure and performance history LUNs must NOT be initialized before the Azure Local deployment wizard runs. The wizard claims them during cluster creation.

Topic 4: FC Zoning Policy (10 min)​

  • Confirm zoning policy: Microsoft's wording is redundant single-initiator zoning per the fabric and array vendor design; single-initiator/single-target is the Azure Local Cloud standard
  • Agree on naming convention for WWPN aliases and zone names
  • Identify who will configure zoning: SAN admin, FC switch admin, or deployment team
  • Confirm timing. Disaggregated: zoning is configured after HBA WWPNs are collected (Phase 03 Task 12) and before Arc registration, because the LUNs must be visible and RAW before registration. Hybrid: do not zone FC HBAs until after the Azure Local deployment; the SAN is attached afterwards

Workshop Output​

Document the following decisions:

  • Storage topology selected: ☐ S2D ☐ Hybrid ☐ Disaggregated SAN; protocol: ☐ FC ☐ iSCSI
  • If SAN: SAN array model and firmware confirmed
  • If SAN: LUN layout approved and documented in infrastructure.yml
  • If SAN: FC zoning policy agreed
  • If SAN: Responsible party for zoning configuration confirmed
  • If SAN: SAN admin contact documented

Reference: Storage Architecture Planning