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

EXOTransportRule - Some array properties are returned as empty even if a value is set #5575

Closed
YenNantes opened this issue Dec 18, 2024 · 3 comments · Fixed by #5584
Closed

Comments

@YenNantes
Copy link

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

Export-M365DSCConfiguration -Components "EXOTransportRule"

Verbose logs showing the problem

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

@YenNantes
Copy link
Author

It seems that issue was introduced with version 1.24.1127.1.
probably by this change:
Image

I have rolled back to version 1.24.1120.1 and it works well.

@jadamones
Copy link

I'm experiencing similar issues as well since 1.24.1127.1 #5500

@ykuijs
Copy link
Member

ykuijs commented Dec 18, 2024

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.

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.

3 participants