Microsoft Teams Phone for Small Business: The Modern Replacement for Microsoft 365 Business Voice

Microsoft 365 Business Voice helped many small businesses bring calling into Teams. In 2026, the current solution is Microsoft Teams Phone: cloud PBX, calling, voicemail, auto attendants, call queues, and PSTN connectivity managed through Microsoft 365 and the Teams admin center.

Business Voice has been replaced by Teams Phone

Microsoft 365 Business Voice is no longer the current offer for new purchases. Its core idea lives on in Microsoft Teams Phone, which adds business calling to Microsoft Teams so users can make and receive calls from the Teams desktop app, mobile app, Teams-certified desk phones, and supported meeting room devices.

For small and midsize businesses, the closest modern path is often Teams Phone with a Microsoft Calling Plan where available. Other organizations may use Teams Phone Standard with Operator Connect, Direct Routing, Teams Phone Mobile, or shared calling depending on geography, carrier requirements, existing contracts, and compliance needs.

What Teams Phone gives your business

Teams Phone turns Microsoft Teams into a cloud-based phone system. Users can have business phone numbers, place outbound calls, receive inbound calls, check voicemail, view call history, transfer calls, park calls, and use caller ID policies. Calls can be answered from a work computer, smartphone, Teams-certified handset, or headset without exposing an employee’s personal mobile number.

The collaboration experience is unified: chat, channels, meetings, file sharing, calendar integration, and calling are all available in Teams. Outlook and Teams continue to work together for scheduling meetings, joining calls, and adding dial-in details when Audio Conferencing is licensed or included for the tenant and region.

Choose the right PSTN connectivity model

Teams Phone provides the phone system features, but you still need a way to connect to the public telephone network. In 2026, common options include:

Microsoft Calling Plans: Microsoft provides the phone numbers and calling minutes in supported countries and regions. This is often the simplest option for smaller organizations.

Teams Phone with Calling Plan: A bundled option that combines Teams Phone capabilities with Microsoft Calling Plan service where available.

Operator Connect: A Microsoft-approved carrier provides PSTN service directly in Teams. This is useful when you want carrier-managed calling, local support, or more regional coverage than Microsoft Calling Plans provide.

Direct Routing: Your organization or provider connects a supported Session Border Controller to Teams. This is often used for complex voice environments, existing telecom contracts, contact center integrations, analog devices, or countries where other options are limited.

Teams Phone Mobile: A mobile operator integrates a user’s mobile number with Teams, where supported.

Shared calling: Some organizations can reduce the need for one phone number per user by routing outbound calls through shared numbers, depending on calling patterns and licensing eligibility.

Licensing considerations in 2026

Licensing depends on your Microsoft 365 plan and PSTN approach. Teams Phone Standard generally provides the cloud PBX capabilities. Calling requires a PSTN option such as Microsoft Calling Plans, Operator Connect, Direct Routing, or Teams Phone Mobile. Some bundles include both Teams Phone and a Calling Plan, while others require separate add-ons.

Under Microsoft’s current commerce experience, many subscriptions are purchased through CSP/NCE terms. Before changing licenses, review term commitments, renewal dates, add-on dependencies, country availability, and whether users already have Teams Phone through another bundle. Existing Business Voice customers should review their current subscriptions because older naming may have been transitioned or replaced with newer Teams Phone offers.

How a modern Teams Phone deployment works

A current deployment typically follows these steps:

1. Confirm business requirements: user calling needs, main numbers, departments, reception flow, after-hours routing, voicemail, call recording requirements, emergency calling, and international calling.

2. Select PSTN connectivity: Microsoft Calling Plans, Operator Connect, Direct Routing, Teams Phone Mobile, or shared calling.

3. Assign licenses: apply the correct Microsoft Teams Phone and calling licenses to users, resource accounts, common area phones, or shared devices as needed.

4. Configure emergency calling: set emergency addresses and, where required, dynamic emergency calling using network locations such as subnets, Wi-Fi access points, switches, or ports. Requirements vary by country, region, and PSTN connectivity method.

5. Assign or port phone numbers: acquire new user numbers and service numbers, or port existing numbers from your carrier. Porting requires planning so downtime and failed cutovers are avoided.

6. Create resource accounts: use resource accounts for auto attendants and call queues, then assign the required resource account licensing and phone numbers where needed.

7. Configure call flows: build greetings, business hours, holiday schedules, menu options, call queues, voicemail destinations, overflow handling, timeout behavior, and operator routing.

8. Apply policies: configure calling policies, caller ID policies, voicemail settings, external access, compliance policies, and admin roles.

9. Test and train: validate inbound calls, outbound calls, emergency calling behavior, transfers, voicemail, call queues, mobile experience, and receptionist workflows before going live.

Auto attendants, call queues, and service numbers

Teams Phone separates user numbers from service numbers. User numbers are assigned to people or supported shared devices. Service numbers are used for organization-level call flows such as main business lines, auto attendants, call queues, and conferencing bridges where applicable.

Auto attendants can greet callers, provide menu options, route by business hours and holidays, transfer to an operator, send calls to voicemail, or route calls to another voice app. Call queues distribute calls to groups of agents and can use presence-based routing, overflow rules, timeout rules, music on hold, and shared voicemail depending on configuration.

For example, a caller can dial your main number, hear a greeting, press 1 for Sales, press 2 for Support, or dial by name if directory search is enabled. Behind the scenes, Teams uses resource accounts and Teams voice applications to manage that routing.

Administration, security, and compliance

Teams Phone is managed primarily in the Teams admin center, with licensing and identity managed through the Microsoft 365 admin center and Microsoft Entra ID. Administrators should use least-privilege roles, separate global admin work from day-to-day voice administration, and document calling policies before rollout.

Security and compliance planning should include caller ID rules, voicemail settings, call recording or contact center requirements, retention policies for Teams data, external access controls, audit logging, and emergency calling compliance. If your organization has regulated communications requirements, confirm how Teams Phone, any recording solution, and your PSTN provider handle retention, consent, storage location, and access controls.

Migrating from Microsoft 365 Business Voice

If your organization previously used Microsoft 365 Business Voice, the important first step is to inventory your current licensing, assigned numbers, resource accounts, auto attendants, call queues, and PSTN connectivity. Do not assume that the old product name maps cleanly to the best current license.

A practical migration review should confirm whether users need direct numbers, whether main numbers are configured as service numbers, whether calling plans still match usage, and whether Operator Connect or Direct Routing would be more appropriate. It is also a good time to modernize call flows, remove unused numbers, update emergency locations, and replace outdated desk phones with Teams-certified devices where needed.

When Teams Phone is a good fit

Teams Phone is a strong fit when a business wants to reduce legacy PBX hardware, centralize communications in Microsoft 365, support hybrid work, and manage calling, meetings, chat, and collaboration from one ecosystem. It can also simplify onboarding because new users can receive Teams, email, identity, and calling access through coordinated Microsoft 365 administration.

It is not a one-click replacement for every phone system. Businesses with analog lines, elevators, fax, warehouses, paging, complex contact centers, or multinational telecom requirements should plan the architecture carefully and may need Direct Routing, Operator Connect, certified devices, or third-party integrations.

Key takeaways

• Microsoft 365 Business Voice is outdated branding; Microsoft Teams Phone is the current cloud phone system for Teams.
• Teams Phone supports calling, voicemail, call transfer, call park, auto attendants, call queues, caller ID policies, and administration through Microsoft 365 and the Teams admin center.
• PSTN connectivity must be selected separately or through a bundle: Microsoft Calling Plans, Teams Phone with Calling Plan, Operator Connect, Direct Routing, Teams Phone Mobile, or shared calling.
• Emergency calling, number porting, licensing, and service numbers require careful planning and vary by country, region, and carrier model.
• Existing Business Voice customers should review current licensing under CSP/NCE and confirm that their call flows, emergency locations, and phone numbers are still configured correctly.

Planning to replace an old PBX or review a Microsoft 365 Business Voice setup? IT Partner can help assess your environment, choose the right Teams Phone licensing and PSTN model, configure call routing, and migrate users with minimal disruption. See our Microsoft Teams Phone and Microsoft 365 services for help designing a current cloud voice solution.