The vast majority of our policies and applications are deployed to devices, rather than users, due to us being an academic environment, and us pushing policies and apps to things such as computer labs. However, our devices are hybrid rather than Entra Joined. Is there a way to have AutoPilot hold on the ESP for only the device flow, and then go to the desktop on the User flow?

Are there any plans to include application installation ordering for Autopilot?  (like the ConfigMgr task sequences capability)

I keep getting "Something went wrong." in Hybrid environment trying to enroll a device, is this still an issue? Does Microsoft still not recommended Hybrid?

If I have a dynamic group that targets all autopilot enrolled devices and I assigned apps to that group, why is it that the total number of apps vary when performing Pre-provisioning? I.G. I have 15 apps assigned, but the pre-provisioning process shows the progress of either 2 or 8 apps being installed. 

Factory Resetting usually fixes this and shows the correct number of 15. 

Welcome to the Windows Autopilot AMA at Microsoft Technical Takeoff! Let's get started. Please post your questions here in the Comments. We will be answering questions in the live stream—and others will be answering here in the Comments. [Note: If your organization’s policies prevent you from seeing the video on this page, you can also tune in on LinkedIn.]

Intune Pre-Provisioning -

Seeking clarification regarding the expected login behavior, Intune Pre-Provisioning once reseal is done.

In Cx environment, User flow administrators typically verify functionality by logging in with an administrative account (XYZ0 or XYZ1), not directing user's to logged-in with their primary email address in user flow, Immediately after resealing, which works as expected.

However, if the device remains connected to the network overnight after resealing, administrative accounts (XYZ0 or XYZ1) are blocked from logging in, resulting in a login loop. This appears to align with Microsoft’s intended process, but we have not found documentation confirming this behavior.

Could you please provide official guidance or documentation that explains whether this login restriction is expected and part of the standard Intune Pre-Provisioning process.

Currently, in 70 % we are using windows autopilot for self deploying mode. Is new process also going to cover device preparation for front line workers where it requires more than 40 apps to be installed and also convert machine into shared mode?

When a user reaches desktop after going through Autopilot/ESP, there is a fixed timer for 1 hour before required apps begins to install. If you restart the pc they will begin after 5 min. Why does this 1 hour timer exist? It's really inconvenient.

I have yet to see a single Autopilot v2 feature that will make me suggest to anyone to migrate away from v1. It introduces more room for error, a less streamlined experience and reduced functionality.