Editor's Note: Originally posted by Paul Cunningham (Microsoft MVP) on his blog, Practical365, this review is extremely comprehensive and discusses the many ways Mailscape 365 can be used in Office 365 cloud and hybrid environments.
The Confusing Case of Cross-Forest Delegation
If you've even participated in an Exchange Online migration at almost any level, it's likely you've run into the issue of cross-forest delegation. You know that Exchange allows you to delegate rights from one mailbox to another, allowing users to access other mailboxes. When you do an Exchange hybrid migration, there are some special considerations you have to take to keep these delegated rights working. Depending on who you ask, you'll get all kinds of different answers about what works when. In this blog post I will explain the confusing case of cross-forest delegation, and what you can expect to work or not work.
There is no cross-forest delegation
Much of the success of Office 365 is built on the Exchange hybrid migration. Since the initial release of Office 365 it has been possible to connect your on-premises Exchange organization to Exchange Online and have the two organization work almost like a single Exchange deployment. In the early days getting hybrid to work was a long and complicated process, but it was possible. The introduction of the hybrid configuration wizard has made the process of configuring hybrid Exchange much better.
Over the past few years, Microsoft has made many attempts to do away with public folders. If you have had the pleasure to work or are still working with Exchange 2007 and Exchange 2010, I’m sure you’ll remember the many rumors about Public Folders being deprecated in “vNext”. Yet, they still exist today in Exchange 2016 –although not in exactly the same form as in earlier versions of Exchange. Not only do they still exist, but Public Folders are still widely used! It’s not unheard of that a company has several million public folders representing terabytes worth of data.
Many administrators reacted surprised when Microsoft first announced “Modern Public Folders” back when Exchange 2013 was introduced to the world. Modern Public Folders offer the same exact user functionality as traditional public folders, but align with Microsoft’s efforts to improve high availability using Database Availability Groups. Traditional Public Folders, which were stored in separate Public Folder databases, did not fit into that paradigm. Even more so, because of that architecture with separate databases and no real HA story, Microsoft could not really support Public Folders in Office 365. To be honest, I am almost certain that Microsoft made the changes to the Public Folder architecture so that they would be able to offer them in Office 365. The fact that on-premises customers can now take advantage of those advancements is an added bonus.
Hybrid environments are complicated. Microsoft has done tons of work over the years to try to simplify the hybrid experience—a huge task when you remember that hybrid Office 365 deployments can cover Active Directory, Exchange, SharePoint, and Skype, along with cloud-only services such as Office 365 Groups. Sometimes, despite the best efforts of the wizards of Redmond, running a hybrid deployment leads to situations that we call Hybrid Headaches… problems that on-prem-only environments won’t encounter but which can be incredibly frustrating obstacles in a hybrid environment.
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.
In case you were caught up in the spectacle surrounding "Back to the Future" day this week, here's what you may have missed in the Exchange and Office 365 world:
A few weeks ago, Microsoft released Exchange 2016 to the public. By now, some of you will have had the chance to play with the latest member in the Exchange Server family and perhaps have formed an opinion on whether it’s something you are willing to consider upgrading to now, or after few more Cumulative Updates have been released.
Here's your weekly dose of popular Exchange and Office 365 insights:
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.
Last week during Microsoft's Ignite conference, I had the pleasure to co-present a session with Timothy Heeney on hybrid Exchange deployments. For those who weren't able to attend Ignite, the recording of that session is available here. During our session, Tim spoke about how Microsoft tests hybrid deployments and the tools it (recently) released to help you troubleshoot hybrid deployments. He also announced some pending changes to the face of the Hybrid Configuration Wizard.