The email quarantine process is as old as email itself, and still an essential part of any email service. As far as Office 365 is concerned, Exchange Online is a world-class product and the quarantine mechanism works well, however the current iteration of the Quarantine portal falls short in user experience and performance.
This protection mechanism, along with the associated user experience, is critical in my opinion because it affects whether one receives legitimate emails or not. Unfortunately, the Office 365 quarantine experience leaves a lot to be desired and deserves some attention from Microsoft.
The quarantine process is hosted by Exchange Online Protection (EOP), a subset of the greater Exchange Online product. EOP performs many of its usual tasks with Artificial Intelligence (AI) and as a result, admins have fewer buttons to push and dials to turn compared to other email protection products. The management interface for Exchange Online Protection may be found within the confines of the Exchange admin center in Exchange Online.
However, the Quarantine settings we need are buried within another portal. As Microsoft works to consolidate the many Office 365 portals, Exchange Online Protection will move from the Office 365 Security & Compliance portal at protection.office.com over to security.microsoft.com, which is currently branded as the Microsoft 365 security center.
I can either review these messages using the Quarantine page in the Security & Compliance Center, OR I have the option to Block Sender or Review. Note that at this stage we are still unable to release the message, even if we know the sender and are confident that this is NOT a phishing attempt.
In this instance, since I know and trust the email address and want to release the message, I click Review, noting that the URL for Review starts with My action takes me to Office 365 Security & Compliance portal. Well, it does eventually, after some animation appears, communicating that something is happening:
At best, this sequence of events lasted well over five seconds, and it was a good 30 seconds before I was able to interact with the message in quarantine. Having used several different vendors for email quarantine functionality, I can say that the time it took between clicking on Review to then arrive at this point, is not on par with other security vendors in this space. Most vendors offer a condensed view with only those emails requiring a review before being released from a performant portal or micro-site.
Now our next step is deciding what to do with the message. I must say, the view of my options is not particularly user-friendly, especially when you consider the non-technical nature of the average person using email:
Hovering over each option reveals more detail and lets the user know what will happen should they decide to click on it. Not every button shows this extra detail though, which can cause user confusion over what they should do:
Moving further down the dialog screen, we see our message and see the default option to Release messages to all recipients. As a normal user, I would change nothing here and click Release message. Next, dots will begin to move at the top of the dialog, indicating that something is happening.
The user is then presented with three options, but only able to select the third option (which would make sense as the message has already been released) but again, this could be confusing for the average user:
If we logon to the Quarantine portal in an admin role, we notice that it is identical to the user view but with the ability to see messages held for all users. The messages may be sorted according to personal preference using the Filter option:
Unfortunately, the default grid view for admins does not display the intended recipient of the held email. The Modify Columns button gives a brief glimmer of hope, but ultimately increases frustration by only offering seven modification choices such as Direction and Message ID and Policy Name. Since the grid is sortable based on columns, having more than these seven arbitrary options available while triaging reasons for the email quarantine would be incredibly useful.
More often than not, I avoid the Quarantine grid view entirely and move to PowerShell so I can efficiently execute bulk actions. The Quarantine cmdlets are available using the Exchange Online PowerShell V2 module. They support modern authentication, and feature well-documented examples:
Another option is to train users on the Microsoft 365 Security portal, which would hopefully enable the user to comb through their quarantine queue for items that appear to be missing. While a more tech-savvy user is adept enough to successfully navigate the portal experience, support staff should still expect frustration from many users.
Microsoft Exchange Online, like its on-premises predecessor Microsoft Exchange Server, tends to function pretty smoothly when built and configured according to best practices. However, some aspects of the Exchange Online user experience are less than pleasing, sometimes downright painful, and the admin experience around email quarantine definitely falls into the latter category.
Compared to all the other vendors in this crowded space, the Exchange Online Protection Quarantine experience is sub-par and disappointing. Actions are slow and often time out, especially during bulk operations. The user experience is complex and not performant at all. Administrators have powerful options but are often hamstrung by the same slow portal experiences which users suffer under.
This is an area which requires some attention and a significant investment from Microsoft, both for product performance reasons as well as obvious flaws with the user experience. Improving the user and administrator experience in the Quarantine portal, as well as streamlining the release workflow, would be changes well overdue and welcomed by all.
@nicholas : thank you for the explanation
However we are in situation, we have end user quarantine policy in place.
Sender a.com sends and email which is quarantined, user gets notification (Quarantine Digest), user clicks on Block sender( which ideally adds sender to blocked list at mailbox level ie in Junk configuration if I am not wrong)
I guess this is intentional behavior where sender is never notified but i can be really frustrating, would it be better to remove these specific extension in Defender365 policy deal with it through another policy/rule ? or should we switch to reject NDR all identified attachment, maybe this way internal users at least will get the NDR ?
I agree with the points made, but with the phishing implications of having notifications enabled, we are now recommending notifications remain disabled, and perhaps spam can go to the Junk folder, with users trained to:
With the newly released GUI, they have removed the ability to see Policy Name for a quarantined message. This makes it difficult to determine which transport policy was used to make a quarantine decision.
The arrival of new Teams audit events allows tenants to analyze data about Teams online meetings. However, the data available in the audit events is incomplete, and the only way to get a full picture is through the Graph APIs. This article explains how to find Teams Online meetings in user calendars, extract information about the meetings, and generate an HTML report.
With the rise of generative AI comes an increased risk of organizational data leakage. This article explores recommendations to secure Microsoft 365 data from unauthorized generative AI applications.
A new sensitivity label setting blocks access to content services for Office applications. In effect, this stops any feature that depends on the ability to send content to Microsoft for processing, including Copilot for Microsoft 365, DLP, text prediction, and so on. It's a precise item-level block that protects sensitive documents from being consumed and used by Copilot in the text that it generates.
Quarantine and isolation are legal, public health authorities that may be, but rarely are, implemented to prevent the spread of communicable diseases. Ill people may be isolated to protect the public by preventing exposure to infected people.
In response to the COVID-19 pandemic, states have used their authority to create quarantine or isolation requirements on certain individuals or populations to slow the spread of this disease. This includes orders for individuals returning or traveling from foreign countries, states and other areas with high rates of COVID-19 transmission to quarantine for a certain amount of time or until they are able to confirm their status through testing. It also includes quarantine orders for individuals who may have been exposed to the virus, who work in high-risk settings, individuals experiencing symptoms of COVID-19 and individuals who test positive for the virus.
The CDC's authority to exercise quarantine and isolation powers for specific diseases derives from the federal Public Health Service Act and a series of presidential executive orders. Under these orders, federal quarantine and isolation powers currently apply to the following diseases: cholera; diphtheria; infectious tuberculosis; plague; smallpox; yellow fever; viral hemorrhagic fevers; influenza caused by new or reemergent flu viruses that are causing, or have the potential to cause, a pandemic; and severe acute respiratory syndromes (which may include COVID-19).
Quarantine is not the same as a statewide stay-at-home order. Stay-at-home orders apply broadly to the entire population of a state or locality, affecting more than just those who are confirmed to have an infectious disease or who have encountered someone carrying the disease. Under a stay-at-home order, individuals are encouraged to stay home and leave their place of residence only out of necessity, for instance, to shop for groceries or receive medical care. During the COVID-19 pandemic, every state used different language and had specific requirements related to these executive order(s). The use of quarantine or isolation powers may create sensitive issues related to civil liberties. Individuals have rights to due process of law, and generally, isolation or quarantine must be carried out in the least restrictive setting necessary to maintain public health.
b1e95dc632