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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: