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
The Dsc365 module is only dealing with the field 'ContentContainsSensitiveInformation'.
In our case the export is empty (no rule) et updating erase the configuration.
The sensitivity type is a custom one.
I don't find what is exactly decide to not create the hashmap ContentContainsSensitiveInformation but our case it's a big issue.
May should we replace ContentContainsSensitiveInformation fields with AdvancedRule that is supported in the xxx-DlpComplianceRule commands.
But it could be a breaking change.
Microsoft 365 DSC Version
1.23.1018.1 & 1.23.1025.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
The text was updated successfully, but these errors were encountered:
Description of the issue
When defined a compliance rule.
When running the command 'Get-DlpComplianceRule' it returns:
The Dsc365 module is only dealing with the field 'ContentContainsSensitiveInformation'.
In our case the export is empty (no rule) et updating erase the configuration.
The sensitivity type is a custom one.
I don't find what is exactly decide to not create the hashmap
ContentContainsSensitiveInformation
but our case it's a big issue.May should we replace
ContentContainsSensitiveInformation
fields withAdvancedRule
that is supported in thexxx-DlpComplianceRule
commands.But it could be a breaking change.
Microsoft 365 DSC Version
1.23.1018.1 & 1.23.1025.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
The text was updated successfully, but these errors were encountered: