Skip to content
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

[Feature Request]: Ability to rename CAPs, Intune policies, and groups in CIPP #3487

Open
HappyEarthDay opened this issue Jan 27, 2025 · 2 comments
Labels
enhancement New feature or request no-priority

Comments

@HappyEarthDay
Copy link

Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.

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.

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.

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 you would normally use to achieve above request

No response

@HappyEarthDay HappyEarthDay added enhancement New feature or request no-priority labels Jan 27, 2025
@KelvinTegelaar
Copy link
Owner

So you want to rename the existing policies, not the templates, right?

@HappyEarthDay
Copy link
Author

So you want to rename the existing policies, not the templates, right?

Exactly - We want to rename the existing policies and groups within the Microsoft tenants.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request no-priority
Projects
None yet
Development

No branches or pull requests

2 participants