Please confirm:
Problem Statement
CIPP currently performs several automatic cache synchronizations, which helps ensure data remains current. However, in larger tenants, these sync processes can become time-consuming and may consume resources for data that is not actively used.
It would be beneficial to introduce per-tenant controls that allow administrators to selectively enable or disable specific automatic syncs. For example:
- Enable automatic SharePoint sharing syncs.
- Disable automatic mailbox rules syncs.
- Configure other sync types independently as needed.
This would allow administrators to optimize performance and tailor synchronization behavior to each tenant's requirements.
Benefits for MSPs
Introducing per-tenant controls for automatic cache synchronization would provide MSPs with greater flexibility and scalability. Administrators could enable only the syncs that are relevant for each customer, reducing unnecessary processing, lowering API consumption, minimizing throttling risks, and improving performance, particularly for large tenants. This would allow CIPP to scale more efficiently while ensuring resources are focused on the features that deliver value to each tenant.
Value or Importance
its nice to have. This would reduce unnecessary processing, lower API consumption, minimize throttling risks, improve performance for large tenants.
PowerShell Commands (Optional)
No response
Please confirm:
Problem Statement
CIPP currently performs several automatic cache synchronizations, which helps ensure data remains current. However, in larger tenants, these sync processes can become time-consuming and may consume resources for data that is not actively used.
It would be beneficial to introduce per-tenant controls that allow administrators to selectively enable or disable specific automatic syncs. For example:
This would allow administrators to optimize performance and tailor synchronization behavior to each tenant's requirements.
Benefits for MSPs
Introducing per-tenant controls for automatic cache synchronization would provide MSPs with greater flexibility and scalability. Administrators could enable only the syncs that are relevant for each customer, reducing unnecessary processing, lowering API consumption, minimizing throttling risks, and improving performance, particularly for large tenants. This would allow CIPP to scale more efficiently while ensuring resources are focused on the features that deliver value to each tenant.
Value or Importance
its nice to have. This would reduce unnecessary processing, lower API consumption, minimize throttling risks, improve performance for large tenants.
PowerShell Commands (Optional)
No response