Encountering an error message in Engagement Messenger when launched on a customer's website

Underlying Root cause

There are multiple reasons for this error:

• The server adds an HTTP header in the response that says the website content cannot be launched in an iframe within another website.
• The response contains some HTTP header parameters that violate some security policy
• network issues and probably many more that are beyond the scope of this little article for engagement messenger

The error for me was caused by security policy violation #2. Looking at the error messages in the JS console confirmed it.

Chrome Dev Tools Error Message is

"Refused to frame 'https://xxxxxxxxx.service-now.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self' frame-ancestors teams.microsoft.com *.teams.microsoft.com"."

EM HTTP Response Header's default setting for Content-Security-Policy matched the error message.