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
SCAutoSensitivityLabelRule - Setting error #4641
Labels
Comments
andikrueger
added
Bug
Something isn't working
Security & Compliance Center
V1.24.424.1
Version 1.24.424.1
labels
May 6, 2024
Fixed this locally togother with @ykuijs by adjusting this on line 625 : From $HeaderMatchesPatternsValue = @{}
if ($null -ne $HeaderMatchesPatterns -and $null -ne $HeaderMatchesPatterns.Name)
{
$HeaderMatchesPatternsValue.Add($HeaderMatchesPatterns.Name, $HeaderMatchesPatterns.Values)
} To : if ($null -ne $HeaderMatchesPatterns -and $null -ne $HeaderMatchesPatterns.Name)
{
$HeaderMatchesPatternsValue = @{}
$HeaderMatchesPatternsValue.Add($HeaderMatchesPatterns.Name, $HeaderMatchesPatterns.Values)
} Have to note when running this there is a notification that the min and maxconfidence is deprecated and will be replaced by confidencelevel |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description of the issue
When importing an SCAutoSensitivityLabelRule it fails because during the proces the variable $HeaderMatchesPatterns is getting filled even when it's not even specified in the configuration.
`[DBG]: [Process:52604]: [Runspace195]: PS C:\WINDOWS\system32>> $CreationParams
Key Value
Name General Data Protection Regulation (GDPR) Enhanced-ODB
Policy Labelingpolicy
ContentContainsSensitiveInformation {System.Collections.Hashtable, System.Collections.Hashtable, System.Collections.H...
Disabled False
DocumentIsPasswordProtected False
DocumentIsUnsupported False
ExceptIfDocumentIsPasswordProtected False
ExceptIfDocumentIsUnsupported False
ExceptIfProcessingLimitExceeded False
ProcessingLimitExceeded False
ReportSeverityLevel Low
Workload Exchange
HeaderMatchesPatterns {}
Verbose True
`
When creating the labelpolicyrule you'll get this error
Write-ErrorMessage : |Microsoft.Exchange.Management.UnifiedPolicy.ErrorPredicateLocationSupportException|Using the 'HeaderMatchesPatterns' parameter is supported only for Exchange content. Either remove this parameter or turn on only the Exchange location.
Microsoft 365 DSC Version
1.24.424.1
Which workloads are affected
Security & Compliance Center
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: