-
Notifications
You must be signed in to change notification settings - Fork 520
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
Conditional access policies: bug with ExcludePlatforms #2337
Comments
Based on the current documentation these values should still be supported. Could you test to set this property manually by calling
|
I assume you were hand-editing the config file to add the ExcludePlatforms properties. When you specify ExcludePlatforms via the portal, the default for IncludePlatforms becomes "all" (or selected platform), sending a null entry is likely generating the error. |
@semangard Could you check if you configuration is working fine by adding "all" to |
Hi @andikrueger not better :
does not work (for CA state = reporting mode): |
Curious - Using 1.22.1005.1 I was able to replicate your error with an empty entry and resolve by adding "All" using the following based on your initial config: AADConditionalAccessPolicy 57138c28-1e7a-4e5b-9f40-590a770b1df8 |
@mlhickey thank you for the support with this issue! @semangard please let us know, if the suggestions work. Please review the .mof file, if there are any issues with the „placeholders“ of yours. |
@mlhickey / @andikrueger : well, here is my last piece of code tested (in UPDATE MODE) and I think I understood my issue:
As you can see I tested various combinations with ExcludePlatforms and IncludePlatforms => Here are ONLY combinations which work:
=> MAM policies ( BuiltInControls = @("approvedApplication") do not support includePlatforms = "All" and support only devices "android" and/or "iOS". ==> SO, it would be great if the tool could raise for MAM policies an explicit error at the compilation: Note: I used variables just to factorize few things among conditional access policies and to easily switch the state from ON to OFF for ex |
@semangard - makes sense. If you only specify the include set, exclude doesn't need to be evaluated. If you specify exclude, CA needs to know what the working set is that items are being excluded from, hence the default of All if you do this via the portal. |
Details of the scenario you tried and the problem that is occurring
Hello,
It seems that the
ExcludePlatforms
property raises some issues:Only the last value (empty array) currently works.
Verbose logs showing the problem
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
Office365
Version of the DSC module that was used ('dev' if using current dev branch)
The text was updated successfully, but these errors were encountered: