mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #4791] [Feature Request]: Manage E-Mail and collaboration Alert Policies through CIPP #2236
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#2236
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 @SLYNETAG on GitHub (Oct 9, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4791
Please confirm:
Problem Statement
Currently, for every tenant we configure alert policies in the security center -> Email and collaboration -> Alert Policies by hand. There are 42 policies which means per tenant we open 42 policies and set an e-mail recipient. This is (a) quite some effort and (b) unmanaged as changes need to be manually tracked or new policies updated. I could think of:
If it is not possible to do so, a doable workaround on our side would be to leave them as is (default alert to TenantAdmins) and set the alternate mail address of our admin (or breakglass) to managedTenant@... and unmanagedTenant@ and filter on the ticketing system side. This would affect all notifications though.
Benefits for MSPs
If CIPP were to allow us to configure these policies this would greatly reduce manual effort and increase quality. CIPP would have another great feature to tighten the customer relationship.
Value or Importance
Not critical as we have an existing workflow and a potential workaround but a strong nice-to-have due to the reasons stated above.
PowerShell Commands (Optional)
No response
@Zacgoose commented on GitHub (Oct 9, 2025):
If I recall correctly this is not possible by any other methods than the GUI, sorry.
@kris6673 commented on GitHub (Oct 12, 2025):
Looked at this a couple of weeks ago, and I can sadly confirm that it's not possible through any other means than the GUI :(
@HappyEarthDay commented on GitHub (Oct 17, 2025):
Thanks for confirming - we were on the hunt for this too. Hopefully Microsoft creates these api endpoints in the future