Tag Archives: HCW

Exchange Online Centralized Transport and Mail Loop Issue.

I had to integrate Exchange Online with an on-premise DLP system for one of my customers. The goal was that all messages delivered to the Internet must go through a deployed on-premise DLP server.

By default, even if a classical hybrid is deployed, all messages sent to the Internet by cloud mailboxes are delivered by Exchange Online directly to the recipient server. To achieve my goal, I had to override the standard logic.

The logic had to be:

  1. A user with a mailbox in the Exchange Online organization sends a message to an external Internet recipient.
  2. Exchange Online is configured to send all Internet-bound messages to an on-premises server, so the message is routed to an on-premises Exchange server.
  3. The on-premises Exchange server sends the message to the internal DLP system.
  4. The internal DLP system checks and forwards all the messages to an internal mail gateway.
  5. The internal mail gateway looks up the MX record for the recipient domain and sends the message to the recipient’s mail servers on the Internet.

The centralized mail transport option can help with this; this option can be enabled during HCW setup.

With centralized mail transport, you can route all mail from mailboxes in the Exchange Online organization through the on-premises organization before they’re delivered to the Internet.

Continue reading

Exchange Hybrid Configuration Wizard Certificate Issues

Setting up a hybrid environment for Exchange can sometimes be a tricky process, especially when dealing with certificates. Recently, I encountered a problem during the Exchange Hybrid Configuration Wizard setup where the certificate from a public certificate authority (CA) was not available for selection. Here’s a detailed account of how I diagnosed and resolved the issue.

While running the Hybrid Configuration Wizard, I noticed that the online certificate I needed wasn’t available for selection, despite having signed certificates displayed. A quick search suggested that the commercial certificate might be incorrectly installed.

This led me to check the certificate using PowerShell and specifically focus on the RootCAType property.

The RootCAType property is crucial in identifying the kind of CA that issued the certificate:

  • ThirdParty: Indicates a commercial, public root CA.
  • Registry: An internal, private PKI root CA manually installed.
  • None: No CA information.
Continue reading