Skip to main content

Pre-Discovery Planning

Runbook Azure

DOCUMENT CATEGORY: Runbook SCOPE: Pre-discovery alignment and preparation PURPOSE: Prepare deployment teams for discovery sessions MASTER REFERENCE: Microsoft Learn - Azure Local Planning

Status: Active


Before beginning discovery workshops, deployment teams must align internally on standards, requirements, and technical approach to ensure consistent and successful Azure Local deployments.

Internal Alignment Meeting​

Before beginning workshops, deployment teams must align on standards, requirements, and approach.

Meeting Participants​

  • Sales Engineer (Lead): Technical requirements and sizing
  • Solution Architect: Design standards and architecture patterns
  • Implementation Engineer: Deployment considerations
  • Network Engineer: Network design and VLAN allocation
  • deployment team Representative: Azure resource planning
  • Project Manager: Timeline and resource coordination

Meeting Agenda Items​

1. Review Deployment Scope and Constraints​

  • Deployment specifications and requirements
  • SLA requirements and service levels
  • Budget constraints and optimization opportunities
  • Timeline expectations and milestones

2. Establish Naming Standards​

Standard Naming Convention Planning:
├── Organization Short Name: [lowercase, hyphens]
├── Environment Tags: prod, dev, test, dr
├── Region Codes: eus (East US), scus (South Central US)
├── Resource Type Identifiers:
│ ├── Cluster Nodes: {customer}AX01, {customer}AX02
│ ├── Resource Groups: rg-{customer}-azlocal-{env}-{region}
│ ├── Virtual Networks: vnet-{customer}-{env}-{region}
│ ├── Storage Accounts: st{customer}azlocal{env}
│ └── Key Vaults: kv-{customer}-{env}-{region}

3. Network Architecture Planning​

Network ComponentStandard AllocationSite SpecificNotes
Management VLAN100-199 rangeTBDSite preference
Storage VLAN 1711 (default)TBDCan be customized
Storage VLAN 2712 (default)TBDCan be customized
VM Network VLANs200-299 rangeTBDApplication specific
Backup VLAN300-399 rangeTBDIf segregated
Management IP Range/24 minimumTBD6+ IPs required
VM Network IP RangesBased on sizingTBDGrowth considered

4. Azure Resource Planning​

  • Subscription model (single vs. multi-subscription)
  • Resource group structure and governance
  • Azure region selection and compliance
  • Cost estimation and optimization strategies

Technical Standards Review​

Infrastructure Standards Documentation​

Dell Hardware Configuration Standards​

  • AX node model selection criteria
  • Memory and storage configuration patterns
  • Network adapter assignments
  • BIOS/firmware baseline versions

Azure Local Build Standards​

  • Current release: 12.2610 (solution version 12.2610.1004.50, October 2026), OS build 26100.33650 for new and existing deployments (Windows Server 2025 foundation). See Releases and Support Lifecycle
  • Drivers and firmware must be compatible with OS build 26100.33650; confirm the Dell gold image, Dell solution version and driver set for the 2610 media with Dell (the values recorded for the 2510/2601 media in earlier engagements are out of date)
  • Solution Builder Extension: opt-in only, used only when the hardware partner provides one (copied to C:SBE). Record the version only if one is chosen
  • Update path planning for existing deployments: each release is supported for six months, install the last cumulative update before a feature update
  • Feature enablement decisions including preview features (for example rack aware clusters with SAN, update proxy settings, Arc gateway after deployment)
  • Security baseline configuration (429 evaluated settings in 2610, up from 408; customizable while drift control keeps enforcing it)

Operational Standards​

  • Monitoring and alerting thresholds
  • Backup schedules and retention
  • Patching windows and maintenance schedules
  • Change management procedures

Pre-Discovery Checklist​

Information to Gather Before Discovery Meeting​

  • Environment Background Research:

  • Industry vertical and compliance requirements

  • Current infrastructure platform (VMware, Hyper-V, etc.)

  • Known pain points and drivers for Azure Local

  • Previous deployments and infrastructure relationships

  • Technical Preparation:

  • Discovery workbook templates prepared

  • Network design templates ready

  • Sizing calculators updated

  • Migration tool licenses available

  • Documentation Preparation:

  • Deployment-specific document templates

  • Naming convention proposals

  • Network allocation proposals

  • Sample architecture diagrams