Farewell Email Warning | Annoying Warning “The Email Below Might Contain Script or Content that is Potentially Harmful and Has Been Blocked.”

Jensk

7 years ago

Let's explore

Farewell Email Warning | Annoying Warning

Not one week go by where I do not get a question from a Dynamics 365 Customer engagement user or admin on how to get rid of the warning on Emails in Dynamics that contains HTML components, such as <script> or <style>. Good news is that it now can be gone with a simple setting. (step by step guide included in this post)

The Annoying warning started way back when in Dynamics CRM 4, where it was just a small yellow line that most users just ignored.

But since Dynamics CRM 2011 the Warning just got more visible in”What’s new” list and lately, in newest Dynamics V9, it got an even more prominent appearance for some strange reason.

Until now only way to get rid of it was to include unsupported script code that usually was not upgrade friendly… but this all changed some point in time this year as Microsoft snug a Feature flag into OrgDbOrgSettings for Admin to toggle this warning on and off.

Before and after setting feature flag “SecuritySettingforEmail” in OrgDbOrgSettings

Email Warning Be Gone in 3 easy steps

To edit the organization database settings aka OrgDbOrgSettings you have at least 2 choices, one is to run a command line script that could be included in your deployment the other is to use this point and click solution from within Dynamics/PowerApps Admin interface create by Sean McNellis.

To Prove it worked, I used Sean McNellis’s tool with below steps:

Download and install the solution
- You can get the latest version under this link: https://github.com/seanmcne/OrgDbOrgSettings/releases
Open the solution and locate the “SecuritySettingforEmail” entry
- Open the Solution and activate the tracking through pressing of the “Add” button.
Change the “SecuritySettingforEmail” value from 1 to 3

See here how i did it:

For the Change Management people

Please notice that this fix also gets rid of the “View full Email” link so please direct users to use the More Commands (…) >> Open Entity Record option instead.