On the CM side you might have one set of apps delivered via OSD task sequence, then other apps deployed to collections of existing devices, whereas on the Intune side the apps like win32 and store apps would be assigned to an assignment group that the autopilot profile is assigned to, so assigning a new app would not only impact newly provisioned devices but also existing devices. I can see that the documentation mentions that Intune automated policy and app deployment by doing this, but it seems to require either more complexity in the installer package to handle either scenario or a requirements script (at least for win32 apps) to make sure that those only apply during autopilot provisioning. What is Microsoft's recommendation for handling this extra complexity vs being able to have one set of apps for devices being provisioned, and another set for existing devices (like can an Intune filter be created for check if a device is being provisioned by autopilot at the moment)? and if it was an Intune filter, what about the 200 filter limit and one filter per assignment group limit?

Can we get to the point where Intune facilitates delivery of Windows [base/vanilla OS] images via the public Internet [in support of Autopilot] that can be taken advantage of like the service that Apple provides to Macs and is pretty much there in HP's Sure Recover? Starting with HP, it seems like something that should be possible. That device firmware can be updated to retrieve the image from a provided URL. The provision of an optionally fully automated/unattended WinPE that deposits a vanilla copy of Windows, ready for the Autopilot stage would also tie this together. It would either be open or the URL would need to include an authentication key identifying the unique tenancy. The advantage of this would be that Microsoft maintains it, replacing the image monthly the same way there are slipped streamed ISO releases on Visual Studio downloads.

The ability to making custom reports based on graph data to use alongside the built-in reports, similar to how SCCM came with some reports, but you could also use SSRS to make reports would be very useful and close a lot of gaps to help adoption rates with companies.

Many organizations traditionally have separate teams for managing Windows devices vs Apple/Android devices. While Intune Roles are great for defining such RBAC for Intune administrators, those Roles and ACLs are not available to coding with Registered Applications (serviceprelinciplenames). Are they any plans to help keep coding access permissions inline with user level permissions? Similar to MECM.

It would be really helpful to add capability to get mobile device SIM Number in Intune report for overall asset manageability and consider it also as an IT Asset management tool

Timestamps on the records in the devices of the configs/policies that it received. Better ways to identify conflicts.

Is there a key in intune warehouse report which can help us identify whether the machine is Autopilot or a SCCM machine? This is specially helpful to make a power BI report to analyze the migration to Autopilot