Forum Discussion
Hybrid deployment in Office 365 | Checklist and pre requirements
Dear Avisek,
if you want Hybrid then your Anywhere, EWS and Autodiscover URL's should be available publicly and published in your exchange servers because autodiscover service will do the autodicsovery of mailboxes either user's mailbox in the cloud or on-premises and EWS will give you the advantage of organization relationships with exchange online organization for unified GAL, calendar and free/busy information sharing and if your exchange do not have EWS Public names published on your exchaneg then your Hybrid Wizard will be failed saying :Organization relationships failed......." because it need to make a trust relationship with your exchange and MFG (Microsoft ForeFront Gateway) for free/busy and calendar sharing.
if your OWA not published it will not gives your users access to Exchange online URL access as a scilent redirection but each users need to open Exchange online URL i.s. https://mail.office365.com and for every user migrated to cloud you need to tell that now your mailbox is in the cloud and you need to use https://mail.office365.com as OWA address and this will not be seamless transaction for your users.
i hope this answer your queries and do let me know if you need further help from my end.
I know if I will use different OWA external URL i need to communicate with the user.What happen i will keep my autodiscover record with same name ?
So next question is what FQDN connector i will use while running hybrid wizard ?can it be same URL like OWA external ?
now do i need to put the third party cert in the exchange server or load balancer(f5)publishing will suffice the purpose.So what certificate will choose while
running the HYbrid wizard if i will not put in my ex server.
Dear Avishek,
Sorry for the late reply because we have public holidays here in Qatar and regarding your question on the external name please have a look at part#2 where you can see how to find your exchange public names FQDN:
2. Exchange On-Premise Hybrid Server | Public IP Address And Public Name (FQDN)
for Autodiscover have a look on the part below under the article.
Simple Exchange on-Premises environment versus complicated environment.
you can use external name as different with the one you are using for internal.
- That"s not an issue,Thanks for your reply.
So the point is I need to use external name different from the internal name.
And if my owa external name is mail.domainname.com\owa so i can use mail.domainname.com as my Hybrid Fqdn in wizard & this names needs to be present in third party certificate.
So Primary job is to be published all the external url for exchange services including autodiscover then we can run hybrid with mail.domainname.com- Yes, you are right