Traditionally, restricting where and from which device users could access their Mailbox in Office 365 required substantial configuration within Active Directory Federation Services (ADFS), or more recently, relied heavily on registration of compatible devices within Intune.
The functionality in Exchange Hybrid is now quite mature. It’s been available since the launch of Office 365 (or even before if you include the embryotic support in Live@EDU) and provides the rich co-existence functionality that allows organizations to mix mailboxes on-premises and in the cloud, retaining much of the normal sharing capabilities people rely on for day-to-day collaboration.
Exchange Server 2016 has arrived and has been lauded as one of the most reliable releases of Exchange yet. In many ways, it’s an evolution of the core technologies built into Exchange Server 2010 – but the way it’s put together has been revolutionized, making deployment choices much more straightforward.
What’s new compared to Exchange 2010?
Exchange Server 2010 has been extremely popular and, for many, was the upgrade point from Exchange 2003. It revolutionized availability with Database Availability Groups and made it possible and practical to deploy site resilient Exchange with relative ease. Six years have passed since its original release, though, and in that time, Microsoft has learned a lot from running the world’s largest Exchange deployment inside Office 365.
Much is new under the hood, including a rearchitected Store engine and better automated availability checks, but some of the most interesting deployments include:
- A beautiful new Outlook Web App – renamed “Outlook on the web” providing near parity with the Outlook client, offline access and fantastic cross platform support, even on mobile devices.
A healthy Exchange Hybrid environment is vital for any organization looking for a stable and rapid migration and essential for those organizations expecting to stay in Hybrid mode for more than a very short period.