This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
This issue is still not fixed. To anyone at Microsoft, if you are looking at this thread, please reply to the thread with an update at least so we all know that you got the bug report. Thx!
I'm having the same problem. We're using self-hosted Exchange, not Office 365. The certificate that appears is the SSL certificate for the company that hosts the web site for my root domain. It is not a certificate for my Exchange servers.
When I do a Wireshark packet capture, I can see that Outlook is attempting to contact the root domain (example.com). This happens on every launch, even though I've manually configured the account to connect to my exchange servers (outlook.example.com). When I click CANCEL on the SSL trust screen, it establishes TLS to the correct server.
Note that we have our autodiscover.example.com domain setup correctly and Windows clients are working properly. The Wireshark capture does not show an attempt to lookup autodiscover, it only shows a query to the root domain.
In reply to the community moderator advising people to "Always Trust", this is horrible advice. In my case, I would assume that once the SSL connection is successfully established, Outlook would potentially transmit my credentials. In my case, since I don't trust the people who host my company's public web server with my credentials, this would be very bad.
Thx Jim for the helpful tip! I just did this and added the URL for this thread.
Hi John,
This is a peer-to-peer forum, so it's just us customers in here.
To let Microsoft know, use the Smile button in the upper right corner of the Outlook window. Those submissions go directly to the product team.
I'm seeing the same thing. Does no one from the Mac Preview team monitor these forums? Five days and no response or acknowledgement of the issue?
Agree! Plus there have been 12 other replies from folks seeing the same problem with this new release. Only peep so far is a Microsoft moderator telling me in another Outlook forum I had posted in the wrong place and to come over here.
Microsoft, can we at least get a ping that you got this? Thx!