starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 16:26:09 +03:00

[GH-ISSUE #1554] [Feature Request]: Standards - External Quarintine Notification Email #835

New issue

Closed

opened 2026-03-02 12:45:38 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 12:45:38 +03:00

Owner

Originally created by @TetraAsh on GitHub (May 25, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1554

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.

Easily set an additional recipient for 'RequestRelease' on Quarintined Emails

Microsoft are increasing their protection around 'High Confidence Phishing'.
It is not possible to allow users to actually release these emails, they must be reviewed and released by an admin.

As an MSP we do not monitor individual admin emails in every Tenant, thus we would like to be able to set these alerts to email to external recipients, this would allow such requests from across our tenant base to be forwarded to our ticketing system and dealt with efficiently.

This has clear benefits for all MSP's to assist in managing these requests

PowerShell commands you would normally use to achieve above request

Under Connect-IPPSession
https://learn.microsoft.com/en-us/powershell/module/exchange/get-protectionalert?view=exchange-ps
https://learn.microsoft.com/en-us/powershell/module/exchange/set-protectionalert?view=exchange-ps

There is a standard alert called 'User requested to release a quarantined message'
The attribute to be edited is 'NotifyUser' and 'NotificationEnabled'

Originally created by @TetraAsh on GitHub (May 25, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1554 ### 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. Easily set an additional recipient for 'RequestRelease' on Quarintined Emails Microsoft are increasing their protection around 'High Confidence Phishing'. It is not possible to allow users to actually release these emails, they must be reviewed and released by an admin. As an MSP we do not monitor individual admin emails in every Tenant, thus we would like to be able to set these alerts to email to external recipients, this would allow such requests from across our tenant base to be forwarded to our ticketing system and dealt with efficiently. This has clear benefits for all MSP's to assist in managing these requests ### PowerShell commands you would normally use to achieve above request Under Connect-IPPSession https://learn.microsoft.com/en-us/powershell/module/exchange/get-protectionalert?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchange/set-protectionalert?view=exchange-ps There is a standard alert called 'User requested to release a quarantined message' The attribute to be edited is 'NotifyUser' and 'NotificationEnabled'

kerem

2026-03-02 12:45:38 +03:00

closed this issue
added the
enhancement

no-priority
labels

kerem commented

2026-03-02 12:45:39 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 25, 2023):

Thank you for creating a feature request!
Your current priority is set to "No Priority". No Priority Feature requests automatically get closed in two days if a contributor does not accept the FR.

If you are a sponsor you can request an upgrade of priority. To upgrade the priority type "I would like to upgrade the priority".
If you want this feature to be integrated you can always do this yourself by checking out our contributions guide at https://cipp.app/docs/dev/. Contributors to the CIPP project reserve the right to close feature requests at will.
If you'd like this feature request to be assigned to you, please comment "I would like to work on this please!".

@github-actions[bot] commented on GitHub (May 25, 2023): Thank you for creating a feature request! Your current priority is set to "No Priority". No Priority Feature requests automatically get closed in two days if a contributor does not accept the FR. If you are a sponsor you can request an upgrade of priority. To upgrade the priority type "I would like to upgrade the priority". If you want this feature to be integrated you can always do this yourself by checking out our contributions guide at https://cipp.app/docs/dev/. Contributors to the CIPP project reserve the right to close feature requests at will. If you'd like this feature request to be assigned to you, please comment "I would like to work on this please!".

kerem commented

2026-03-02 12:45:39 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (May 25, 2023):

We currently only accept feature requests by sponsors

@KelvinTegelaar commented on GitHub (May 25, 2023): We currently only accept feature requests by sponsors

kerem referenced this issue

2026-03-02 13:56:34 +03:00

[PR #835] [MERGED] Dev to release #3037

kerem referenced this issue

2026-03-02 13:56:40 +03:00

[PR #937] [MERGED] Main to dev #3060

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#835

No description provided.

Rows
Columns