Skip to main content

11 docs tagged with "zero-touch"

View all tags

Automation Prerequisites

What you need before running the azurelocal-ztp automation: Azure subscription settings and roles, hardware and BMC, network paths, and the Windows management host.

Choose Your Route: ISO or Simplified Provisioning

Two routes lead to the same Azure Local cluster deployment. A flow chart and a decision matrix show which OS installation, OS configuration and Arc registration steps each route needs before Validate.

Monitor the Run with Sonar

Follow a zero-touch provisioning run live and read-only with azurelocal-sonar, from the virtual USB boot to ready for Validate, and on through cluster Validate and Deploy.

Output and Handoff to Cluster Deployment

What the azurelocal-ztp automation produces at the Handoff, and what to give OS configuration and cluster deployment, including each machine's arcMachineResourceId and the management address result.

Phase 02: OS Installation

Install the Azure Stack HCI OS on cluster nodes by one of two paths: manual installation from an ISO or OEM image, or simplified machine provisioning (preview), by hand or automated with azurelocal-ztp.

Run from a Pipeline

Run the azurelocal-ztp zero-touch automation from a pipeline on a self-hosted Windows runner: why self-hosted, identity and roles, Key Vault secrets, a manual approval before the Boot stage, and resume with -From.

Simplified Machine Provisioning (Preview)

Install the OS and register Azure Local machines using simplified machine provisioning — an alternative to manual ISO installation that automates OS deployment from Azure.

Troubleshooting and Known Issues

Known issues found on live runs of the azurelocal-ztp zero-touch automation, with the recovery steps Microsoft Learn documents for simplified machine provisioning.

Zero-Touch Provisioning Automation (Preview)

How the azurelocal-ztp scripts take Azure Local machines from bare metal to Provisioned and Arc-connected, ending at the Handoff, with no one in the rack: stages, gates, management address modes, what runs where, parallel nodes, and resume. OS configuration follows.