mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #2123] [Feature Request]: Change Alert for SharePoint Storage Threshoold #1088
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1088
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
@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.
@BNWEIN commented on GitHub (Feb 28, 2024):
This has been implemented in https://github.com/KelvinTegelaar/CIPP/pull/2178