The following is a code example from send connector logs. In the send connector log, you can check for the thumbprint of the certificate that is given to Exchange Online. (Here we assume that the send connector name that's used for relaying to external domains through EOP is "outbound to Microsoft 365.")įor Exchange 2010 (Get-SendConnector "outbound to Microsoft 365").SourceTransportServers | foreach | Select-Object name,SendProtocolLogPath To find the location of the send connector logs, run the following cmdlet against the source servers that are listed in that send connector. Confirm the issue by enabling logging on the send connector that is used for routing mail to Microsoft 365 and checking those logs. If the new certificate isn't sent from on-premises Exchange to EOP, there may be a certificate configuration issue on-premises. Make sure that the new certificate is sent from on-premises Exchange to Exchange Online Protection (EOP) when users send external mail. Option 2: Change the inbound connector without running HCW Changes may take some time to take effect. ![]() When the Wizard has successfully completed, the value for the TLSSenderCertificate name should match the certificate that's used by the on-premises server.
0 Comments
Leave a Reply. |