-
Notifications
You must be signed in to change notification settings - Fork 500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Group members for dynamic group/large groups #2190
Comments
Did you remove these parameters from your resource configuration? They are not mandatory and as long as you do not need these properties managed by M365DSC, I would leave them out. |
Thanks for confirming. This need to be investigated. Runtime is increasing due to the get method exporting all members… this is kind of the expected behaviour. Changing the settings without this parameters being present is not. |
NikCharlebois
added a commit
to NikCharlebois/Microsoft365DSC
that referenced
this issue
Sep 12, 2022
Merged
NikCharlebois
added a commit
that referenced
this issue
Sep 12, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My customer has several very big dynamic groups that they have created using M365 DSC. Prior to the recent changes in then 7/20 build, everything worked fine, however with the change to add in support for group members, there are new permission errors that show up. It looks as though membership is attempting to be reapplied, however since my groups are dynamic, group membership should not be applied explicitly (rather via rule). Additionally, this change has greatly increased the run-time from a few seconds for the resource to several minutes per group.
I'd recommend some kind of flag for when groups/licenses should be handled by DSC to allow for opting out of processing for those groups.
The text was updated successfully, but these errors were encountered: