Skip to content
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

AADConditionalAccessPolicy - Invalid Users or Groups still commit change #4342

Closed
NikCharlebois opened this issue Feb 15, 2024 · 0 comments · Fixed by #4350 or #4357
Closed

AADConditionalAccessPolicy - Invalid Users or Groups still commit change #4342

NikCharlebois opened this issue Feb 15, 2024 · 0 comments · Fixed by #4350 or #4357
Labels
Bug Something isn't working Entra ID

Comments

@NikCharlebois
Copy link
Collaborator

Description of the issue

If an invalid user or group name is passed in one of the parameters (e.g., ExcludedGroups), M365DSC logs an error, and moves on to the next group. This could cause an issue where if no valid groups are specified, that the API will be called with an empty array, effectively clearing the value for the parameter on the tenant.

Microsoft 365 DSC Version

1.24.214.2

Which workloads are affected

Azure Active Directory

The DSC configuration

No response

Verbose logs showing the problem

No response

Environment Information + PowerShell Version

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Entra ID
Projects
None yet
2 participants