Tech Community Live: AMA – Windows manageability

Any chance that the 8gb limit on applications in Intune will be universally raised?

When using the Expedite Windows quality updates policy, we have many clients reporting "Expedite client missing". I realize we can install this manually (or with the msi package deployed via Intune as a LOB app), but is there any reason why Intune doesn't just deploy this automatically when an Expedite policy is assigned to devices?

Is there a way to skip the" Skip user Enrollment Status Page" on co-managed devices where the Device Configuration workload has not been moved yet? I understand that we can do this in MEM through a device configuration profile (csp), but what if you have not moved Device Configuration workload yet?

To use the locate function for Windows machines in Intune, it's my understanding that location services need to be enabled on the desktop. To enable location services, it seems like we either have the draconian approach to force location services for all installed apps via the settings catalog or to use a posh script to enable location services while leaving the control in the users' hands. Am I misunderstanding how this is supposed to work and if not, might there be any plans to simply allow Intune to manage this function automatically?

As you suggested, about my question: Hybrid AD joined (Autopilot) Environment: we got two different identities on Endpoint Manager and AAD for the same device: Why is that and who is doing what (i.e to which of the two apps are targeted to, etc..)? In my company, there are some Hybrid AD joined devices. The Domain-join process starts on Autopilot and Domain Join configuration profile side rather than on on-premised AD. Through the Device Setup step, the device is enrolled into Intune, then through Account Setup the user has to insert his/her credential to join/register the device to AAD and that's when two devices are co-existing: inside the Autopilot dynamic group there are two devices with the same name, but they have two Object IDs and one is AAD Registered and the other is Hybrid AD joined. The latter should take priority, but I wonder if they will be merged after some time or if I have to do some manual clean-up. Thanks!

As the number of policies and applications increase in MEM (Intune), what is the best governance methodology for managing deployments and minimizing negative performance impact? The legacy SCCM / AD GPO architecture, as those policies increased you ran into group bloat and endpoint performance issues during user login, we don't want to carry that over into the cloud as we scale up.

For Win32 app deployments, any plans to specify ARM under the architecture? E.g. For the Surface Pro X and providing ARM variants of Win32 apps.

When reviewing devices' configuration profiles, frequently there are conflicts, or just "errors". Why do settings exist in multiple places? When you have settings in multiple places, it makes conflicts inevitable. At the very least, could you add information to identify WHICH policies/settings that a particular setting is conflicting with. Currently it's a really time consuming and cumbersome process to work though conflict issues.

As people return to work, what's the best architecture, capability to minimize network bandwidth for devices that are AAD joined / Intune managed fully?