-
Notifications
You must be signed in to change notification settings - Fork 491
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
New-M365DSCDeltaReport: "No discrepancies have been found!" when adding an exclusion to Conditional Access Policies #4680
Comments
From what I can tell, this seems to be happening once the 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. |
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... |
@cstringham I'm experiencing the same issue. I'm getting the same issue when I'm testing with these cmdlets:
The only place left, where I can find any "-" is in the name of the actual Conditional Access policy. Could that be the cause? |
Description of the issue
When running the
New-M365DSCDeltaReport
command against two reports, I am getting no discrepancies despite having added an account to the excluded users list for one of our policies. I have also tested this on Microsoft365DSC Version 1.24.515.2 to the same result.Source Config
Destination Config
HTML Delta Report
Microsoft 365 DSC Version
V1.24.424.1
Which workloads are affected
Azure Active Directory (Entra ID)
The DSC configuration
No response
Verbose logs showing the problem
No response
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: