Forum Discussion
Hybrid deployment in Office 365 | Checklist and pre requirements
What a great article!
I have an Exchange Server 2010 on premise server setup in Hybrid Mode.
This server also has OWA configured and I remember needing to do this as I wanted to migrate my Public Folders over to Exchange Online.
This I have now done so all mailboxes and Public Folders are over in Office 365.
Do I need to maintain the presence of the OWA locally still?
Dear Chris,
Thanks for liking my article and for getting an expert opinion for your Exchange Hybrid from me, as you are using exchange 2010 which is not supporting silent OWA redirection (2013 and 2016) supported and if no mailbox is on-premise you do not need to change the actual OWA URL name but redirect the URL from old to Office 365 deleting the old DNS A record and adding a new CNAME entry e.g if you on premise OWA name is mail.contoso.com then you can add a new CNAME record as Host Name "mail.contoso.com" and point to address is "outlook.office.com" so every time when your users try to access the old OWA they will be redirected to new URL.
Hope this will help you
- Chris-YueApr 30, 2018Iron Contributor
Hi Ahmed,
Thanks for the advice.
So I understand this, can I remove the OWA role from my on premise Exchange 2010 server?
Just wanted to make sure that there was no impact on the Hybrid functionality.
Users are going straight to office.com for their email needs, web wise.
- Ahmed BilalApr 30, 2018Copper Contributor
you can remove the CAS role and also need to change the Autodiscover entry to Office 365 because your exchange front-end (CAS) on premise look for user's mailbox using autodiscover service using CAS Role and if there is no mailbox change the autodiscover DNS entry and remove the CAS role so your client will use Office 365 CAS for mailbox discovery process.
Hope you understand the whole process