Thanks for joining today’s AMA on Windows Autopilot! Below is a recap of the questions panelists answered during the AMA, along with associated timestamps:

Question – 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. -- In other words - What are the main benefits of Autopilot device preparation and who should use it? – answered at 1:57.

Question – Why do we limit the number of apps and scripts with the OOB experience for for autopilot device prep? – answered at 6:02.

Question – [LinkedIn] Who decided that "Windows Autopilot device prep" was a suitable name to distinguish from "Windows Autopilot"? Was it the same person who replaced "Microsoft Teams" with "Microsoft Teams New"? Any chance we could go back to just using version numbers please? – answered at 8:39.

Question – Are there any plans to include application installation ordering for Autopilot?  (like the ConfigMgr task sequences capability) – answered at 12:07.

Question – 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? – answered at 15:45.

Question – With Autopilot Device prep, can my device manufacturer prepare devices off autopilot device prep? – answered at 18:06.

Question – Are major OEMs like Dell and HP able to inject corporate device identifiers in new format to customers tenants? Like they used to do with older hardware hashes? – answered at 19:34.

Question – With Device Prep how can we smoothly transition to a Co-Management scenario with both Intune and Configuration Manager on the device? Config Mgr can interfere with AutoPilot in some scenarios – answered at 20:55.

Question – 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. – answered at 22:42.

Thanks for joining today’s Ask Microsoft Anything on Windows Autopilot. Q&A will remain open through Friday so keep your comments and questions coming! Up next: The AI-powered admin: emerging trends in endpoint management.

I'm still not clear on OEM enrollment.  It sounded like this is not a priority.  If that is the case, it should be.
Having our OEM pre-register our current device hashes saves a ton of time.  

The Device Ownership behavior (should never show the Personal flow on a Corporate hashed device, and we are not seeing support for OEMs of pre-uploading the Corporate Device Identifier) as well as Device Naming (we use asset tags that get physically added and pre-associated with hardware) have been complete showstoppers from going to Autopilot Device Preparation for us.

I have also heard others say the same about no Self-Deploy (kiosk) or White Glove, and the Application selection process is also clunky (should just be a checklist of available apps, not configuring more groups and policies).

There are many reasons to allow us to define the order of app installation. Some apps have dependencies. Some apps might generate a restart, so we want to install them last. Some apps might install in parallel, so long running installers should be started early in the process. If lots of customers keep asking for it, it should be on your roadmap, surely? "The customer is always right"

With Device Prep how can we smoothly transition to a Co-Management scenario with both Intune and Configuration Manager on the device? Config Mgr can interfere with AutoPilot in some scenarios

Would you recommend InTune to deploy printers for clients that don't use a print server ?
Any improvements planned ? Update a driver on a existing printer deployed through InTune for exemple.

We have our OEM provide registration and pre-provisioning services. What role would they play or what service would they provide if we move to Device Prep?

when will AP device prep (APv2) become feature complete? It's got advantages over APv1, but we still have a handful of Hybrid devices, and we make use of pre-provisioning. We were told pre-prov was "coming soon" to device prep, years ago now. Will it ever come? Be honest, no customer wants 2 different Autopilot solutions. We all want one good solution.

Sorry, I might be not up to date with everything that is documented.

Are major OEMs like Dell and HP able to inject corporate device identifiers in new format to customers tenants? Like they used to do with older hardware hashes.