New-M365DSCDeltaReport: "No discrepancies have been found!" when adding an exclusion to Conditional Access Policies about microsoft365dsc HOT 2 CLOSED

From what I can tell, this seems to be happening once the Initialize-M365DSCReporting function calls the DSCParser module using ConvertTo-DSCObject. The file content that is being passed through doesn't seem to play nice with the DSCParser module, as line 345 of the ConvertTo-DSCObject function ($Config = $AST.Find({$Args[0].GetType().Name -eq 'ConfigurationDefinitionAst'}, $False)) returns a null value causing the comparison to happen between two null values.

Not sure if this is a problem with the configs that the Microsoft365DSC module is creating or with how the DSCParser module is handling the configs. I can create an issue with the DSCParser module if that seems to be what is causing the issue.

from microsoft365dsc.

Digging into it, I have been using the tenant ID in the configuration name. The issues that I was running into seem to be because I had "-" in the name of the configuration...

from microsoft365dsc.