This is a client-side functionality, not Exchange one. The previous reply is usually included only for the sake of convenience. As you are effectively composing a new message, there is no way to prevent you from modifying any text therein, including old replies. Plus, many people prefer to answer "inline", i.e. add their replies in between paragraphs of the existing message, which is again a modification of the original text. In any case, you can always open a request for this over at the Feedback portal: https://feedbackportal.microsoft.com/feedback/forum/89a8afa3-2e1c-ec11-b6e7-0022481f8472
Trailing mail should be tampered proof.
I have an observation, while replying to any mail thread trailing mail contents can be altered. My suggestion is that Microsoft Mailing solution should have a capability that trailing mails cannot be altered and it should be tampered proof or trailing mail should be grayed out. This can be one of the way to avoid tampering.
Exchange Online
Exchange | Exchange Server | Other
Exchange | Exchange Server | Management
2 answers
Sort by: Most helpful
-
Vasil Michev 119.5K Reputation points MVP Volunteer Moderator
2023-04-25T18:52:32.36+00:00 -
Yuki Sun-MSFT 41,376 Reputation points Moderator
2023-04-26T05:23:08.49+00:00 Hi @M Gazanfar Wanchoo ,
As far as I know, this is currently not feasible from either the perspective of Exchange or Outlook client side.
With this being said, a possible workaround is that you can force users to attach the original email when replying or forwarding via Group Policy, so that when a user clicks Reply/Reply All or Forward, the original email would be attached automatically and thus cannot be alerted:
However, this only works when users handling emails with Outlook clients inside the domain, so it's not a perfect solution for your request.
Then I did further research and it appears to me that it might be possible to be realized by the ADRMS template for on-premises:
Restrict edit email body when forwarding or replyin to emails
If you have interest digging deeper on this, you can probably starting a new thread with the "Azure Information Protection" tag so that experts there can help look into it as well.
In addition, agree with Vasil that in any cases, the suggestions can be submitted to the dedicated feedback portal. I've helped reposting there and will leave the link below in case you or others would like to vote it up or comment over there as well:
https://feedbackportal.microsoft.com/feedback/idea/a9596957-f2e3-ed11-a81c-6045bd78706c
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.