You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details of the scenario you tried and the problem that is occurring
My DSC deployment is working just fine. But when I edit the "ExcludeUsers" of AADConditionalAccessPolicy Resource (remove value), it doesn't actually update on the policy and the user is still excluded. I get no error, the whole DSC-Configuration is running just fine (verbose) and does complete the "set" procedure. In the Azure Portal, I can see that "Modified Date" of the ConditionalAccessPolicy changed to the corresponding time, but the configuration did actually not change according to the new DSC-Configuration file, as described.
Btw. a colleague of mine noticed similar issues on SPO related settings.
Verbose logs showing the problem
none
Suggested solution to the issue
M365DSC should either log an error, or actually change the configuration as it is supposed to do :-)
The DSC configuration that is used to reproduce the issue (as detailed as possible)
# insert configuration here
The operating system the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
1.22.601.1
The text was updated successfully, but these errors were encountered:
Just want to make sure we understand the scenario. For example, you have a CAP with 2 excluded users, then you remove one of the 2 users from the config, and apply it. This user is never removed from the ExcludedUsers? We are not able to repro on our end for whatever reason. Thanks
Details of the scenario you tried and the problem that is occurring
My DSC deployment is working just fine. But when I edit the "ExcludeUsers" of AADConditionalAccessPolicy Resource (remove value), it doesn't actually update on the policy and the user is still excluded. I get no error, the whole DSC-Configuration is running just fine (verbose) and does complete the "set" procedure. In the Azure Portal, I can see that "Modified Date" of the ConditionalAccessPolicy changed to the corresponding time, but the configuration did actually not change according to the new DSC-Configuration file, as described.
Btw. a colleague of mine noticed similar issues on SPO related settings.
Verbose logs showing the problem
none
Suggested solution to the issue
M365DSC should either log an error, or actually change the configuration as it is supposed to do :-)
The DSC configuration that is used to reproduce the issue (as detailed as possible)
# insert configuration here
The operating system the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
1.22.601.1
The text was updated successfully, but these errors were encountered: