[GH-ISSUE #2123] [Feature Request]: Change Alert for SharePoint Storage Threshoold #1088

Closed
opened 2026-03-02 13:41:28 +03:00 by kerem · 2 comments
Owner

Originally created by @BNWEIN on GitHub (Feb 9, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2123

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.

We currently have a classic alert for SharePoint Storage threshold reaching 90% or above. The issue we have with this is we have customers we anywhere between 6TB and 10TB of SharePoint storage, and notifying us at 90% is just to early. Ideally, if we could edit this classic alert to allow us to choose if we want to set a % threshold, or a GB threshold would allow us to customise this more per customer.

I am sure we are not the only MSP this would be useful for. It would help avoid daily notifications for customers who still have over 600-1000GB of storage available.

PowerShell commands you would normally use to achieve above request

No response

Originally created by @BNWEIN on GitHub (Feb 9, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2123 ### 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. We currently have a classic alert for SharePoint Storage threshold reaching 90% or above. The issue we have with this is we have customers we anywhere between 6TB and 10TB of SharePoint storage, and notifying us at 90% is just to early. Ideally, if we could edit this classic alert to allow us to choose if we want to set a % threshold, or a GB threshold would allow us to customise this more per customer. I am sure we are not the only MSP this would be useful for. It would help avoid daily notifications for customers who still have over 600-1000GB of storage available. ### PowerShell commands you would normally use to achieve above request _No response_
kerem 2026-03-02 13:41:28 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 19, 2024):

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.

<!-- gh-comment-id:1951558841 --> @github-actions[bot] commented on GitHub (Feb 19, 2024): 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.
Author
Owner

@BNWEIN commented on GitHub (Feb 28, 2024):

This has been implemented in https://github.com/KelvinTegelaar/CIPP/pull/2178

<!-- gh-comment-id:1969316617 --> @BNWEIN commented on GitHub (Feb 28, 2024): This has been implemented in https://github.com/KelvinTegelaar/CIPP/pull/2178
Sign in to join this conversation.
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#1088
No description provided.