Products
...
Capabilities
Managing Azure Only Distribution Lists in Activate
5 min
managing azure groups with activate activate uses the microsoft graph rest api for all management of azure where possible the rest api provides high performance and is recommended by microsoft as the preferred option however, there are limitations on the types of groups that can be managed this way, as outlined in the microsoft graph groups overview group types in microsoft graph in microsoft graph, the type of group can be identified by the settings of its grouptype, mailenabled, and securityenabled properties, as shown below true 132,132,132,132,133 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type key limitation mail enabled groups that are not microsoft 365 groups cannot be managed using microsoft graph microsoft recommends using microsoft 365 groups customer scenarios some customers still wish to use mail enabled distribution groups (dls) that are not microsoft 365 groups this was not possible in versions before v8 v8 support in v8 , we have enabled this functionality however, this requires using powershell to manage these groups the process is mostly seamless to scripts and processes within activate, but there are important limitations and known issues limitations and known issues there is a 5–10 second delay when first connecting to exchange online the first time a session is started this can occur any time an action is required against a dl the group types in adcache are used to determine the group type if the group type changes between syncs, the wrong action may be taken and the action may fail each action requiring powershell is 6–10 times slower than using graph as a result adding large numbers of users or bulk changes will be slower for these groups large scale changes may hit powershell execution limits recommendation microsoft strongly recommends using microsoft 365 groups where possible to avoid these limitations