Emails generated by platform render differently in Outlook for Windows than Outlook for Mac or Web BrowsersIssue Customers may notice that emails generated by the platform may not render as expected when using the Microsoft Outlook client for Windows. Here is an example of what this email may look like. Notice the 'Take me to the Incident' button in the below image is not completely shaded in blue here when the email is viewed in the Windows client. In Outlook for Mac or any browser, the button displays normally. CauseAfter testing email rendering across several browsers and Outlook clients in both macOS and Windows, there seems to be an issue with the way the Windows Microsoft Outlook client interprets HTML in emails. When opening the sample e-\mail in Windows, notice the message: "If there are problems with how this message is displayed, click here to view it in a web browser." When opening the email in a browser like Internet Explorer or Chrome, it displays the 'Take me to the Incident' button normally. The reason why this behavior occurs in the Windows Outlook client is that it relies on Microsoft Word for rendering HTML in email, and Microsoft Word is not compliant as a web browser for rendering HTML. Here are some links that explain this in more detail: Outlook 2016 rendering problems Rendering, CSS Support & More in Office 365’s Outlook Web AppResolutionAs this issue is specific to the Windows client for Microsoft Outlook, there are no fixes from the ServiceNow perspective to address this at this time. With that said: For example, here is the email script responsible for rendering the 'Take me to the Incident' button:https://<instance_name>.service-now.com/nav_to.do?uri=sys_script_email.do?sys_id=f25bc270d711120035ae23c7ce610323The incident_take_me_to_the_incident Email Script is an out-of-the-box script, but a customer may change it to make it work with their Windows Outlook client. Alternatively, re-direct the customer to contact Microsoft Support to see why they are not handling the current HTML used in the script in a standard web-compliant manner. Please keep in mind that custom implementation of code is outside of the scope of support, and the customized record will be skipped by future upgrades if that future upgrade intended to change the record.