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
@Varol
Moving the existing namespace from 2010 to 2013 can certainly have an impact, which is why you needs to first determine which version of Exchange you should be running the HCW from. If the users are on Exchange 2010 then maybe 2010 is the right version to use
so, why even bring in Exchange 2013. If you however require an 2013 specific feature it will be less disruptive and more predictable to deploy Exchange the way it was designed to work. If you deploy Exchange in a way that we do not validate you run the risk
of things not working unexpectedly. This has happened in the past and it could certainly happen in the future.
Again if you look at one of the points of the article, there is no such thing as a Hybrid Server, just Exchange servers. There are proper ways to deploy Exchange so coexistence works in the most predictable way, that is the point we are trying to get across.