Skip to main content

Planning Tools

Runbook Azure

DOCUMENT CATEGORY: Runbook SCOPE: Planning tools for Azure Local PURPOSE: Choose and use the assessment and design tools before deployment MASTER REFERENCE: Microsoft Learn - Azure Local system requirements

Status: Active

Overview​

Use Azure Local Surveyor to assess workload fit, sizing, and storage design. Then use Azure Local Trailwright to record the deployment design and review its findings.

Surveyor accepts RVTools exports or Azure Migrate inventory. Its plan can be exported as JSON using schema 2.8.0. Trailwright can import that plan, with a conflict preview before anything is applied.

The two tools​

ToolQuestion it answersInputOutput
Azure Local SurveyorDoes it fit?RVTools exports or Azure Migrate inventoryWorkload assessment, sizing, and storage design. A plan can be exported as JSON using schema 2.8.0. See the Surveyor documentation.
Azure Local TrailwrightHow is it built?A Surveyor plan or a saved Trailwright projectA recorded design, release-aware validation findings, and data-only handoffs.

Trailwright records nodes and topology; identity route using Active Directory or Local Identity with Key Vault; networking including VLANs, Network ATC intents, switched or switchless storage, and an IP plan; connectivity using a direct, proxy, Arc gateway, or private path; Azure landing zone resources; storage volumes and resiliency; and operations.

Trailwright validation is release-aware, with each finding linked to its Microsoft Learn source. It follows the newest generally available release, currently 2610.

Trailwright exports include:

  • Design handoff in Markdown and PDF
  • infrastructure.yml in schema 5, the master environment file that the Azure Local Toolkit validates and its automation, including zero-touch provisioning, reads
  • ARM parameter files for the Active Directory and Local Identity templates
  • A Bicep parameter file
  • Schedules in CSV and Excel
  • A draw.io topology
  • The project as JSON

Secrets appear only as references.

Workflow​

  1. Collect the workload inventory in RVTools or Azure Migrate.
  2. Assess and size the workloads in Surveyor, including storage design.
  3. Export the Surveyor plan as JSON.
  4. Import the plan into Trailwright. Review the conflict preview before applying anything.
  5. Record the deployment design in Trailwright. You can also start from a saved Trailwright project.
  6. Review the release-aware findings and their linked Microsoft Learn sources.
  7. Export the design handoff and other data-only outputs as needed.
  8. Follow the Implementation section of this site.

What the tools do not do​

Neither tool deploys anything. Trailwright exports are handoffs and starting points, not a complete or executable deployment.