The evolution of corporate communications and the role of Microsoft Teams Phone
The transition from traditional on-premise IP PBX systems to cloud-based unified communications is becoming a strategic decision for many companies. The primary challenge for CIOs is determining whether Microsoft Teams Phone can provide the same level of functionality, reliability, and security as existing on-premise infrastructure, while optimizing costs and operational complexity.
Microsoft Teams Phone integrates PSTN telephony features into the cloud-based Teams platform, offering an alternative to traditional IP PBX systems.
Calling plans: Understanding models and costs
One of the fundamental aspects differentiating Microsoft Teams Phone from an on-premise IP PBX is the PSTN connectivity model. Microsoft offers its own Calling Plans, which allow Teams Phone users to make and receive external calls directly through Microsoft. These plans are available in Domestic and International options, including a certain number of minutes per month.
Mechanism: Users receive phone numbers and a bundle of minutes managed by Microsoft 1. This simplifies administration by eliminating the need for direct contracts with traditional telecom operators for basic PSTN services.
Cost impact: Calling Plans represent a predictable monthly per-user expense 1, which can be advantageous for companies with stable call volumes. However, for organizations with high international call volumes or specific tariff requirements, a direct comparison with existing SIP trunk or analog line contracts is crucial. Potential additional costs for exceeding minute limits or calls to special numbers must be considered.
Practical step: Conduct a detailed audit of current telephony costs, including per-minute rates, line rental fees, and number charges. Compare this data with the cost and included minutes of Microsoft Teams Calling Plans, factoring in projected call volumes.
Session Border Controllers (SBCs): Necessity and integration
For companies that prefer not to use Microsoft's Calling Plans or have existing contracts with telecom operators, Microsoft Teams Phone supports the Direct Routing option. This mechanism allows connecting proprietary SIP trunks to Teams Phone via a certified Session Border Controller (SBC).
Mechanism: An SBC acts as an interface between the on-premise PSTN infrastructure (or a third-party SIP provider) and the Microsoft Teams cloud platform 2. It ensures security, media transcoding, call routing, and compatibility between different SIP protocols. An SBC can be deployed on-premises or as a virtual machine in the cloud.
Impact on security and manageability: Deploying an SBC adds a layer of security, protecting the corporate network from external threats and providing traffic encryption. However, it also increases operational complexity, as the SBC requires configuration, monitoring, and maintenance. SBC selection, licensing, and integration represent additional cost and risk factors.
Practical step: Evaluate the necessity of Direct Routing based on existing operator contracts, routing flexibility requirements, and security needs. If Direct Routing is the preferred option, research certified SBC solutions and their deployment and licensing requirements.
Survivability: Ensuring communication continuity
Communication continuity is critical for any organization. Traditional IP PBX systems often have built-in fault tolerance mechanisms, such as redundant controllers, SRST (Survivable Remote Site Telephony), or geographic redundancy. Microsoft Teams Phone, as a cloud solution, relies on the distributed architecture of Microsoft 365 for high availability.
Mechanism: In case of connectivity issues with the Microsoft cloud, Teams Phone can utilize survivability mechanisms. For example, with Direct Routing, if the SBC loses connection to Teams, it can be configured to redirect calls to alternative numbers or local PSTN gateways. The Branch Office Survivability (BOS) feature allows users to continue making and receiving internal calls and, under certain conditions, external calls via a local SBC, even if the primary connection to Microsoft 365 is temporarily unavailable 3.
Impact on continuity: While Microsoft's cloud infrastructure is highly available, reliance on internet connectivity remains a key risk. Teams Phone survivability mechanisms can mitigate this risk, but they require careful planning and configuration. Compared to on-premise solutions, where IT departments have full control over redundancy, in the cloud, part of the responsibility shifts to the provider.
Practical step: Develop failure scenarios for your network infrastructure and assess how Microsoft Teams Phone with survivability mechanisms (e.g., Direct Routing with a local SBC and BOS) would behave in each. Compare this with your current IP PBX’s capabilities for ensuring communication continuity.
Emergency calling: Compliance with regulatory requirements
Emergency calls (e.g., 911 in the US, 112 in Europe) are a critically important aspect of any telephone system. Traditional IP PBX systems are typically configured to transmit the caller’s precise location to emergency services.
Mechanism: Microsoft Teams Phone supports Dynamic Emergency Calling 4. This allows automatic determination of a user’s location based on their network connection (e.g., Wi-Fi access point, IP address) and transmission of this information to emergency services. This requires integration with network infrastructure and configuration of the Emergency Location Information Service (ELIS).
Impact on safety and compliance: Improper configuration of emergency calls can lead to serious consequences, including delays in providing assistance. For CIOs, it is crucial to ensure full compliance with local and national regulatory requirements for emergency calling. This may necessitate additional configurations, testing, and potentially the use of third-party services to ensure location accuracy.
Practical step: Review local and national regulatory requirements for emergency calls. Develop a plan for configuring and testing emergency calling functionality in Microsoft Teams Phone, including dynamic location determination and routing to appropriate services.
Total Cost of Ownership (TCO): A comprehensive analysis
Evaluating the Total Cost of Ownership (TCO) is a key factor in migration decisions. TCO for Microsoft Teams Phone includes not only licenses but also other hidden and operational costs.
Components of TCO for Teams Phone:
- Licenses: Cost of Microsoft 365 licenses (which include Teams) and additional Teams Phone Standard or Teams Phone System licenses, as well as Calling Plans or Direct Routing licenses 5.
- Hardware: IP phones, headsets, and potentially an SBC for Direct Routing.
- Network infrastructure: Network modernization to ensure necessary bandwidth and QoS for voice traffic.
- Implementation and migration: Services for planning, configuration, integration, and number porting.
- Training: Training for end-users and IT staff.
- Support and operations: Ongoing support, monitoring, and system management.
Comparison with IP PBX: A traditional IP PBX has significant initial capital expenditures (CAPEX) for hardware and software but may have lower operational expenditures (OPEX) over time, excluding upgrades and scaling. Teams Phone, conversely, follows an OPEX model with recurring license payments, which can provide greater flexibility and scalability without large upfront investments. However, it is important to consider all hidden costs, such as network upgrades and integration.
Practical step: Create a detailed TCO model for both scenarios (retaining IP PBX and migrating to Teams Phone) over a 3-5 year period. Include all direct and indirect costs, as well as potential savings from simplified administration and integration.
Conclusion: A practical checklist for decision-making
The decision to replace a traditional IP PBX with Microsoft Teams Phone is complex and requires thorough analysis. Teams Phone offers modern unified communications capabilities and integration with the Microsoft 365 ecosystem, but it demands adaptation to a cloud model and attention to specific architectural and operational aspects.
Checklist for CIOs:
| Criterion | Current State (IP PBX) | Expected State (Teams Phone) | Impact Assessment (Low/Medium/High) | Decision (Acceptable/Requires Research/Unacceptable) |
|---|---|---|---|---|
| Cost of Calling Plans (Domestic/International) vs. current tariffs | ||||
| Necessity and cost of SBC (Direct Routing) vs. current infrastructure | ||||
| Survivability mechanisms (BOS, local SBC) vs. current fault tolerance | ||||
| Emergency Calling (911, 112, etc.) compliance with regulatory requirements | ||||
| Overall TCO (licenses, hardware, support, training, operational costs) | ||||
| Integration with existing business applications and CRM | ||||
| Network infrastructure requirements (bandwidth, QoS) | ||||
| Security and compliance with company policy | ||||
| Migration and support complexity | ||||
| Availability of necessary features (e.g., call centers, call recording, IVR) |
Softline IT assists in planning and implementing unified communications solutions: from auditing the current state to a coordinated change plan.
Softline IT helps teams plan and implement unified communications, from an assessment of the current environment to an agreed change plan.
