-
Notifications
You must be signed in to change notification settings - Fork 490
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
IntuneAppProtectionPolicyiOS Doesn't accept multiple arguments for TargetedAppManagementLevels #5032
Comments
@acmcg I'm trying to find the appropriate property in the GUI, but unfortunately, I can't find it. Where can I recreate so that this property changes its value? |
@acmcg I am unable to select anything in that dropdown. Do I have to configure some specific settings for it to work? Can you try and create a new policy and configure the same setting there? To me it seems that Microsoft moved this setting to the filter in the assignments, that's why we can't select anything there in new policies. |
@acmcg How do I have to configure a new policy so that it shows as assigned to unmanaged devices, just like in your screenshot? Updating something what we can‘t do anymore in the Intune portal isn‘t really something we want to do because nobody would use that (simply because they wouldn‘t know it existed). |
You can't do this manually now from the portal. To your point above, if we don't support the use of multiple values for 'Device Types' the exports from existing policies are not useful (they cannot be imported). |
@acmcg I opened a Pull Request to address the situation. Checked it on my side, and it's working, if you specify the property like |
Description of the issue
IntuneAppProtectionPolicyiOS doesn't accept multiple arguments for TargetedAppManagementLevels, which it should, e.g. 'unmanaged,mdm'
works if you specify 'unmanaged' or 'mdm', but not when there are multiple items
Microsoft 365 DSC Version
1.24.731.1
Which workloads are affected
Intune
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
No response
The text was updated successfully, but these errors were encountered: