-
Notifications
You must be signed in to change notification settings - Fork 499
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
SCDLPComplianceRule - AccessScope - Cannot convert value "System.Collections.Generic.List1[System.String]" #3463
Comments
FYI, this still happens on 1.23.712.1 Is there any workaround if we cannot specify AccessScope? |
Just confirmed the same issue still happens on 1.23.719.1 |
Should the unit tests for this resource specify AccessScope? The config provided in the docs has it, but the unit test doesn't. https://microsoft365dsc.com/resources/security-compliance/SCDLPComplianceRule/ |
Just updated to the latest release - same error on 1.23.726.1 |
|
This comment was marked as duplicate.
This comment was marked as duplicate.
We are having the same issue, is there a fix due soon? |
Per william-boyd comment "Should the unit tests for this resource specify AccessScope? The config provided in the docs has it, but the unit test doesn't." |
Details of the scenario you tried and the problem that is occurring
SCDLPComplianceRule - AccessScope - Cannot convert value
I am deploying one DLPComplianceRule. When specifying
AccessScope
it always fails with the same error. When removing this key, the configuration succeeds.Verbose logs showing the problem
##[error]Cannot process argument transformation on parameter 'AccessScope'. Cannot convert value
"System.Collections.Generic.List
1[System.String]" to type "System.Nullable
1[Microsoft.Office.CompliancePolicy.Tasks.AccessScope]". Error: "Unable to match the identifier nameSystem.Collections.Generic.List`1[System.String] to a valid enumerator name. Specify one of the following enumerator
names and try again: InOrganization, NotInOrganization, None"
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
Windows Server 2022
Version of the DSC module that was used ('dev' if using current dev branch)
1.23.628.1
The text was updated successfully, but these errors were encountered: