You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We apply a lot of InTune Templates using Standards, as well as Group Templates.
That said we have a few policies we want to exclude specific groups from - right now, standards basically overwrite the Excluded field which is not good in cases where we want to apply to all devices / users but also need to have some fine grained control.
Can we please have the "Exclude" option made available in Standards similar to how InTune functions now? It would be identical to the below, just another section for Exclude instead of Include:
Thank you,
PowerShell commands you would normally use to achieve above request
No response
The text was updated successfully, but these errors were encountered:
I did mean to include that in #2540 😬 would be awesome to have.
Currently, I find myself working around it by writing exclusions into my dynamic groups and that just gets messy
This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.
We apply a lot of InTune Templates using Standards, as well as Group Templates.
That said we have a few policies we want to exclude specific groups from - right now, standards basically overwrite the Excluded field which is not good in cases where we want to apply to all devices / users but also need to have some fine grained control.
Can we please have the "Exclude" option made available in Standards similar to how InTune functions now? It would be identical to the below, just another section for Exclude instead of Include:
Thank you,
PowerShell commands you would normally use to achieve above request
No response
The text was updated successfully, but these errors were encountered: