Using Classic Outlook on Windows for personal email, calendar, and contact management
Thank you Gabe!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hyper links wont open and I get the error message.
Using Classic Outlook on Windows for personal email, calendar, and contact management
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Thank you Gabe!
Hi all,
I know this is a very late reply, but I wanted to make sure you saw that we posted a Known Issue article, Outlook blocks opening FQDN and IP address hyperlinks after installing protections for Microsoft Outlook Security Feature Bypass Vulnerability released July 11, 2023 - Microsoft Support.
The Security Update CVE articles (in the link above) are also updated with a FAQ item explaining the changes further and that these are expected. These changes should have been communicated with the security updates. I apologize for the disruption.
This issue is also being published in the M365 Service Health Dashboard as EX649739.
Hi Gabrielle,
That is great news. Any idea on a timeline for a fix? I really don't want to poke holes in our internal security if I can avoid it.
Hi Alex,
It would seem there will not be any "fix" the workarounds are the resolutions to be used with caution on verified trusted domains, IP Paths, URL's etc.
Hi,
The problem with applying this "workaround" with GPO is that if we try to do it we take Administrative control of Trusted Sites or Sites in Local Intranet. This approach is removing any custom assigned by user sites.
This is very timeconsuming workaround as administrator should go computer by computer and document current sites.
It will be better Microsoft to provide real fix.
BR,
Ivan Cholakov
We have the same issue. Removing the affected update and turning off the warning message via the registry aren't decent solutions regarding to security. Therefore, Microsoft MUST provide us with a fix/workaround without negleting the security.
I tried to add various patterns to the zone "Trusted Sites", but without success:
And still the warning message when trying to open an affected URL that consists of an UNC path: