[Feature Request]: #4496
Description
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
I opened this issue already but it was closed, I do have a screenshot of our sponsorship payment but unsure the best way or providing this to Kelvin.
(original issue #4420)
Original issue-
I searched the feature requests and I do not see it, please make me aware if I missed something 😊
(Closest one I found was #3906)
The basic idea here is that CIPP already has the ability to deploy Policies via the standards & templates, but we do not get full control of the policy deployment.
For example the anti-spam policy deploys with the SPF hard fail setting enabled and is not adjustable from the standards template in CIPP.
If we could import a policy that we have in .json format and mass deploy it to clients that would be ideal.
This way we can stipulate the policy name we want, what settings we want enabled, what status to deploy in, etc without it needing to be defined as a standard by CIPP devs.
It would be great if we could also export policies that CIPP can see to .json so we can quickly iterate and mass-deploy.
Benefits for MSPs
This would reduce manual work the same way that standards do however with the added benefit of configuration and general wide-applicability.
Specifically for my MSP, we would use this to deploy policies that have the settings we need with our branded name rather than the "CIPP Anti-Spam" default names.
Value or Importance
This is borderline critical for my MSP, but we will be pursuing this using CIPPAPImodule.
The reason this would be nice to have is that CIPP wouldn't need to keep up with Microsoft in defining standards for it's users.
This .json approach would enable advanced users to have more customization and management over what is being deployed with what settings.
PowerShell Commands (Optional)
No response