As part of your Exchange Hybrid deployment you might introduce new Exchange Servers into your organization. If you’ve planned your deployment correctly, then these will be covered by Hybrid Exchange licences included within your Office 365 Enterprise subscription.
When you don’t need a Hybrid licence
First and foremost, you must consult Microsoft or your licensing specialist for correct guidance for whether you are licensed correctly. However, there is as a key scenario where you will not need to acquire Exchange Hybrid licences.
If you are running Exchange Server 2010, 2013, 2016 or 2019 then you already have Exchange Hybrid capabilities built in to your Exchange Servers today.
Your Client Access services will be used for Autodiscover services and Exchange Web Services based communications. This includes redirecting clients to the cloud, Federated Sharing for Free/Busy and Mailbox Moves. Your Hub Transport services also have the capability built-in to manage Hybrid mail flow between Office 365 and your Exchange Server.
Adding additional servers to your organization to support Exchange Hybrid is a common piece of bad advice shared regularly. If you have a healthy Exchange 2010+ organization today, then you almost certainly have everything you need and will not need to licence Hybrid Servers.
When you do need a Hybrid licence
If you are running Exchange Server 2003 or 2007 you will need to add Exchange 2010 or 2013 servers if you want to perform a Hybrid migration. As those servers don’t have any Hybrid components built-in, then for many organizations it means a part-migration to a newer version of Exchange Server. Typically, this means implementing co-existence with the newer version, and migrating some client-facing services across, such as Autodiscover, Exchange Web Services, ActiveSync and Outlook Anywhere.
It’s important to note that when you add Exchange Hybrid servers to your Exchange 2003/2007 organization you cannot move any mailboxes to the servers if you wish to qualify for a “free” Exchange Hybrid licence. That means you can’t (for example) stage mailboxes from Exchange 2003 to Exchange 2010 first, before moving them to Office 365.
Another key scenario where you are likely to need a Hybrid licence is after you have completed your migration from Exchange Server 2010 to Office 365. After moving your final mailboxes and if you have them, Public Folders, you will decommission Exchange Server 2010. Most organizations will keep Azure AD Connect in place after the migration completes, which means Hybrid Identity (where AD remains the master) is in place. You will therefore require require Exchange Server to manage those attributes – and potentially to relay SMTP email, too. This of course is a great use of an Exchange 2016 or higher server.
Finally – and it comes as a surprise to some organizations – if you have never had Exchange within the organization then you might need to install Exchange Hybrid servers for attribute management within the local AD. As mentioned above – if you use Azure AD Connect, you will have Hybrid identity in place. Many organizations running Domino today and migrating to Office 365 find they need to install an Exchange Hybrid server (or two) and utilize the free Hybrid licence.
Acquiring Exchange Hybrid licences
The process to acquire an Exchange Hybrid licence has recently changed. Previously, you would request Exchange Hybrid licences from the Office 365 portal. This of course, made it easy to request the licences you needed in advance in the same way you licenced Exchange Servers traditionally within your organization.
If you are licensing new Exchange Servers for Hybrid today, the process has changed. You will now licence new Exchange Hybrid servers within the Office 365 Hybrid Wizard.
When you run the Wizard, you will be able to choose the option Licence this server now to apply the Exchange Hybrid licence:
After choosing to licence the server, you’ll be provided with the option to copy product key if you need to apply the Hybrid licence key manually (for example, using the Exchange Admin Center, or PowerShell).
Steve is a Microsoft MVP for Office Servers and Services. He enjoys getting hands-on, solving some of the more complex problems associated with migrating to the cloud or to newer versions of Exchange Server.
Rkast says
February 12, 2019 at 2:53 amNice write up. For a free key you cant have any mailboxes on the server or pf. But what if your IDM first creates a user and mailbox on-prem and then immediately move the mailbox to o365? Generatie a key when the box is empty but are you compliant and eligble?
Steve Goodman says
February 12, 2019 at 3:23 amThe key will be generated regardless of whether there is a mailbox present, IIRC.
In the above case, then it’s less about “getting the key” but ensuring you remain compliant with Microsoft licensing throughout the Exchange Server ‘s lifecycle. That might mean reconfiguring your provisioning system to stamp the new user object with the necessary attributes to make it a Remote Mailbox.
gman77 says
March 12, 2019 at 12:10 amwe have exchange 2013 in house currently and am considering virtualizing it so it can be used for management purposes.
if in a few years we need to upgrade exchange to a newer version, could you use this key?
Steve Goodman says
March 12, 2019 at 9:26 pmMy understanding of the licensing terms would be that that is acceptable, and a fairly common end-point as well.
Kevin says
March 21, 2019 at 12:33 amHello Steve,
Great information here–Thanks for sharing!
Is there a link to the Microsoft Terms of Licensing for the use of the Hybrid Key? I frequently encounter scenarios where my customer may have Exchange 2010 SP 3 (fully patched) – and as you have pointed out, is a version of Exchange that already has the hybrid functionality built in.
As many clients understand that to remain in a “supported” configuration Microsoft recommends keeping at least one Exchange Server in the environment. The concern that is raised (especially in scenarios where EOL support is quickly approaching) could the HCW key be used as a means to remain in both a supported configuration AND with an Exchange Server version that is not “out of support”?
If so- when running (or re-running) the HCW in an Exchange 2010 environment, would the option be presented to obtain this key (for 2016)? This remains a bit unclear and Microsoft seems a bit gray on this. (It is understood this key is for a “coexistence edition” which has limited functionality and cannot be used as a mailbox server).
Your clarification and any supportive links would be HUGELY appreciated.
Thank you sir!
K
Ted says
April 23, 2019 at 8:29 pmHi Kevin, did you find an answer to this?
Matt says
March 26, 2019 at 1:09 amSteve:
I have a client that is using SBS 2011 and will be getting Office 365 Business Premium licensing. We were thinking of spinning up a new server to run Exchange 2016 and then using the HCW to license the Exchange 2016 server as the Hybrid server. We would then migrate mailboxes and decommission SBS 2011. Will this work, or will SBS 2011 and / or O365 Business Premium licensing prevent it?
Matt
Dan Kyaw says
May 3, 2019 at 2:46 pmHi Steve,
We already have hybrid server (on-prem) which has been synchronizing successfully. we are planning to replace it with a new hybrid server which will now be located in the cloud. How do i go about licensing the new hybrid server? Also what is the best practice of dealing with existing on-prem hybrid server? all resources were migrated to the cloud a while back and this server was being used just for management purpose. Thanks.
Manuel Berfelde says
May 28, 2019 at 12:22 amHi Dan,
have you found a solution for this?
I have the same question.