In part two of this series, we took a look at how OAuth is used when establishing an Exchange Hybrid configuration.
In the final part of this series, we will take a look at the other features of Exchange Online federation, including the InterOrg Relationship as well as the Hybrid Configuration.
Now that you’ve read the first two parts of this series, let’s review some of the base features of the Exchange hybrid configuration. As in years past, some of the features an Exchange hybrid deployment will give your organisation include:
- Authenticated SMTP routing between on-premises and Exchange Online
- A unified global address list (GAL)
- Free/busy and calendar sharing between on-premises and Exchange Online
- Migrations to and from Exchange Online
- The ability to enable a cloud-based archive for an on-premises Exchange mailbox
For more details on the features that come available with an Exchange hybrid deployment, please refer to the following link:
https://learn.microsoft.com/en-us/exchange/exchange-hybrid#exchange-hybrid-deployment-features
Do You Need a Hybrid Deployment
As stated in a previous blog, Microsoft has now given you the choice of removing your last Exchange server. However, your organisation may have requirements to maintain an on-premises Exchange server. These are some of the reasons your organisation may need to keep at least one on-premises Exchange server:
- Mailboxes left on-premises – of course, if you have some mailboxes, that, for whatever reason, cannot be migrated to Exchange Online, you will still need to maintain an on-premises Exchange server
- Data Loss Prevention (DLP) requirements mandate routing to an on-premises service – your organisation may have a DLP service that can only connect to on-premises, and so, you will need to enable centralised mail transport to route all mail back to on-premises
- The ability to return to on-premises – even after migrating all of your mailboxes, your organisation may require that you have the quick and easy ability to migrate back to on-premises
Those are just some of the reasons why you may choose or need to keep at least one Exchange server on-premises. Microsoft is making it easier to finally remove the last Exchange server, which is what more and more organisations are now doing.
Until your organisation decides to remove the last Exchange server, it is important to plan out your Exchange hybrid deployment, to understand the requirements, and to keep all of your servers and your Exchange hybrid deployment up to date.
I thank you for spending some of your time reviewing with me Oauth vs Dauth, and other features of the Exchange hybrid deployment.
In this series, we explored the features of Exchange Hybrid configuration, including OAuth, InterOrg Relationship, and Hybrid Configuration. Now, let’s review some of the base features of the Exchange hybrid deployment, such as secure SMTP routing, unified global address list (GAL), free/busy and calendar sharing, migrations, and the ability to enable a cloud-based archive.
If you need assistance with planning and deploying your Exchange hybrid environment or migrating to Exchange Online, Insentra is here to help. As Microsoft continues to make it easier to remove the last Exchange server, it’s essential to keep your servers and Exchange hybrid deployment up to date.
If your organisation requires maintaining an on-premises Exchange server, Insentra can assist you in fulfilling your needs. We appreciate your time spent with us learning about Oauth vs. Dauth and other features of the Exchange hybrid deployment.
Contact Insentra today to learn more about Exchange Hybrid deployment and Exchange Online migration.
