Using older versions of Outlook for Mac in business environments
MSFT please answer/fix here... we move to this Outlook version and now being severily affected. Thanks
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I just installed Outlook v15.9 as well as updates for the entire new Mac 2016 suite released yesterday. I'm getting an Outlook certificate error as can be seen in the attached screen shot. I can click Continue and run Outlook without any problems and it works fine. Also, I wasn't getting this error in the immediate prior release. All of my company's email is hosted on Office 365. How can I fix this or should I worry about it? Thx! John
Using older versions of Outlook for Mac in business environments
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.
MSFT please answer/fix here... we move to this Outlook version and now being severily affected. Thanks
Hi there,
Just found work-around: downgrade to 15.8.2
you can pull DMG from MSFT
https://support.microsoft.com/en-us/kb/3048674
Sad but only way I manage after a full day playing with certificates.
HTH
MSFT: you need to fix this ASAP
Thanks
-f
We encountered the same issue after installing version 15.13.1. The certificate error keeps coming back whenever we relaunch Outlook. Even though I followed the KB article from Microsoft below, the error still comes back.
Yep, I solved getting back to 15.8.2. Sad solution. In the meanwhile I used Mail, not bad at all, reconsidering use Outlook again till this bug get solved.
Hi. We have on site Exchange 2010, and just installed Office 2016, Outlook is upgraded to 15.14.2 but we also have this issue.
In our case, instead of using our own certificate hosted on Exchange, Outlook goes and resolves our domain and grabs the cert off our website, which is hosted by a 3rd party, instead of internally resolving to our mail.domain.com certificate.
Can't believe this issue is still on going...did Microsoft not run into this issue while testing? Maybe it's some settings that needs to be changed on Exchange or on Outlook's profile?
Looking forward to a fix for this.
Northenio.