With Operator connect we will be able to manage partnerships with our local telephony providers and provide telephony features to end users in Microsoft Teams. We can evict the need of managing & maintenance of SBC locally in the datacenter unless we have some specific requirements for routing calls to another ip-pbx environment within the organization .This is a big advantage for customers who want to go completely to the cloud and eliminate their on-premise dependency.
Microsoft recently announced Operator Connect to be General and it can be a good start for organizations which has less dependency on legacy PBX integrations in their environment. For instance when a customer having only Skype for business, SBC and a SIP Trunk with their local telephony provider in their current configuration can easily think of moving this enterprise voice service to cloud easily by benefiting the operator connect service.
At the moment of writing this post there are 22 operators present in this program which supports upto 60 regions all over the world with Microsoft and the list can definitely grow in future. In this blog we will run through the steps to enable operator connect and the steps to enable them with the provider NTT.
Below prerequisites are required from Office 365 tenant to evaluate the operator connect service:
- Users must have minimum E1+Phone System, E3+Phone System or E5 License.
- All these users leveraging the operator connect service must be in Teams Only mode.
- Emergency Address must be created and assigned to these users.
In our case we are testing from the location Netherlands and hence we have only Netherlands defined as Emergency address.Continue reading