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
When using Export-M365DSCConfiguration with EXOTransportRule resources, some array properties show no value on the DSC result file while the get-transport rule cmdlet shows that the value is properly set.
I'm using the last M365DSC version and dependencies are up to date.
I have detected the issue at least on the following properties: ExceptIfHeaderContainsWords, FromAddressContainsWords, ExceptIfHeaderContainsWords.
For example for the policy below the "ExceptIfHeaderContainsWords" value (I have removed the other properties to keep it short:
DSC result file:
EXOTransportRule "EXOTransportRule-Email Tagging - Unverified Sender"
{
ExceptIfHeaderContainsWords =@();
}
Get-TransportRule:
Get-TransportRule"Email Tagging - Unverified Sender"|select ExceptIfHeaderContainsWords
ExceptIfHeaderContainsWords
{1}
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered:
This is indeed cause by this PR, which was released in 1.24.1127.1. Have also found a possible solution, but am now first checking what the rationale was of that earlier change.
Description of the issue
When using Export-M365DSCConfiguration with EXOTransportRule resources, some array properties show no value on the DSC result file while the get-transport rule cmdlet shows that the value is properly set.
I'm using the last M365DSC version and dependencies are up to date.
I have detected the issue at least on the following properties: ExceptIfHeaderContainsWords, FromAddressContainsWords, ExceptIfHeaderContainsWords.
Microsoft 365 DSC Version
1.24.1211.1
Which workloads are affected
Exchange Online
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: