Ability to trigger a dynamic group update
It would be wonderful if there was a way to trigger a re-sync of dynamic groups after changes are made. Right now some changes take over 24 hours to show and when experimenting with new dynamic rules it makes it difficult to see results. The trigger could be something like the Reset and Resync box in Enterprise Apps provisioning or just a Powershell applet that can be run.
Bill Kaage
shared this idea
Our feature team is looking into options for addressing this scenario, but we do not yet have any timelines to share. For now as a workaround, you can manually trigger the reprocessing by updating the membership rule to add a whitespace at the end. We’ve also added the ability to check the membership processing status, to keep track of the status and know if processing is complete.
51 comments
-
Anonymous
commented
What a brutal group. Put yourself in their shoes and then add 10k tasks to your todo list. Its not like Intune and AAD have been around as long as AD. If you are old enough to remember AD in 2000, you would no there no instant gratification with it either.
-
Leroy Simon
commented
connect-azuread
import-module azureadpreview -force
set-azureadmsgroup -id <group objectid> -membershipruleprocessingstate "paused"
set-azureadmsgroup -id <group objectid> -membershipruleprocessingstate "on"This will force a group membership enumeration.
-
Imre
commented
In our case the dynamic group was paused and we were not able to make it continue again.
For me the solution was not adding a white space but to copy the dynamic rule to a notepad first. Then change the properties from dynamic to assigned (this will retain all members). Then change it back to dynamic and add the rule back from the notepad.
-
[Deleted User]
commented
In our case the dynamic group was paused and we were not able to make it continue again.
For me the solution was not adding a white space but to copy the dynamic rule to a notepad first. Then change the properties from dynamic to assigned (this will retain all members). Then change it back to dynamic and add the rule back from the notepad.
-
We are still recommending the workaround to trigger reprocessing by updating membership rule to add a whitespace at the end and save the group. The feature team is also working on improving Dynamic group performance which will help address this issue as well.
-
Anonymous
commented
Dynamic groups are 100% useless right now, the lack of update controls is fatal and they can't be used in production in any meaningful way. This is espicially troubling since support advises using them but you can have no control over them at all. If I worked at Microsoft this would be my priority. Product manager should be fired.
-
Darren
commented
Would be very much welcomed as causes delays in project work / testing.
-
Cooper, Damian
commented
Requesting an update on this as we are trying to use (device.devicePhysicalIds -any _ -eq "[OrderID]:***") to allow machines to use a different Hybrid join profile to our 3 domains. The only way I've been able to get this to work is to delete the group and recreate it every time. Please update this function.
-
Elliot Smith
commented
Hello Microsoft? Any update on this? Has this been considered at all? Pease say something.
-
Raja Sekhar
commented
We have requirement to create new dynamic group, By automatically to add the existing members of old “Mail enabled security” group to the new dynamic group and whenever we add the member in old “Mail enabled security” those members need to automatically update on the new dynamic group.
-
Anonymous
commented
Under review for a year! OMG really?
-
Sujithkumar
commented
The Dynamic device group which i am playing around is with the below query to fetch autopilot devices based on (devicePhysicalIDs and OrderID), when I created this group with the dymanic query rule, it picked up the existing devices based on the below query but then it didnt work for the new entry ( I would say partially worked). For example, I have assigned the same group for several services like Apps, Device Configuration and AutoPilot deployment profile. it works fine with AutoPilot deployment profile but not for the Apps and Device Configuration. therefore, it would be great to have this dynamic group working, unfortunately for now it is not fit for production.
(device.devicePhysicalIDs -any _ -contains "[ZTDId]") -and (device.devicePhysicalIds -any _ -eq "[OrderID]:EU-Devices") -
Sujithkumar
commented
The Dynamic device group which i am playing around is with the below query to fetch autopilot devices based on (devicePhysicalIDs and OrderID), when I created this group with the dymanic query rule, it picked up the existing devices based on the below query but then it didnt work for the new entry ( I would say partially worked). For example, I have assigned the same group for several services like Apps, Device Configuration and AutoPilot deployment profile. it works fine with AutoPilot deployment profile but not for the Apps and Device Configuration. therefore, it would be great to have this dynamic group working, unfortunately for now it is not fit for production.
(device.devicePhysicalIDs -any _ -contains "[ZTDId]") -and (device.devicePhysicalIds -any _ -eq "[OrderID]:Devices") -
Trond Stien
commented
This is essential for dynamic group memberships.
Currently having issues with removal/joining of group members due to no total-refresh of members.
-
Morten Trab
commented
Intune is pretty useless with dynamic device groups as these are WAY too slow to update.
We have around 2000 mobile devices which we need to target on device level, and as it is now the users are able to mess around in several settings, before policies and apps are forced. -
Anonymously Frustrated
commented
A Re-Process option exists on the licenses tab for dynamic groups, so you must have thought about this. +1 on providing a PS command to do this.
-
Anonymous
commented
we need to have the ability to update dynamic group, without the ability to update on demand, this is useless.
-
Declan
commented
+1 - Takes too long to update.
-
Anonymous
commented
This is critical for Intune devices.
-
Midtbø, Atle
commented
+1
