Many Office 365 customers are using our hybrid deployment option since it offers the most flexible migration process, the best coexistence story, and the most seamless onboarding user experience. H...
Updated Jul 01, 2019
Version 2.0
Blog Post
Tim,
Appreciate the quick response and for working to get the EDA updated. I wanted to follow up on #3 and #4 - hopefully others are benefiting from this discussion as well :)
"3. Deploying Exchange in the proper way, meaning following our guidance to deploy Exchange 2013 into an existing 2010 environment will be much less impactful than attempting to work around the designed coexistence logic we have in product"
Could you please elaborate further? In my mind, this seems more impactful as we must move the existing namespace to 2013, meaning the modification of existing DNS records and firewall rules.. and in the case of existing 2007, the creation of a new legacy namespace.
After the change, users will see a new OWA login page, which may be a concern if end user communications have not been sent out. With a separate hybrid namespace, nothing changes from an existing DNS/firewall/end user perspective except we repoint Autodiscover
at 2013. When a user is moved to EXO, Autodiscover reconfigures Outlook and they use a new URL for OWA.
"4. In addition, there are many customers that will end up keeping a good portion of users on-premises, in that case they may want to move some of the users to Exchange 2013 on-premises. If you deployed correctly from the beginning there is no extra changes
that would need to take place... you just move mailboxes"
Agreed this may be true of larger enterprises, although it's not something we run into too often.. for these customers, it'd be important to point out the licensing requirements during planning, as I believe the free hybrid license terms of use do not allow
for the migration of production mailboxes onto the hybrid servers.
Thanks again.