Microsoft Teams is already the go-to platform for chats, meetings, and collaboration in many companies. With this guide to Microsoft Teams telephony, it also becomes a professional telephony solution: Employees can make calls using their business number and can be reached in the office, while working from home, and on the go. What matters isn\u2019t just whether a call works technically. A good solution must effectively integrate phone numbers, availability rules, security, existing processes, and costs.<\/p>\n
Teams alone does not replace a full-fledged corporate phone system. To make calls to the public telephone network, you need a connection to a telecommunications provider as well as the appropriate Microsoft licenses. Only then can employees call external numbers and be reached at a Swiss or international business number.<\/p>\n
For small teams, one direct extension per person is sometimes enough. In an SME<\/a> In an organization with multiple departments, the requirements are usually more extensive: a central main number, an automated greeting, business hours, call groups, call forwarding, queues, call transfers, and call analytics are all part of everyday operations. Fax machines, intercom systems, conference rooms, analog devices, and a CRM system may also continue to play a role.<\/p>\n This is exactly where the difference between a simple Teams integration and a well-designed communication architecture becomes apparent. Teams serves as the user interface for many employees. The phone system and the trunk in the background, on the other hand, control how calls are routed, prioritized, logged, and secured.<\/p>\n There are three common models for connecting Teams to the public telephone network. Which one is right depends on the existing infrastructure, the desired flexibility, and the range of features.<\/p>\n With Calling Plans, the telephony service comes directly from Microsoft. The model is easy to set up and may be suitable for clearly defined use cases. In Switzerland, however, and when international phone numbers are needed, companies should carefully check which numbers, countries, rates, and additional features are actually available. Those who need complex PBX scenarios or custom routing rules may quickly reach their limits, depending on their requirements.<\/p>\n Operator Connect connects Teams to a Microsoft-approved carrier. Provisioning is largely handled in the Teams Admin Center, which can simplify administration. This is an attractive option for companies seeking standardized Teams telephony, provided the chosen provider covers all the necessary phone numbers, locations, and features.<\/p>\n The advantage lies in the ease of implementation. The downside: Specific requirements\u2014such as multi-level IVR menus, integration with an existing phone system, customized emergency call protocols, or special routing logic\u2014must be addressed early on. A standardized solution is not automatically the right fit.<\/p>\n With direct routing, Teams is connected via a session border controller (SBC) to a SIP trunk and, if needed, to a cloud-based or on-premises phone system. This model offers a great deal of flexibility. Existing phone numbers can be ported, locations can be connected in a uniform manner, and PBX functions can be continued or expanded as needed.<\/p>\n For companies with multiple locations, reception groups, contact center requirements, CRM integration, or a mix of end devices, direct routing is often the more cost-effective and sustainable option. However, it requires a well-planned architecture. SBCs, network quality, security policies, and responsibilities must not be addressed only after the go-live.<\/p>\n The most common problems with Teams telephony aren\u2019t caused by the software, but by incomplete requirements. If you only count the number of users, you\u2019ll overlook the operational aspects of telephony. It makes sense to map out your current call routes: What are the main numbers? Who answers incoming calls? What happens outside of business hours? Which teams or individuals need direct extensions?<\/p>\n Special cases are just as important. These include emergency numbers and accurate location mapping, alarm or elevator phones, DECT devices, door intercoms, fax services, and shared areas such as the reception desk or conference rooms. Interfaces with CRM, ERP, or contact center solutions should also be documented. CTI integration is only beneficial if responsibilities, data quality, and workflows are aligned with it.<\/p>\n For distributed organizations, it\u2019s worth taking a look at the network architecture. Work-from-home stations, mobile employees, and remote offices do not need identical technical equipment, but they do require a consistent policy for availability and security. Business phone numbers should not have to be redirected to personal cell phone numbers simply because an employee is not at their desk.<\/p>\n For customers, a phone number is part of a company\u2019s identity. A migration should therefore retain existing main numbers and extensions whenever possible. Number porting takes time and requires the correct documentation. Parallel operation, clear deadlines, and a tested contingency plan ensure that customers do not end up calling a dead line during the transition.<\/p>\n The responsibility for managing call handling lies with the line departments, not exclusively with IT. Sales may require different rules than Support, and the reception desk may have different rules than the on-call service. Teams call queues can handle a wide range of scenarios. A PBX complements these systems in cases where, for example, complex IVR menus, time-based routing, overflow destinations, group permissions, or comprehensive statistics are required.<\/p>\n Here\u2019s an example: Calls to the main number are initially routed to the front desk during business hours. If no one answers there, they are forwarded to a designated group. Outside of business hours, an automated message provides information about the next business day or forwards urgent inquiries to the on-call service. Such rules should be easy for customers to understand and simple for administrators to customize.<\/p>\n Telephony via Teams is a service that relies on the Internet, identities, and networks. That\u2019s why good headsets and a fast connection alone aren\u2019t enough. Voice quality depends on stable bandwidth, low latency, proper prioritization, and a correctly configured network. When connections are heavily loaded, Quality of Service can be critical.<\/p>\n On the security front, multi-factor authentication, clearly defined roles in the Teams Admin Center, and a structured approach to managing user accounts form the foundation. The SBC protects the boundary between the corporate network and the telecommunications provider when Direct Routing is used. Firewall rules, certificates, logging, and updates must be managed on an ongoing basis, not just during implementation.<\/p>\n Data protection also deserves attention. Call recordings, voicemail, and call data may contain personal or business-critical information. Companies should define who is authorized to access this information, how long data is stored, and what guidelines apply to recordings. Technical measures are no substitute for clear internal rules.<\/p>\n The cost of Teams calling involves more than just the per-minute rate. You must also factor in Microsoft licenses for the calling feature, SIP Trunks or Connection Fees<\/a>, phone numbers, any flat-rate plans, PBX licenses, hardware, implementation, and managed services. Depending on the plan, international calls, calls to mobile numbers, or special numbers may also be billed separately.<\/p>\n A flat rate makes budgeting easier, but it isn\u2019t automatically the most cost-effective option for every usage profile. Companies with few external calls may be better off with per-minute billing. For teams that make a lot of calls, service organizations, or international locations, however, a detailed review of rate plans is worthwhile. The key is to ensure that costs remain transparent per user, location, and usage scenario.<\/p>\nChoose the Right Connection Method<\/h2>\n
Microsoft Calling Plans<\/h3>\n
Operator Connect<\/h3>\n
Direct Routing with SIP Trunk and PBX<\/h3>\n
Identify Requirements Before Migration<\/h2>\n
Organizing Phone Numbers, Availability, and the PBX Properly<\/h2>\n
Security and voice quality go hand in hand<\/h2>\n
Plan Licenses and Costs Transparently<\/h2>\n