You should see the certificate in the Server Certificates list. The next step is to ensure the SMTP Server is correctly configured to use the certificate. Open IIS Manager 6.0 (Start->Administrative Tools->Internet Information Services (IIS) 6.0 Manager). In the left window, expand the server name. Find your Direct Gateway SMTP server, right-click it and select Select the tab. Properties. Access In the Communication” section you should see the text TLS certificate is found with “Secure “A Refer to Figure 22. expiration date: “… Figure 22: TLS certificate is available. If you see the text, the TLS certificate is correctly installed, and clients can initiate TLS channels with the Direct Gateway. When Exchange Online relays messages to the Direct Gateway it will use a secure TLS connection since we instructed it earlier to validate against a self-signed certificate. Note: If you don’t see the text above, the TLS certificate can’t be found by the SMTP Server. Ensure the property of the certificate you created earlier matches the “CN=” Fully Qualified Domain Name (FQDN) of your Direct Gateway. The FQDN of the Direct Gateway can be retrieved by clicking on the tab shown at the top of Figure “Delivery” 22, and then clicking Advanced… Testing your new Direct-enabled Exchange Online instance At this point everything is configured and we can verify the new Exchange Online instance is working with the Direct gateway. Here are some steps to perform to validate your configuration: Validate incoming messages to Exchange Online Send a Direct message TO the Office 365 user you created earlier. Log-in as the user to Office 365 and navigate to the Outlook inbox to see the message. Of course, trust will need to be established between the sender’s Direct instance and your new instance in order to receive the message. Information on configuring anchor certificates to establish trust is beyond the scope of this document; details can be found at the links in the about Direct” section. “Learning Repeat the above, but try sending the message from an address for which trust does not exist with your new Exchange-enabled Direct instance. The message should be rejected by the Gateway. You can verify this through the Direct Gateway logs.
You should see the certificate in the Server Certificates list. The next step is to ensure the SMTP Server is correctly configured to use the certificate. Open IIS Manager 6.0 (Start->Administrative Tools->Internet Information Services (IIS) 6.0 Manager). In the left window, expand the server name. Find your Direct Gateway SMTP server, right-click it and select Properties. Select the Access tab. In the “Secure Communication” section you should see the text “A TLS certificate is found with expiration date: “… Refer to Figure 22. Figure 22: TLS certificate is available. If you see the text, the TLS certificate is correctly installed, and clients can initiate TLS channels with the Direct Gateway. When Exchange Online relays messages to the Direct Gateway it will use a secure TLS connection since we instructed it earlier to validate against a self-signed certificate. Note: If you don’t see the text above, the TLS certificate can’t be found by the SMTP Server. Ensure the “CN=” property of the certificate you created earlier matches the Fully Qualified Domain Name (FQDN) of your Direct Gateway. The FQDN of the Direct Gateway can be retrieved by clicking on the “Delivery” tab shown at the top of Figure 22, and then clicking Advanced… Testing your new Direct-enabled Exchange Online instance At this point everything is configured and we can verify the new Exchange Online instance is working with the Direct gateway. Here are some steps to perform to validate your configuration: Validate incoming messages to Exchange Online Send a Direct message TO the Office 365 user you created earlier. Log-in as the user to Office 365 and navigate to the Outlook inbox to see the message. Of course, trust will need to be established between the sender’s Direct instance and your new instance in order to receive the message. Information on configuring anchor certificates to establish trust is beyond the scope of this document; details can be found at the links in the “Learning about Direct” section. Repeat the above, but try sending the message from an address for which trust does not exist with your new Exchange-enabled Direct instance. The message should be rejected by the Gateway. You can verify this through the Direct Gateway logs.
1680.Office365%20and%20Direct%20HOWTO.docx