“Hybrid” is possibly the most overused word in our Microsoft world. It means everything and nothing. I often cringe when people talk about their topology as “hybrid” without defining it further, I even try to ban using “hybrid” without any context at Modality :-).
So why am I not a fan? Many different Skype for Business and now Microsoft Teams topologies are referred to as hybrid with quite different functionality. Beyond Microsoft UC “hybrid” is also used in Exchange, SharePoint and other workloads. So here is a quick breakdown of the different types of Skype for Business and Microsoft Teams “hybrid” and what I believe is the correct name to use to refer to them (IMHO).
If you have 100% SfBS and Exchange UM On-premises, or 100% SfBO/Microsoft Teams and Microsoft PSTN Calling plans, you are not hybrid, and things are nice and easy. For the uninitiated “hybrid” means some workload(s) on customer premises (or hosted by a partner) and some workloads in Microsoft Office 365. Here are the 5 types:
EXO UM: Skype for Business Server and Exchange Online Unified Messaging
In this scenario, all users are homed on-premises on Skype for Business Server, but their voicemail is routed via an Edge server to Exchange Online Unified Messaging, which “answers” the call, records the message and puts it in an Exchange Online User Mailbox.
Where this makes sense?
- I have some/all my mailboxes in Exchange Online but have Skype for Business Server
- Exchange Online UM can be used for any SFBS Users in any topology with SFBS. SFBO/Teams users always use Azure Cloud Voicemail.
Blog: Configuring Skype for Business Server with Exchange Online Unified Messaging
Side note, you used to be able to connect third-party IP PBX’s to Exchange Online Unified Messaging, but this has now been depreciated.
Split Domain: Skype for Business Server and Skype for Business Online for the same SIP Domain(s)
In this scenario, Skype for Business Server and Skype for Business Online are set up to work together in the same topology, users can be homed either on Skype for Business server or Skype for Business Online, with the same SIP domain, and can communicate seamlessly.
Where this makes sense?
- I want to have some users homed in Office 365 to reduce SfBS Server/take advantage of cloud scale/Cloud PSTN Audio Conferencing/Cloud Evergreen service
- I have some requirement for users to be on SfBS, compliance call recording, specific application integrations, response group use cases, Survivable Branch Appliances
- I get the benefits of the cloud where it makes sense, and all the features of SfBS, but also all the complexity of running both.
- Supports a gradual migration from SfBS to SfBO
“Split domain” does not define where PSTN (telephony) is connected or even which features/modalities are enabled in SfBS and SfBO, so whenever someone says they are split domain there are some follow-up questions/options
- SfBS users can only consume user PSTN connectivity and PSTN conferencing connectivity via SFBS, likely on-premises gateways and SIP or ISDN connectivity
- SFBO users can consume user PSTN connectivity via Microsoft user PSTN Calling Plans in Office 365 or via the SfBS servers (see On-Premises Call Handling)
- SFBO users can only consume PSTN Conferencing via Microsoft Audio Conferencing or a certified third-party Audio Conferencing Provider (ACP)
OPCH: On-Premises Call Handling
A bit of a Microsoft insider phrase. This is specifically a setup for SFBO users routing their user PSTN calls via SfBS. Therefore it’s a configuration option when you have a Split domain setup. Indeed you may set up a Split domain and have 100% of your users on SFBO with OPCH; it’s technically still split domain.
The acronym is saying users calls are handed via SfBS On-Premises
Where does this make sense?
- I already have an investment in SfBS On-Premises with PSTN Gateways but want to move users to the cloud for their main services and conferencing
- I want to use SFBO with PSTN connectivity in a country Microsoft PSTN Calling Plans do not service and already have SFBS somewhere in my global topology
- If there are any SfBS (or Lync 2013) in a customers topology, this is the only option to “Bring their own user telephony/own carrier” to SfBO users. CCE cannot be used alongside SfBS.
- Requires SfBS servers to be licenced.
This is only for routing user PSTN connections, Cloud PSTN Conferencing and Cloud Auto Attendants/Hunt Groups require numbers from Microsoft (you can potentially 1:1 forward to from your PSTN numbers to Microsoft numbers)
CCE: Cloud Connector Edition
In this scenario, 100% of users are on SfBO, but a specific appliance, the “cloud connector edition” allows the customer to connect their own PSTN carrier for user numbers to SfBO. Cloud Connector Edition can be installed on a commodity server or can be bought in an appliance from AudioCodes or Sonus.
Where does this make sense?
- I want SfBO but want to bring my own PSTN carrier
- I have no requirement in my topology for SfBS
- CCE itself requires no additional licence beyond having an active SFBO user licence, but if you deploy your own on a commodity windows server you do need to licence Windows Datacenter Edition
CCE cannot be used if there is any SfBS or Lync 2013 in a customers topology, so cannot be used alongside any SfBS or Split domain.
Microsoft Teams Direct Routing
AKA names while in development: Hybrid Voice Connectivity, Bring Your Own Trunk (BYOT), Direct Connection For Microsoft Teams
Still a roadmap item. So there is limited public information available and a few names floating around. What has been shared is that this will allow customers to “bring their own user PSTN” for Microsoft Teams users. It will use certified Session Border Controllers from Ribbon (previously called Sonus) and AudioCodes which will connect directly to the Microsoft Teams cloud service. It will not require a windows server(s) like CCE.
Where does this make sense?
- I am using Microsoft Teams and want to bring my own user PSTN connectivity
Notes:
- This can be deployed alongside other SfBS/SFBO/CCE topologies
- AudioCodes and Sonus have confirmed CCE appliances will also be able to work in this model
- This is only for Microsoft Teams, not SfBO
- Currently on the roadmap for Q2 2018 (end of July)
- Since SBC’s can connect directly to the service, I would anticipate Telco’s offering this as a service with no need for a customer to have an on-premises SBC
So hopefully you are now armed with the different types of “hybrid” and can explain the differences.
Thanks to this document from Microsoft for the graphics I adapted: Plan your Skype for Business hybrid deployment
Any questions welcome
Tom
[…] http://tomtalks.blog/2018/02/know-5-types-hybrid-skype-business-microsoft-teams/ […]
This is just what I needed, thanks! Now all I need to do is create or find a matrix to evaluate the various one-time and ongoing cost estimates, especially in light of what we learned about the calling plans at the SfB/Teams User Group meeting.
Great, glad it’s useful
[…] The Feature is now generally available, it lists at $8 per phone per month, which effectively is the “Cloud Phone System” Licence to run an IP Phone. In addition, to make calls, you will need a Microsoft PSTN Calling Plan or “bring your own trunk” […]
[…] It’s worth taking a look at the blog of Tom Arbonuth, who cover’s 5 different types of hybrid’s: Know The 5 Types of Hybrid for Skype for Business and Microsoft Teams […]
Hi Tom. Thanks for the overview, really useful.
Do you know if once a hybrid server has been used for a migration to 365 and decommissioned, can we then spin up a new hybrid from a completely different forest (and with a different SIP domain) to migrate those users into the same tenancy? We basically have 3 completely separate companies we wish to migrate into the same tenancy, one at a time. Microsoft seem to say you can only have a hybrid connected to 1 on-premise SfB topology but they don’t mention repeating the process for a different topology after you’re done with the 1st hybrid.
Matt
[…] I talked about on my 5 types of hybrid blog post, the only option to bring your own PSTN carrier to Microsoft Teams will be a model where […]
Hi Tom,
Thanks for the write up. It’ll be interesting to see how Teams progresses, once it starts to implement Skype-like voice functionality.
I read one of your other articles on Skype Hybrids as we are planning on migrating to Skype Online, but we have several completely separate Skype installs which we would like to migrate and you can only have a single Skype hybrid connection.
If we decommission a hybrid connection and on-premise servers, after migrating all users, can we create a new hybrid connection from another on-premise Skype (different SIP domain and forest – in fact different company) and migrate those users into the same tenancy?
We would like to migrate them all into a single 365 tenancy, but it can be done consecutively if we can’t do it concurrently.
Hi,
This is quite a big topic, but basically, you need split domain hybrid to move from SfBS to Teams, you can add or remove hybrid at any time in the process
Hi, Thanks for post; I have 2 questions:
Are we saying that Skype for Business online will remain as it is in coming months and it will not be migrated to Teams
And also Skype for Business vNext 2019 server based on premise version is coming in this year
My question is: for future SFB Hybrid setup ,
1. will it be Skype for Business Server 2019 to Teams integration or
2. there will be Skype for Business server 2019 to another version of Skype for Business online
SFBO has no end of life date. MSFT is currently saying no one will be “pushed” to Teams. So the message is you can stay on SFBO as long as you need, but be aware that MSFT clearly hopes customers will move from SFBO to Teams over time.
SFBS 2019 will likely “hybrid” with SFBO, not Teams.
SFBO doesn’t really have a “version” it’s a continuous service.
Hope that helps
Tom
Hi Tom,
In Case of CCE deployment, how is the dial-in conferencing handled?
You can’t route your own PSTN dial-in conference numbers to SFBO via CCE, you have to buy PSTN conference numbers/service from Microsoft
Hi Tom,
A really great article that explains the topic in an accessible way. I’m not sure about to the correctness of the acronym OPCH. In my point of view, it stands for Configuration Hybrid. Can you check it?
Hi Piotr,
Thanks for the comment. It’s an “internal” Microsoft acronym, so there is no official source to check to be honest. I’m pretty confident the “more correct” is “On-Premises Call Handling” but I’ve seen vendors use “configuration hybrid”. “Call Handling” is a clearer description IMHO.
Happy to be corrected if someone has a definitive answer.
cheers
Tom
Hi,
can we have a CCE and an classic hybrid SFB at the same time ?
You can’t have CCE and OPCH in one topology I’m afraid.