should offlineautopilotprofiles create the autopilot device?

[Jason_B1025]

To wipe and resetup machines we are testing OSDCloud which uses offlineautopilotprofiles

Because it doesn't seem to be registering and tagging the computer in autopilot. it just joins Azure AD. windows hello forces itself to be setup during the OOBE which we don't want.

Should offlineautopilotprofiles, create the autopilot device? 

[#2]

For the Autopilot Deployment Profile, did you enable the option "Convert all targeted devices to Autopilot"? I believe that's a requirement for the devices to show up in Autopilot.

[#3]

Hi Jason,

Offline autopilot doesn’t create the device in the autopilot section in the Intune portal.

If the devices are already in the intune portal you have to create an autopilot profile, assign the profile to all device or scope this with an azure ad device group, turn on the option convert all targeted devices to autopilot. Device will show up in the autopilot device section.

If the devices aren’t in intune portal under devices and only in azure ad. Then you have to enable the mdm enrollment urls.

https://docs.microsoft.com/en-us/mem/intune/enrollment/windows-enroll#enable-windows-10-automatic-en...

You can manage Windows Hello via multiple ways. Under device enrollment can you block windows hello for all users or you can use the identity protection profile under device configuration and assign this to azure ad group but with this profile you also have the option to make exceptions.

Let me know if this helps you.

Kind regards,

Rene

[#4]

Yes, that setting is enabled.

[#5]

If that option is enabled, and the device is still not added to autopilot, I would raise a ticket with Microsoft about this. That should happen under normal circumstances.