Apologies for a late response, I only just saw it.
Happy to provide more detail...
Today, my company has a global footprint of 60K Windows devices across 700 locations. These locations span 8 business groups into ~100 divisions. In legacy AD, we leveraged OU structure to organize things down into admin scopes, and in moving to Entra+Intune, we flatted to using Group Tags and Dynamic Groups based on those Group Tag assignments, so yes-- that's definitely a blocker for my org to adopt the new implementation. It also negatively impacts inventory and asset management. In the current implementation, it's good to go into the Devices list that is fed to us by Dell partner integration that includes PO numbers, etc. Also, Group Tags, in my scenario, directly impact the device naming conventions as our devices are effectively %GROUPTAG%%SERIAL%. So bare minimum, I would expect you to give us 1:1 between Autopilot v1 and v2. Understand that right now APv2 feels too much like it's focused on BYOD than an enterprise focus of tight controls.
The rest of my comment is pretty straight-forward, what customers are consistently asking for (at least here in the comments) is that we want better order of operation control when we need more control over how things run. Personally, I can use Dependencies easily enough, but that doesn't always achieve what I want of ensuring security stack items get installed ASAP and other things like Office and non-security apps get installed later.
Also, when I say it would be helpful for the Windows Autopilot ESP screens being more informative, simple things like showing the name of the app being installed instead of "X of Y installed" counters and logging that only shows AppID. For example:
Installing Apps (X of Y):
Microsoft 365 Apps (64-bit)