Autopilot registration

What it does

Captures the device's hardware hash and registers it into the client's Windows Autopilot through Microsoft Graph. Once registered, the device is known to the client's tenant and follows their Autopilot deployment profile on first boot, the modern cloud-joined path. No exporting CSVs and importing them by hand.

Capture

The device reads its own hardware hash during the build.

Resolve credentials

StageReady fetches the client's Graph credentials from the vault, just in time.

Register via Graph

The hash is posted to the client's tenant. No CSV, no manual import.

First boot

Autopilot recognises the device and applies the client's deployment profile.

The Graph credentials for the client tenant are resolved by StageReady at the moment the job starts and handed to the device. They're never stored on the USB. See Microsoft ecosystem and CIPP & delegated access for how that access works.

Options

This step has no settings to configure. The target tenant comes from the client you picked when generating the code.

Good to know

• Needs a network. It talks to Microsoft Graph, so it runs after Windows is installed and a network is available.
• If registration fails, the setup stops by default, since enrollment is usually the point of the build.

Part of the step catalogue.