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

SCRoleGroup: Inconsistent Resource state because of missing Property on creation, Drifts because of returned Role Format #5036

Closed
afloca opened this issue Sep 11, 2024 · 0 comments · Fixed by #5037 or #5132

Comments

@afloca
Copy link
Contributor

afloca commented Sep 11, 2024

Description of the issue

Issue #1
Creating a Purview Rolegroup with DSC leads to a corrupted and inconsistent Role Group because of missing DislayName:
image
Issue #2
Get-Target Resource returns Roles in format that cannot be used for creation or drift detection
Expected Format for creation:
Roles = @("Communication Compliance Case", "Communication Compliance Viewer")
Actual returned format
Roles = @("FFO.extest.microsoft.com/Microsoft Exchange Hosted Organizations/tenant.onmicrosoft.com/Communication Compliance Case Management","FFO.extest.microsoft.com/Microsoft Exchange Hosted Organizations/tenant.onmicrosoft.com/Communication Compliance Viewer"):
Result: After creation using expected format, the resource will be in a continuous drift
image
Creation using the full format("FFO.extest.microsoft.com/Microsoft Exchange Hosted Organizations/tenant.onmicrosoft.com/Compliance Search") would fail:
Ex75BFC9|Microsoft.Exchange.Configuration.Tasks.ManagementObjectAmbiguousException|Multiple management roles exist
that match the value "FFO.extest.microsoft.com/Microsoft Exchange Hosted
Organizations/tenant.onmicrosoft.com/Compliance Search"

Microsoft 365 DSC Version

1.24.904.1

Which workloads are affected

Security & Compliance Center

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
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant