Bookmark and Share
Welcome to TechNet Blogs Sign in | Join | Help

Microsoft Online Services Team Blog

Technical discussions on the Microsoft Online Services and the various aspects of each of these services.
Verify Microsoft Online Services Transport Layer Security (TLS) E-mail Delivery
To secure e-mail message delivery between your on-premise and Online environments first, follow the steps on how to configure your on-premise messaging environment.
 
Next, determine whether Transport Layer Security (TLS) was used during Message Delivery. Assumption: Your on-premise SMTP Connector has been configured to request a TLS Session.
  1. Send a test message from your on-premise environment to a Microsoft Online Services mailbox.
  2. Log in to your Microsoft Online Services mailbox by opening Office Outlook.
  3. Open the test message that you sent from from your on-premise sender, and then click the small down-arrow in the options section:

    Outlook Message Header Option
  4. Review the Header information for TLS, which indicates that the message was delivered using TLS:        

        Outlook TLS Message Header

Note:  Perform this test in the opposite direction to make sure TLS is being used in both directions

Exchange Hosted Services (EHS) front-ends all Microsoft Online Mail and uses Deterministic TLS when sending/receiving messages, which means that it will attempt to send/receive mail via TLS (issuing EHLO statements to understand the message servers capabilities). 

 

On-Premise à TLS à EHS à TLS à Microsoft Online Services

Microsoft Online Services à TLS à EHS à TLS à On-Premise

 

Note:  IF TLS is not available anywhere along this path, delivery will fallback to SMTP port 25 and deliver in clear-text.

 

If a customer requires full TLS Messaging Transport capabilities, they will need a TRUSTED certificate (a certificate that can be verified and is trusted – Verisign, GoDaddy, etc.) on their On-Premise Exchange Bridgehead Server, so when MS Online/EHS delivers mail, it can properly negotiate the TLS session.  ALSO, the On-Premise Exchange Admin must configure their SMTP Connector to use Outbound Security – TLS, in order to request a TLS session for any Address Namespaces (i.e. contoso1.microsoftonline.com) defined for that Connector.

Posted: Thursday, October 23, 2008 11:29 AM by Ryan J. Phillips

Comments

joshmaher said:

This is great that TLS will be supported.

I am curious though, why won't the MTLS features take effect if a customer has Exchange 2007 on-site?

Also for those customer's who want to have private certificates, is there anything on the roadmap to allow private certs between the on-site email system and Exchange Online?

# November 5, 2008 12:19 AM

Ryan J. Phillips said:

Hi Josh, EHS does not require a client (sending server) certificate, so we wouldn't do MTLS.  EHS provides it's certificate, which is a commonly used certificate, which is trusted by ALL Windows machines.  As a result, the sending server is able to successfully able to establish a TLS connection and deliver the message.

When EHS attempts to deliver a message to an On-Premise Messaging server (Coexistence), it will attempt a TLS connection and if enabled on the receiving server AND is using a certificate that can be validated (Not expired, on a CRL and the Common Name matches), then EHS will deliver using TLS.

So that end, private certificates cannot be used when receiving mail from an EHS endpoint over TLS.

I hope this helps

....Ryan

# November 24, 2008 3:50 PM
Leave a Comment

(required) 

(required) 

(optional)

(required) 

  
Enter Code Here: Required

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Page view tracker