The physical asset has been received.
Its ownership and purpose have been recorded.
Now the technical lifecycle begins.
From Asset to Provisioning Record
The journey becomes:
Asset Recorded
↓
Windows Autopilot Registration
↓
Classification Applied
↓
Provisioning Population Identified
Registration tells the provisioning service:
this hardware belongs to an organisational deployment process.
It still does not mean:
Microsoft Entra Joined
Intune Managed
Compliant
Ready for Use
Those states come later.
Autopilot Registration
For supported corporate Windows devices, the hardware identity is registered with Windows Autopilot.
That creates a provisioning relationship between the device and Wire Finance.
Conceptually:
Physical Device
↓
Hardware Identity
↓
Windows Autopilot
↓
Wire Finance Provisioning Relationship
Registration therefore answers a different question from Microsoft Entra Join.
Autopilot Registration
↓
How should this hardware be provisioned?
while:
Microsoft Entra Join
↓
What organisational device identity does it have?
Classification Comes Next
The registered device can then receive the appropriate Autopilot classification.
For a standard endpoint:
Group Tag:
CORPORATE
For a Privileged Access Workstation:
Group Tag:
PAW
That classification drives the device toward the correct provisioning population.
For example:
CORPORATE
↓
SG-DEVICES-AUTOPILOT-CORPORATE
or:
PAW
↓
SG-DEVICES-PRIVILEGED
The device is now recognised not only as registered hardware, but as hardware with an intended provisioning purpose.
Lifecycle Status
During registration and preparation:
Lifecycle Status:
Provisioning
becomes appropriate.
The device has moved from simply being received to actively being onboarded.
Multiple Records Begin to Appear
At this stage the endpoint may already exist in more than one system.
WF-LT-001
│
├── Asset Register
└── Windows Autopilot
Soon it will also appear in:
Microsoft Entra ID
Microsoft Intune
Microsoft Defender for Endpoint
Each new record should remain traceable back to the same physical asset.
Registration Decision
The lifecycle now looks like:
Corporate Asset
↓
Autopilot Registered
↓
Correct Classification
↓
Correct Provisioning Population
The governing principle is:
registration introduces the device to the provisioning system; it does not establish the final managed or trusted state.
The device is recognised.
Now it needs to be built.
What happens when Wire Finance turns registered hardware into a Microsoft Entra joined and Intune-managed endpoint?