Blog Post

Exchange Team Blog
2 MIN READ

Reply All Storm Protection in Exchange Online

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
May 07, 2020

Update 5/5/2021: For additional information on this subject and new settings, please see this post.

When a reply all mail storm happens in your organization, it can disrupt business continuity and in some cases even throttle the rest of your organization’s email for a period of time. At Microsoft Ignite 2019 we announced the Reply All Storm Protection feature to help reduce the impact that reply all storms can have on large organizations. This feature has completed our rollout, and is now available to all Office 365 tenants worldwide (except GCC-High… it’s coming).

Initially the Reply All Storm Protection feature will mostly benefit large organizations who have large distribution lists. When the feature detects a likely reply all storm taking place on a large DL it will block subsequent attempts to reply all to the thread and will return an NDR to the sender. The reply all block will remain in place for several hours.

Initially the Reply All Storm Protection feature will use the following conditions to detect a reply all storm:

  • 10 reply all-s to over 5000 recipients within 60 minutes

It will then block subsequent replies to the thread for 4 hours.

The reply all storm NDR will look something like this:

 

Over time, as we gather usage telemetry and customer feedback, we expect to tweak, fine-tune, and enhance the Reply All Storm Protection feature to make it even more valuable to a broader range of Office 365 customers.

We’d love to hear your feedback on this feature. We are considering possible future enhancements to improve our reply all storm detection accuracy, add admin customizable thresholds and block duration, as well as producing reply all storm reports and notifications.

We’re already seeing the first version of the feature successfully reduce the impact of reply all storms within Microsoft (humans still behave like humans no matter which company they work for 😉 and believe it will also benefit many other organizations as well.

The Exchange Transport Team

Updated May 05, 2021
Version 3.0

37 Comments

  • HaydonG's avatar
    HaydonG
    Copper Contributor

    This is a great new feature addition and would personally want to drop the reply all limits lower [BEDLAM DL3!], but there is a need on occasion to allow an additional mail in the thread from a 'trusted party', so it would be nice if the Manager of a DL was not blocked by this - so that they can at least do a mail back in the thread to educate or update the members in relation to the content / issue.


  • Sankarasubramanian Parameswaran it's enabled for all tenants. There's nothing to configure. 

     

    You don't need to 'test' or set up rules for it. You'll have to trust us on this, it is enabled, and it works when the threshold is met. If you want to kick off a mail storm in your tenant to prove it, make sure your resume is up to date. 

  • Ed Woodrick's avatar
    Ed Woodrick
    Brass Contributor

    Awesome addition folks!!!

     

    A few things to think about moving forward

    • Ability to adjust the limit (lower it in many cases)
    • Ability to disable for some specific DLs, or at least if a single app sends the messages (and keeps the same subject)
    • Admin ability to invoke it on emergency demand, when it hasn't hit the preset numbers
    • Tool-Tip for when it feels like a storm.

    Again, great job!

  • Thanks. I'll ask here as everyone wants to know anyway, but is the rule for 10 when over 5000 in the hour configurable or is this tuning something you look after in the service?