MemberOf Approval Workflow?

Hello, David.

Creating a workflow that responds to a group membership change event is "run-of-the-mill", point-and-click configuration in a workflow, as you probably know. If you only have a handful of the groups that you know to be "large", then you could create a Managed Unit that contains these groups and have the Workflow configured to target only said Managed Unit. If you must have logic that filters dynamically based on the size of the group, then that would likely have to be scripted. It's not all that complex a script, for what it's worth, but obviously if you could get away with the Managed Unit path that might be easier to manage since there would be no code.

Hope that helps!

Shawn

Was thinking about this - you could populate a virtual attribute on groups that you consider large and look for the contents of attribute in the start conditions of your workflow that is reacting to a group being added to a group.  For example,  edsvaIsLargeGroup = TRUE.

If you wanted to get really elaborate, you could even have a scheduled Automation Workflow that goes out periodically and "scans" your AD groups to find the ones that meet your criteria of large - for example, those with more than 100 members and automatically "tags" them as I have suggested above.   You would just need a little bit of Powershell code to supply the member counts to the Automation Workflow but the rest could be codeless - i.e. relying only on built-in workflow Activities.

Just some food for thought.