Simplified Machine Provisioning (Preview)
DOCUMENT CATEGORY: Runbook SCOPE: Azure Local OS installation via simplified provisioning PURPOSE: Install OS and register machines from Azure using FIDO Device Onboarding MASTER REFERENCE: Microsoft Learn — Simplified Machine Provisioning
Status: Active
Simplified machine provisioning is currently in preview. Review the Supplemental Terms of Use for Microsoft Azure Previews before using in production.
- Supported region: East US only (preview)
- Arc Gateway: Not supported in this preview release
- Production recommendation: Use ISO-based installation for production deployments until this feature reaches GA
Microsoft introduced simplified machine provisioning in release 2603 and still labels it preview in the 2609 documentation. The region (East US only) and Arc gateway limits above are unchanged. Re-check the Learn article before each pilot.
An ownership voucher (a .pem file named after the machine serial number) is the proof that lets Azure claim a machine. Anyone holding it might try to claim that machine into their own tenant. Store vouchers in a secured, backed-up location until provisioning completes, then delete them. The maintenance environment uses documented default credentials until the target OS is installed, so keep the machines on an isolated network during preparation.
Overview
Simplified machine provisioning offers an alternative to manual ISO installation. Instead of creating boot media, connecting to each server's management interface, and manually running Windows Setup, this workflow:
- Prepares machines with a USB-based maintenance environment that generates FIDO Device Onboarding (FDO) ownership vouchers
- Provisions machines from Azure — the OS is downloaded and installed automatically, with network configuration and Azure Arc registration handled remotely
- Deploys the cluster using the provisioned machines, just as with ISO-based installation
This approach is most valuable when someone other than on-site staff prepares the machines (e.g., a hardware manufacturer or integrator), and on-site staff simply power them on and connect them to the network.
For a fully automated approach that bypasses the manual USB media step entirely, see the azurelocal-ztp project. It uses BMC/Redfish (iDRAC, XCC, iLO) to mount the maintenance-environment ISO as virtual media, set the boot source, and reboot — all without anyone in the rack and without physical USB media.
This is especially useful for remote or lights-out deployments where physical access is limited.
ISO vs Simplified Provisioning Comparison
| Aspect | ISO (Manual) | Simplified Provisioning (Preview) |
|---|---|---|
| Status | GA — production supported | Preview — East US only |
| OS Installation | Manual via iDRAC/BMC virtual console | Automated from Azure |
| Physical Access | Required for initial ISO boot | Required for initial USB boot |
| Network Configuration | Manual (SConfig or PowerShell) | Automated from Azure portal |
| Azure Arc Registration | Separate step (Phase 04) | Included in provisioning flow |
| Arc Gateway Support | ✅ Supported | ❌ Not supported (preview) |
| Supported Hardware | All Azure Local Catalog hardware | Dell AX-650/750, Lenovo MX650 V3/V4, HPE DL360 Gen11 |
| Best For | Production deployments, all hardware | Automated provisioning of supported SKUs |
Supported Hardware SKUs
| Vendor | Model | BMC |
|---|---|---|
| Dell | AX-650, AX-750 | iDRAC |
| Lenovo | ThinkAgile MX650 V3, MX650 V4 | XCC |
| HPE | ProLiant DL360 Gen11 | iLO |
Workflow Overview
graph TD
A[Download Maintenance ISO + USB Tool] --> B[Create USB Installation Media]
B --> C[Boot Each Server from USB]
C --> D[Maintenance Environment Generates Voucher]
D --> E[Collect Ownership Vouchers]
E --> F[Create Site in Azure Portal]
F --> G[Upload Vouchers + Configure Site]
G --> H[Azure Installs OS + Configures Network]
H --> I[Azure Arc Registration Completes]
I --> J[Machines Ready for Cluster Deployment]
Prerequisites
Hardware
| Requirement | Details |
|---|---|
| Validated hardware SKU | Dell AX-650/750, Lenovo MX650 V3/V4, or HPE DL360 Gen11 |
| USB flash drive | At least 8 GB, one per prep session |
| Windows 11 PC | Reliable internet connection and USB port for media creation |
| USB port on servers | Required for booting the maintenance environment |
Azure
| Requirement | Details |
|---|---|
| Feature registration | az feature register --namespace Microsoft.DeviceOnboarding --name AzureLocalZTP |
| Resource providers | Microsoft.HybridCompute, Microsoft.AzureStackHCI, Microsoft.DeviceOnboarding, Microsoft.Edge, Microsoft.GuestConfiguration, Microsoft.HybridConnectivity, Microsoft.KeyVault, Microsoft.ManagedIdentity, Microsoft.PolicyInsights, Microsoft.Storage, Microsoft.Insights |
| Permissions | Resource group Owner, or Contributor + RBAC Administrator |
| Region | East US (preview limitation) |
Steps in This Section
| Task | Description | Duration |
|---|---|---|
| 1 | Create USB Installation Media | 15 min |
| 2 | Prepare Machines | 30 min per machine |
| 3 | Provision Machines from Azure | 15 min + wait |
| 4 | Monitor Machine Setup | 30–60 min |
| 5 | Verify Azure Arc Connectivity | 10 min |
Outcome
Upon completion of this section:
- All Azure Local machines have the Azure Stack HCI OS installed
- Network is configured automatically based on site-level settings
- All machines are registered with Azure Arc
- Machines are ready for Phase 03: OS Configuration or directly for cluster deployment (if the OS configuration was handled during provisioning)
Follow a running provisioning and deployment live with azurelocal-sonar, and check endpoints and network readiness first with azurelocal-beacon.
Navigation
| ← Phase 02: OS Installation | ↑ Cluster Deployment | Phase 03: OS Configuration → |
References
- Microsoft Learn — Simplified Machine Provisioning
- Microsoft Learn — Install OS via ISO
- FIDO Device Onboarding Overview
- azurelocal-ztp — BMC/Redfish Automation
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2026-05-01 | Azure Local Cloud | Initial release — Simplified Provisioning (Preview) |