Forum Discussion
Dynamic groups based on device.enrollmentProfileName for WIndows 10 devices
Didn't really find an answer to this and getting a proper answer from support seemed hard because the functionality spans multiple teams. So here it goes.
As I read in the dynamic group documentation (Docs Page - Device Rules) the "device.enrollmentProfileName" would allow me to create dynamic groups of Win10 devices based on their assigned autopilot profile. I was getting mixed results when I was trying/testing this however.
What I could establish so far is that it seems this value for the device is set as it's getting deployed with the profile or getting enrolled in Intune. And if you later reassign the device to a different Autopilot profile the value is not changed until you restage or re-enroll the device.
I'ld like to have some confirmation that this is actually correct and if it is at Autopilot deployment only or also when re-enrolling the device in intune.
As an extra it would be nice to export this value for all devices, but so far saw no reference to this attribute when polling devices with PowerShell or the MSGraph.
Who could clarify this a little bit for me?
- EnrollmentProfileName is more for Android Dedicated devices.
You could look into devicePhysicalIDs, check out this website: https://docs.microsoft.com/en-us/mem/intune/enrollment/enrollment-autopilot#create-an-autopilot-device-group- I could, and I am for now.
But that doesn't quench my curiosity about this. 🙂
I've also seen scenario's where suddenly the Autopilot related attributes in devicePhysicalIDs seem to have disappeared. But that is a problem for another time. Haven't been able to replicate that one.- Have you looked into GroupTags?
What they might mean for you?
I haven't seen easy issues with them disappearing.
https://techcommunity.microsoft.com/t5/intune-customer-success/support-tip-using-group-tags-to-import-devices-into-intune-with/ba-p/815336
