starred/CIPP

Fork 0

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

[GH-ISSUE #3924] [Feature Request]: Ability to rename CAPs, Intune policies, and groups in CIPP #1760

New issue

Closed

opened 2026-03-02 13:46:51 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:46:51 +03:00

Owner

Originally created by @HappyEarthDay on GitHub (Apr 3, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3924

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

This is a duplicate of #3487

As an MSP, we aim to streamline the deployment of conditional access policies, Intune templates, and groups by leveraging the Standards policy templates in CIPP. However, a significant challenge arises from the manual work required to rename existing policies in each tenant to align with the CIPP-deployed standard naming for each policy.

When onboarding new clients or deploying standards to those that don't yet have them, we must manually rename pre-existing policies to match our standards. For instance, if a CIPP-deployed standard Intune policy is named "MSP Standard - BitLocker Enforcement" but the client's tenant already has a policy named "BitLocker Enforcement," CIPP would deploy a duplicate policy instead of updating the existing one. To prevent this, we currently have to access the client's portal via GDAP and manually rename the policy.

It's the same with Groups. We already have all of the members in a group with the same purpose, but it just has a different name.

Benefits for MSPs

Having the ability to rename policies directly within the CIPP interface would significantly improve efficiency, allowing us to seamlessly align existing policies with CIPP-deployed standards. This enhancement would save substantial time, increase the tool's value to our team, and build greater trust in its functionality.

You might wonder: why not simply remove the old policy and allow the new one to take effect? The answer lies in preserving manually configured exclusions for users or groups within the existing policies. CIPP does not typically modify exclusions, and removing the old policy would require manually recreating those exclusions in the new CIPP-deployed policy. By enabling a renaming feature within CIPP, we can retain these configurations while avoiding the duplication of policies.

Value or Importance

This improvement would transform CIPP into an even more powerful tool for our staff, reducing overhead and ensuring a smoother deployment process across all tenants.

PowerShell Commands (Optional)

No response

Originally created by @HappyEarthDay on GitHub (Apr 3, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3924 ### 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 ## **This is a duplicate of #3487** As an MSP, we aim to streamline the deployment of conditional access policies, Intune templates, and groups by leveraging the Standards policy templates in CIPP. However, a significant challenge arises from the manual work required to rename existing policies in each tenant to align with the CIPP-deployed standard naming for each policy. When onboarding new clients or deploying standards to those that don't yet have them, we must manually rename pre-existing policies to match our standards. For instance, if a CIPP-deployed standard Intune policy is named "MSP Standard - BitLocker Enforcement" but the client's tenant already has a policy named "BitLocker Enforcement," CIPP would deploy a duplicate policy instead of updating the existing one. To prevent this, we currently have to access the client's portal via GDAP and manually rename the policy. It's the same with Groups. We already have all of the members in a group with the same purpose, but it just has a different name. ### Benefits for MSPs Having the ability to rename policies directly within the CIPP interface would significantly improve efficiency, allowing us to seamlessly align existing policies with CIPP-deployed standards. This enhancement would save substantial time, increase the tool's value to our team, and build greater trust in its functionality. You might wonder: why not simply remove the old policy and allow the new one to take effect? The answer lies in preserving manually configured exclusions for users or groups within the existing policies. CIPP does not typically modify exclusions, and removing the old policy would require manually recreating those exclusions in the new CIPP-deployed policy. By enabling a renaming feature within CIPP, we can retain these configurations while avoiding the duplication of policies. ### Value or Importance This improvement would transform CIPP into an even more powerful tool for our staff, reducing overhead and ensuring a smoother deployment process across all tenants. ### PowerShell Commands (Optional) _No response_

kerem

2026-03-02 13:46:51 +03:00

closed this issue
added the
enhancement

no-priority

no-activity
labels

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Apr 13, 2025):

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.

@github-actions[bot] commented on GitHub (Apr 13, 2025): 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.

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Apr 20, 2025):

This issue was closed because it has been stalled for 14 days with no activity.

@github-actions[bot] commented on GitHub (Apr 20, 2025): This issue was closed because it has been stalled for 14 days with no activity.

kerem referenced this issue

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

[PR #1760] [MERGED] Scheduler: Update text and filters #3400

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

No description provided.

Rows
Columns