Event details
The biggest issue that I have with Autopilot Device Preparation is that the hardware isn't tied to our tenant by uploading a hash.
There is nothing to prevent a use setting up a device with a personal account, e.g. they have left the business & not returned the equipment or setting it up with another tenant.
Traditional Autopilot locks the device to our tenant as long as it can access the appropriate Microsoft endpoints.
Device Association sounds like it may resolve that, any vague ideas on timeline?
MicrosoftHi BillGallop​,
A couple of notes here.
- We are working on a method to associate a device with a tenant when using Windows Autopilot device preparation. This is in the later stages of development and will serve a similar purpose as device registration in Windows Autopilot. No commitment on timeline.
- Even with device registration, devices were never truly "locked" to a tenant and users could still set up devices in their possession for personal (or other) use. Locking devices to a tenant (thus barring them from any other use) is not the intent or purpose of registration (or the yet to be released association feature).
We accept the feedback that some organizations would like this type of locking but with a software only solution, this is not truly possible. Many hardware vendors have solutions that may work for you depending on your exact requirements.