Following Friday morning we have not had any further occurrences with any of our clients. No issue today either.
I don't think this can be classified as anything to do with Bitdefender as we dont' use that product anywhere in our own stack but were experiencing the same issue.
@B_Toronto your support experience sounds exhausting. Hope you brought your patience! So frustrating that you gotten taken down a rabbit hole with MX records etc. This is very clearly a certificate revocation issue related to an MS cert. If there was a name mismatch I could see going down the path of a configuration issue. I really have to wonder if there is a certificate somewhere in the certificate chain of trust that was revoked, even temporarily or that some UTM products didn't like during SSL inspection and flagged as not trusted. I'm not 100% ready to blame MS on this one as I think Digicert, some root certificate, or even UTM products performing SSL inspection could be the cause.
Glad it isn't an issue today for us, but I don't like unsolved mysteries.
Chris