starred/CIPP

Fork 0

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

[GH-ISSUE #4114] [Feature Request]: Ability to exclude tenants from Standards when a Tenant group is selected as Include #1863

New issue

Closed

opened 2026-03-02 13:47:43 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:47:43 +03:00

Owner

Originally created by @HappyEarthDay on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4114

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

Currently, we can exclude tenants from standards ONLY when the standard targets AllTenants.

We require the ability to exclude a tenant from a specific standard if the standard is targeting a Tenant Group. For example, we have a tenant group called "High Security clients". We have a few standards templates that apply settings to this tenant group, and if a single client needs to be excluded from a single standards template, we can't do that.

Ideally, we'd be able to exclude individual tenants from any standards template, regardless of what it is targeting.

Benefits for MSPs

Being able to exclude tenants generally is crucial for specific client needs and industries.

Value or Importance

This limits our ability to deploy standards en masse and troubleshoot them effectively. To troubleshoot and turn off the settings, we have to exclude the client from all standards associated with the group (remove the client from the group), which is not a good solution.

PowerShell Commands (Optional)

No response

Originally created by @HappyEarthDay on GitHub (May 20, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4114 ### 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 Currently, we can exclude tenants from standards ONLY when the standard targets AllTenants. We require the ability to exclude a tenant from a specific standard if the standard is targeting a Tenant Group. For example, we have a tenant group called "High Security clients". We have a few standards templates that apply settings to this tenant group, and if a single client needs to be excluded from a single standards template, we can't do that. Ideally, we'd be able to exclude individual tenants from any standards template, regardless of what it is targeting. ### Benefits for MSPs Being able to exclude tenants generally is crucial for specific client needs and industries. ### Value or Importance This limits our ability to deploy standards en masse and troubleshoot them effectively. To troubleshoot and turn off the settings, we have to exclude the client from all standards associated with the group (remove the client from the group), which is not a good solution. ### PowerShell Commands (Optional) _No response_

kerem

2026-03-02 13:47:43 +03:00

closed this issue
added the
enhancement

no-priority

not-assigned
labels

kerem commented

2026-03-02 13:47:44 +03:00

Author

Owner

@ndit-dev commented on GitHub (May 27, 2025):

+1
I would always like to be able to apply exclude, even when only single tenants are choosen. I have a few standards that I absolutely not want pushed to my partner tenant or my template tenant for intune policies for example. Would sleep better if I could add them as excluded tenant for said standards.

@ndit-dev commented on GitHub (May 27, 2025): +1 I would always like to be able to apply exclude, even when only single tenants are choosen. I have a few standards that I **absolutely not** want pushed to my partner tenant or my template tenant for intune policies for example. Would sleep better if I could add them as excluded tenant for said standards.

kerem commented

2026-03-02 13:47:44 +03:00

Author

Owner

@ndit-dev commented on GitHub (May 27, 2025):

https://github.com/KelvinTegelaar/CIPP/issues/3907

@ndit-dev commented on GitHub (May 27, 2025): https://github.com/KelvinTegelaar/CIPP/issues/3907

kerem referenced this issue

2026-03-02 13:58:25 +03:00

[PR #1863] [MERGED] Add Sign-In Status to UserDetails #3456

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#1863

No description provided.

Rows
Columns