starred/CIPP

Fork 0

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

[GH-ISSUE #2560] [Feature Request]: Standard Update for Quarantine Policy #1295

New issue

Closed

opened 2026-03-02 13:43:03 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:43:03 +03:00

Owner

Originally created by @HappyEarthDay on GitHub (Jun 14, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2560

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.

Microsoft recently released these features for Quarantine management via Quarantine polcies: https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=380185

Detail on the feature:
https://petri.com/microsoft-changelog/m365-changelog-microsoft-defender-for-office-365-quarantine-end-user-allow-and-block-list-management/

A very common user request is to prevent block senders from hitting quaratine and notifying the user. Now, this is possible by setting the Quarantine policy with this setting: Quarantine Notificiation < Enable < Do not include quarantine messages from blocked sender address

In the quaratine management screen, you can still remove the filter to view the block senders (good for troubleshooting), but by default, they will be hidden, and no emails will be sent to end users when a block sender email comes in.

We'd liek not only to specify hiding them from the view, but also setting the user's access to : Delete, Preview, Block Sender (NOT Allow Sender). Maybe making this a variable field in the Standards would be good, as other MSPs likely have other preferences for this.

PowerShell commands you would normally use to achieve above request

Honestly not sure about this. CIPP can deploy and update a Quarantine policy rght now, so hopefully MS as a new API endpoint for theses settings?

Originally created by @HappyEarthDay on GitHub (Jun 14, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2560 ### 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. Microsoft recently released these features for Quarantine management via Quarantine polcies: https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=380185 Detail on the feature: https://petri.com/microsoft-changelog/m365-changelog-microsoft-defender-for-office-365-quarantine-end-user-allow-and-block-list-management/ A very common user request is to prevent block senders from hitting quaratine and notifying the user. Now, this is possible by setting the Quarantine policy with this setting: Quarantine Notificiation < Enable < _Do not include quarantine messages from blocked sender address_ In the quaratine management screen, you can still remove the filter to view the block senders (good for troubleshooting), but by default, they will be hidden, and no emails will be sent to end users when a block sender email comes in. We'd liek not only to specify hiding them from the view, but also setting the user's access to : Delete, Preview, Block Sender (NOT Allow Sender). Maybe making this a variable field in the Standards would be good, as other MSPs likely have other preferences for this. ### PowerShell commands you would normally use to achieve above request Honestly not sure about this. CIPP can deploy and update a Quarantine policy rght now, so hopefully MS as a new API endpoint for theses settings?

kerem

2026-03-02 13:43:03 +03:00

closed this issue
added the
enhancement

no-priority

no-activity
labels

kerem commented

2026-03-02 13:43:04 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 24, 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.

@github-actions[bot] commented on GitHub (Jun 24, 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.

kerem commented

2026-03-02 13:43:04 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 8, 2024):

This issue was closed because it has been stalled for 14 days with no activity.

@github-actions[bot] commented on GitHub (Jul 8, 2024): This issue was closed because it has been stalled for 14 days with no activity.

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

No description provided.

Rows
Columns