Forum Discussion
Outlook - Certificate has been revoked
Here is the error message (Office 365):
Amir Jafarian that looks like either a problem communicating with the CRL or there might be another issue with your system or an intermediate network device (like a proxy). Since you are connecting to Exchange Online you can raise a support ticket with Microsoft for troubleshooting assistance. You can also try running diagnostics with the SARA tool (https://diagnostics.outlook.com).
Other posters are complaining of certificate popups for on-premises Exchange server environments, which could be an entirely different problem with their server or certificate configuration.
- Edgar GuerreroAug 21, 2017Copper Contributor
any news with this
- Jane EthariaSep 27, 2017Copper Contributor
Anyone found a solution for this issue. Microsoft support is of no help.
- HapSep 29, 2017Copper Contributor
Unfortunately not. MS was able to reproduce against our environment once, but hasn't occurred since. I haven't had the revoked popup since a month, so it might be that is has been resolved in an update. Are you still getting it with Outlook 2016 updated to the latest version?
- James ChapmanMay 24, 2017Copper Contributor
Hi,
We're experiencing the same issue as @Amir Jafarian
Fully patched msi version of Outlook 2016. Connecting to Exchange online. Sporadic Digicert certificate warnings across the org. Seems to happen most commonly when waking a device from sleep. I'd agree it looks like issues checking the CRL but can't find the cause.
We've got tickets open with Microsoft and our proxy vendor but not getting anywhere fast. We've had our proxy solution in place for some time without issue and nothing has changed.
I'll post if we find anything.
- HapJun 07, 2017Copper ContributorJust a quick note. We have the same issues, but no proxy in between. Doubt it is related to your (forward) proxy, or did you mean reverse?
- Paul CunninghamMay 26, 2017Steel Contributor
James Chapman wrote:can't find the cause.
our proxy solution
I'm not a betting man, but...