Forum Discussion
Hybrid query with Exchange 2019
Hey all, We have 2x Exchange 2019 CU13 in a DAG. We are looking at going hybrid (full) but won't be migrating any mailboxes in the near future. Two things: We use Teams, and I read that Mod...
- HCW will throw an error saying the connector from EXO to on-prem couldn't be validated, but will still complete. You can use a separate namespace for the hybrid mail flow (ie hybrid.contoso.com), but that name will also need to be in the certificate on the Exchange server
Question 1: Yes it remains the same...if you want Teams free/busy, Microsoft advise not to use the modern hybrid agents
Question 2: Yes you would need a direct SMTP route from EXO to your on-prem Exchange server. When you run the hybrid configuration wizard and your MX record still points on prem, the hybrid connector created in EXO is only configured for messages between your EXO mailboxes (which you may have none initially) and your on-prem mailboxes. The reason for this is that messages sent from an EXO mailbox to an on-prem mailbox is considered "internal" and you don't want this mail going via a 3rd party message hygiene service/appliance.
Question 2: Yes you would need a direct SMTP route from EXO to your on-prem Exchange server. When you run the hybrid configuration wizard and your MX record still points on prem, the hybrid connector created in EXO is only configured for messages between your EXO mailboxes (which you may have none initially) and your on-prem mailboxes. The reason for this is that messages sent from an EXO mailbox to an on-prem mailbox is considered "internal" and you don't want this mail going via a 3rd party message hygiene service/appliance.