starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 08:16:01 +03:00

[GH-ISSUE #5344] [Feature Request]: Assignment Filters support for All users and All Devices #2577

New issue

Closed

opened 2026-03-02 13:53:28 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 13:53:28 +03:00

Owner

Originally created by @Cyclone47 on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5344

Originally assigned to: @kris6673 on GitHub.

Please confirm:

I have searched existing feature requests (open and closed) and found no duplicates.
**me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

CIPP currently supports assignment filters only for custom groups. However, Microsoft Intune natively allows assignment filters to be applied to "All Users" and "All Devices" assignments with both include and exclude modes. When deploying standards or policies through CIPP to all devices, I cannot apply assignment filters without first creating custom groups. This means I either need to manually add filters in the Intune portal after CIPP deployment, or create unnecessary custom groups just to leverage filter functionality that should work with "All Devices" and "All Users" assignments.
https://github.com/KelvinTegelaar/CIPP/issues/4721 has addressed the custom groups implementation but did not address the all devices or all users with assignment filters.

Current implementation:

Example of the Custom Groups option:

Benefits for MSPs

This feature would reduce manual work for MSPs by eliminating the need to configure assignment filters in the Intune portal after CIPP deployments. It would also reduce the overhead of creating and maintaining custom groups solely for filtering purposes. For baseline deployments targeting all users or devices, MSPs could apply filters directly during CIPP configuration without additional post deployment steps.

Common use cases include filtering by OS version, device ownership type (Corporate vs BYOD), device manufacturer, device model, device category, enrollment profile name, or combining multiple criteria to target specific hardware configurations while deploying to "All Devices" or "All Users".

Value or Importance

While not critical, this feature is very valuable as it provides feature parity with native Microsoft Intune capabilities and eliminates workarounds. In my specific use case, dynamic groups often don't propagate fast enough, resulting in Autopilot delays or issues. Using assignment filters on "All Devices" assignments would avoid this problem entirely. Additionally, this feature would be particularly useful for temporary exclusions during testing, OS version-specific deployments, and device ownership filtering all without the complexity of creating and maintaining dynamic groups. It streamlines a workflow that MSPs perform regularly across multiple client tenants.

PowerShell Commands (Optional)

No response

Originally created by @Cyclone47 on GitHub (Feb 10, 2026). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5344 Originally assigned to: @kris6673 on GitHub. ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement CIPP currently supports assignment filters only for custom groups. However, Microsoft Intune natively allows assignment filters to be applied to "All Users" and "All Devices" assignments with both include and exclude modes. When deploying standards or policies through CIPP to all devices, I cannot apply assignment filters without first creating custom groups. This means I either need to manually add filters in the Intune portal after CIPP deployment, or create unnecessary custom groups just to leverage filter functionality that should work with "All Devices" and "All Users" assignments. https://github.com/KelvinTegelaar/CIPP/issues/4721 has addressed the custom groups implementation but did not address the all devices or all users with assignment filters. Current implementation: <img width="229" height="165" alt="Image" src="https://github.com/user-attachments/assets/c8d8683a-889d-4d97-be59-2cfcadf80614" /> Example of the Custom Groups option: <img width="261" height="248" alt="Image" src="https://github.com/user-attachments/assets/cd254edf-a9e6-449c-9c9d-12c7035b53ae" /> ### Benefits for MSPs This feature would reduce manual work for MSPs by eliminating the need to configure assignment filters in the Intune portal after CIPP deployments. It would also reduce the overhead of creating and maintaining custom groups solely for filtering purposes. For baseline deployments targeting all users or devices, MSPs could apply filters directly during CIPP configuration without additional post deployment steps. Common use cases include filtering by OS version, device ownership type (Corporate vs BYOD), device manufacturer, device model, device category, enrollment profile name, or combining multiple criteria to target specific hardware configurations while deploying to "All Devices" or "All Users". ### Value or Importance While not critical, this feature is very valuable as it provides feature parity with native Microsoft Intune capabilities and eliminates workarounds. In my specific use case, dynamic groups often don't propagate fast enough, resulting in Autopilot delays or issues. Using assignment filters on "All Devices" assignments would avoid this problem entirely. Additionally, this feature would be particularly useful for temporary exclusions during testing, OS version-specific deployments, and device ownership filtering all without the complexity of creating and maintaining dynamic groups. It streamlines a workflow that MSPs perform regularly across multiple client tenants. ### PowerShell Commands (Optional) _No response_

kerem

2026-03-02 13:53:28 +03:00

closed this issue
added the
enhancement

no-priority

not-assigned
labels

kerem commented

2026-03-02 13:53:29 +03:00

Author

Owner

@kris6673 commented on GitHub (Feb 13, 2026):

I would like to work on this please!

@kris6673 commented on GitHub (Feb 13, 2026): I would like to work on this please!

kerem commented

2026-03-02 13:53:29 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 13, 2026):

Great! I assigned you (@kris6673) to the issue. Have fun working on it!

@github-actions[bot] commented on GitHub (Feb 13, 2026): Great! I assigned you (@kris6673) to the issue. Have fun working on it!

kerem commented

2026-03-02 13:53:29 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Feb 15, 2026):

added to dev

@KelvinTegelaar commented on GitHub (Feb 15, 2026): added to dev

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#2577

No description provided.

Rows
Columns