Just recently I was speaking to a Microsoft Premier Field Engineer (PFE) who had just returned home from a rather arduous onsite dispatch. While onsite he was tasked with unwinding a phenomenon c...
Updated Aug 28, 2026
Version 3.0
Blog Post
9 MIN READ
Removing Reply All Functionality for Outlook Users in Reply-All Storms, via Group Policy
Roady, thanks for taking the time to read the article and provide some feedback.
I wanted to take some time to respond directly to some of the points you have raised here.
First and foremost, I’m not specifically saying that this approach should be used carte blanche in each and every enviornment that is being tasked with such a problem. It is up to the discretion of the company, management, and administrators. The point here is really to show one aspect or approach to potentially dealing with such a problem. Chances are the approach will be multi-faceted (technical, user education, etc.).
I fully agree that there is no decision tree (e.g. its enabled here, not enabled here) when removing “Reply All”. It is all or nothing. Thus, I completely agree this could potentially limit a user’s ability to efficiently perform some aspects of their job responsibilities. Again a decision to implement or not implement is best left up to the company/management chain.
While I do agree that the user may still have the ability to “Resend the Message” to the complete contents of the DL or other large lists that may still reside within Sent Items, I think that each additional instance of the behavior would need to be looked at individually if it constitutes a problem. If he/she was doing it in a malicious way (e.g. to cause more intentional mail flooding), I would probably disable his/her mailbox until that user situation could be dealt with appropriately.
Lastly, as far as adding large DLs to the BCC line, I share the sentiment that it is a best practice. However, that really boils down to user education. The good users do it, “sometimes” the bad ones don’t. A company, could for example, make that type of best practice training mandatory for having a user’s Reply All ability restored...or perhaps it would just be part of Company 101 training. It really boils down to the policies in place at a company and each one is going to be a bit different.
My 2 cents.
E.
I wanted to take some time to respond directly to some of the points you have raised here.
First and foremost, I’m not specifically saying that this approach should be used carte blanche in each and every enviornment that is being tasked with such a problem. It is up to the discretion of the company, management, and administrators. The point here is really to show one aspect or approach to potentially dealing with such a problem. Chances are the approach will be multi-faceted (technical, user education, etc.).
I fully agree that there is no decision tree (e.g. its enabled here, not enabled here) when removing “Reply All”. It is all or nothing. Thus, I completely agree this could potentially limit a user’s ability to efficiently perform some aspects of their job responsibilities. Again a decision to implement or not implement is best left up to the company/management chain.
While I do agree that the user may still have the ability to “Resend the Message” to the complete contents of the DL or other large lists that may still reside within Sent Items, I think that each additional instance of the behavior would need to be looked at individually if it constitutes a problem. If he/she was doing it in a malicious way (e.g. to cause more intentional mail flooding), I would probably disable his/her mailbox until that user situation could be dealt with appropriately.
Lastly, as far as adding large DLs to the BCC line, I share the sentiment that it is a best practice. However, that really boils down to user education. The good users do it, “sometimes” the bad ones don’t. A company, could for example, make that type of best practice training mandatory for having a user’s Reply All ability restored...or perhaps it would just be part of Company 101 training. It really boils down to the policies in place at a company and each one is going to be a bit different.
My 2 cents.
E.