New-M365DSCDeltaReport - No discrepancies have been found about microsoft365dsc HOT 10 CLOSED

Totally understand. I will get the files updated, make sure they still throw the error, and send them over. Thanks!

from microsoft365dsc.

Ahh... that is a good first step. Easy to see in VS Code. Thanks again!

from microsoft365dsc.

@adambrubaker It would be very helpful to have the configuration. What you can do is anonymize and remove some of the configuration but still have the error be reproducible. Just a minimal amount of configuration so that we can have a look at that, doesn't have to be the complete one.

from microsoft365dsc.

OK so strange stuff here. I deleted all sections that matched and just left the 3 that were different. I kept all the header and footer information, open/close brackets, etc.

When I run the New-M365DSCDeltaReport command against these new files with only the 3 sections it produces a perfect report that shows all 3 differences.

So I'm only able to reproduce the results with a bunch of other config info that is the same. Does that make any sense? I can probably anonymize the full configs, but it will take me a while to get them both updated. Any other ideas?

from microsoft365dsc.

@adambrubaker Sounds very interesting tbh, but for a full investigation we unfortunately need the configuration from you. It would be really helpful if you could provide that. I think removing anything that could identify the company you're working for should already be enough for the anonymization part, since the ids and the selectable configuration cannot be traced back to you.

from microsoft365dsc.

OK I got them cleaned up and they still show "No discrepancies have been found". I had to update the file extensions to .txt so they would upload. They were originally .ps1 files. Thanks!

dsc_config.06182024.txt
dsc_config.06192024.txt

from microsoft365dsc.

@adambrubaker Thanks a lot for the configuration. I already found an issue in the resource for EXOTransportRule "EXOTransportRule-Mail_Delivery", there the property SubjectOrBodyContainsWords (which is an array) has an invalid escaped string: ""Remote server returned '554 5.7.0 < #5.7.520 smtp;","Your organization does not allow external forwarding. Please contact your administrator for further assistance". At the beginning of that string, there is a single " missing.

If I add that and retry the comparison, three differences are outputted:

• EXOTransportRule-Message Tagging for Company Tenants
• ODSettings
• EXOTransportRule-Adam Testing

Can you try and do the same on your side, just to check if it also works?

Edit: Did you export the configuration that way? Then maybe there is an issue with the DSCParser that we would have to check.

from microsoft365dsc.

@FabienTschanz thanks for the quick response. That was the issue! After removing those quotes I'm able to see the changes in my configs using New-M365DSCDeltaReport now. I'm glad it was an easy fix. To answer your question the quotes were in our config. It wasn't an issue with the export.

Question. If I see something similar again is there any way I can troubleshoot this on my own? Are you leveraging some other module I can download and use or is it something custom in the Microsoft365DSC module?

For those playing along at home the quotes in front of the word Remote in my Exchange Transport Rule was causing the issue. I just removed that first character. Screenshot below.

from microsoft365dsc.

@adambrubaker Glad we got it worked out. The basic troubleshooting can be done by using VS Code and the PowerShell extension, which highlights potential issues with your configuration since there is syntax highlighting and an automatic check of the configuration when it is opened in the editor. For additional information during the runtime (e.g. when using Export-M365DSCConfiguration or something like that), you can add the -Verbose switch parameter to the command and you might get more information from that output.

But it's always quite good to open an issue, since there might be another problem in place than just something "obvious" (like the double quotes in your case here). So feel free to drop by and ask 😄

from microsoft365dsc.

@adambrubaker If it's work for you now, do you mind closing the issue?

from microsoft365dsc.