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
As we don't have any online mailboxes and are not intending to have any in the near future, can we still run the hybrid wizard (ews is internet accessible) and make sure we enable Centralised Mail Transport?
Would this be enough to provide Teams on-premise calendar access (the real goal at this stage) and then we can worry about mail flow later?
Would this be enough to provide Teams on-premise calendar access (the real goal at this stage) and then we can worry about mail flow later?
- No...centralised mail flow is not related to Teams free/busy or calendar access. The problem is that Teams requires direct access to EWS to see a users calendar, and the hybrid agent can't (currently) provide that, so you need a full hybrid which publishes this to the internet so Teams can access the Exchange server directly and get the calendar information.
Thanks for the repliesDan_Snape
If we don't have any EXO mailboxes, can we still set up classic full hybrid without the direct smtp connection, or will the wizard complain that it isn't there and not continue? EWS will be accessible.
On our primary IP address we already have port 25 open for mail flow to/from our mailscanner appliance which sits in front of Exchange on-prem. We would need another IP to permit stmp traffic to/from EXO. We would sort this out when we decide to start setting up EXO mailboxes.
- 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