-
Notifications
You must be signed in to change notification settings - Fork 531
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
AADConditionalAccessPolicy: deployment bug since version 1.24.522.1. It's working with 1.24.515.2 #4725
Comments
Both logs show that the deployment fails, do you have a log of one that succeeds? |
Sorry for that. I corrected the log. |
hello, Moreover, in the eventlog, you may see the below error I have one computer with module Microsoft365dsc version 1.24.522.1. I have update the Microsoft365dsc recently. Moreover, I can see that new export have new option for "TransferMethods" in conditionaccess settings. Does any one manage to create and update conditionalAccess object with version 1.24.522.1 ? |
hello, The M365DSC team has switched from "Update-MgBetaIdentityConditionalAccessPolicy" to Invoke-MgGraphRequest. |
Description of the issue
I'm not able to use the latest version 1.24.522.1 because I have a deployment bug that I don't have with 1.24.515.2. This only concerns a few conditional access policies with specific configuration. The error I get is :
If I delete the policy I get the same kind of message but with failed to create policy message.
Without changing anything else except the DSC module version, I have a different result.
I noticed that with module 1.24.522.1 I have an additional property that appears in the verbose log, which is not set with the 1.24.515.2 module. It's this one: includeGuestsOrExternalUsers=$null
Here the log when it's successfully deployed with module 1.24.515.2
And the log when it failed with module 1.24.522.1 :
Microsoft 365 DSC Version
1.24.522.1
Which workloads are affected
Azure Active Directory (Entra ID)
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
No response
The text was updated successfully, but these errors were encountered: