Microsoft Teams Phone in Canada: Replacing Your Old PBX

The phone closet is where old technology goes to hide. Somewhere in your office sits a PBX installed a decade ago, the technician who understood it has retired, and the maintenance contract costs more at every renewal. Meanwhile, the analog and PRI lines feeding it get pricier as carriers wind down their legacy copper networks. If that sounds familiar, Microsoft Teams Phone in Canada has become the most practical exit for small and mid-sized businesses, especially those already paying for Microsoft 365.

You already use Teams for chat and meetings. Teams Phone adds real phone service to the same app: a business number that rings on your laptop, your mobile, or a desk phone, with voicemail, transfers, auto-attendants, and call queues. Your team answers the same way at the office, at home, or on the road.

This guide covers what a Quebec SMB needs to plan: licensing, the three ways to connect Teams to the public phone network in Canada, porting your numbers, building a bilingual auto-attendant, and taking 911 seriously.

Key Takeaways

• Teams Phone turns Microsoft 365 into a complete business phone system through per-user add-on licensing.
• Canadian SMBs pick between Microsoft Calling Plans, Operator Connect, and Direct Routing for phone network access.
• You can port existing local numbers; keep your old lines active until the port completes.
• Auto-attendants handle bilingual menus, and Quebec businesses should greet callers in French first.
• Confirm emergency calling behaviour with your carrier and test 911 addressing before cutover.

Why SMBs Are Replacing Their PBX with Microsoft Teams Phone in Canada

Three pressures drive most of the migrations we see. First, hardware age. Replacement cards for a 2012 PBX are eBay purchases now, and the one local technician who still services your model gets harder to book every year. When the system dies, it tends to die on a Monday morning with no warning.

Second, line costs. Carriers across Canada have been steadily raising prices on analog lines and PRI circuits as they retire copper infrastructure. Many SMBs pay hundreds of dollars a month for capacity they stopped using when half the team went hybrid.

Third, the way people actually work. A desk phone ringing at an empty desk helps nobody. With calling folded into Teams, the receptionist transfers a call to a technician working from Lévis the same way she would if he were down the hall. Presence shows who's available before you transfer. Voicemail lands in the inbox with a transcript.

Moving telephony into Microsoft 365 also fits the broader pattern of replacing single-purpose hardware with cloud services you can manage centrally, license monthly, and scale one user at a time.

What Teams Phone Licensing Looks Like

The core license is called Teams Phone Standard. It's a per-user add-on that sits on top of the Microsoft 365 plan you already have, including the Business plans most SMBs run. Microsoft 365 E5 includes it already. The add-on unlocks the phone system itself: call control, voicemail, auto-attendants, call queues, transfers, and calling policies.

What it does not include is the connection to the public phone network. That's a separate decision, covered next, and it's where most of the real planning happens. Budget-wise, think per-user add-on licensing plus whatever your chosen calling option costs. We deliberately avoid quoting prices in a blog post because Microsoft adjusts them, and a licensing review takes minutes.

One aside worth making: if you're going to audit your tenant for Teams Phone, audit the rest while you're in there. Our guide to Microsoft 365 features you already pay for regularly surprises clients who were buying third-party tools that duplicate their subscription.

Calling Plans, Operator Connect, or Direct Routing?

Teams Phone needs a route to the public switched telephone network (PSTN). In Canada you have three options, and choosing well matters more than any other decision in the project.

Microsoft Calling Plans

Microsoft becomes your carrier. You buy calling plans and phone numbers directly in the Microsoft 365 admin centre, and everything from billing to number management lives in one place. Calling Plans are available in Canada and suit small teams with straightforward needs: no contracts to negotiate, no equipment, fastest to deploy.

Operator Connect

A participating carrier delivers the phone service, but your numbers appear right inside the Teams admin centre and the carrier manages the network connection on its side. Several operators serve the Canadian market. You get carrier-grade support, competitive rates, and someone clearly accountable for call quality. For most SMBs replacing a PBX, this is the sweet spot.

Direct Routing

Your organization (or your MSP) connects Teams to a SIP trunk from any carrier through a session border controller. It's the most flexible option: keep an existing carrier contract, connect analog devices through gateways, handle unusual routing. It's also the most complex, and it's usually the right answer only when the other two options can't meet a specific requirement.

Porting Your Local Numbers to Teams

Your 418, 581, or 514 number is often the most valuable asset in the whole project. It's on your trucks, your invoices, and fifteen years of Google listings. Porting moves it from your current carrier to Microsoft or your Operator Connect provider, and it's the step where migrations most often slip.

A few hard-earned rules. The billing name and address on the porting request must match your current carrier's records exactly; based on what we see in migrations, mismatched records are the top cause of delays. Gather a recent bill and a signed letter of authorization before you start. Port the main number last, after you've tested call flows with temporary numbers. And never cancel the old service in advance: cancelling before the port completes can forfeit the number. Schedule the port for mid-week, mid-morning, with the old system still able to receive forwarded calls as a safety net.

Building a Bilingual Auto-Attendant, French First

The auto-attendant is your new receptionist: it greets callers, offers a menu, routes by business hours, and handles holidays. Call queues sit behind it for teams like support or sales, with hold music, position announcements, and overflow rules. Both come with Teams Phone licensing.

For Quebec businesses there's a design decision that deserves care: language order. Quebec's language rules expect businesses to serve the public in French, and the standard pattern is a French-first greeting with the English option offered right after: Bonjour, hello. Pour le service en français, faites le 1. For service in English, press 2. Build the French menu as the primary path, mirror it in English, and route each language to a queue staffed by agents who can take the call in that language.

You can record professional prompts or use text-to-speech for both languages, and updating a greeting for the holidays takes a minute in the admin centre instead of a service call to a PBX vendor. Keep menus to three or four options; every layer you add costs you callers.

911, Cutover Day, and What Can Go Wrong

Treat emergency calling as a project requirement, never an afterthought. Teams supports dynamic emergency calling, where the location tied to a 911 call can follow the user's network location, but how emergency calls are routed and what address gets transmitted depends on your calling option and carrier. Register your civic address, confirm the emergency calling behaviour with your carrier or operator in writing, test after cutover, and give remote workers clear guidance on keeping their address current.

Then inventory the stragglers. Fax lines, alarm panels, elevator phones, and door intercoms don't move to Teams by themselves. Each needs a decision: keep a single analog line, use an analog gateway through Direct Routing, or replace it with the vendor's modern equivalent.

Finally, plan the cutover like the small project it is: a pilot group for two weeks, certified headsets ordered ahead (add them to your employee onboarding checklist while you're at it), a one-page cheat sheet for staff, the port date booked, and a fallback forwarding rule ready. If you'd rather not manage carrier tickets and call-flow design yourself, our IT support team runs these migrations end to end.

FAQ

Can I keep my current business phone number with Teams Phone?

Yes. Canadian local numbers can be ported to Microsoft or to an Operator Connect carrier. The billing details on the porting request must match your current carrier's records exactly, and you should keep the old service active until the port is confirmed. Plan for a few weeks of lead time.

Do I need to buy desk phones for Microsoft Teams Phone?

Most users don't. A certified headset with the Teams app on a laptop or smartphone covers the typical office worker. Teams-certified desk phones still make sense for reception desks, shared areas, and anyone who strongly prefers physical hardware.

What happens to our calls if the internet goes down?

Calls can still reach the Teams mobile app over cellular data, and you can set forwarding rules that send a main number to a mobile phone. Build this into your continuity plan and test it, because an internet outage should degrade your phone service, never eliminate it.

How long does a PBX to Teams Phone migration take?

For a typical SMB, plan several weeks from decision to cutover. Licensing and configuration move quickly; number porting usually sets the calendar. A pilot group, porting paperwork completed early, and a scheduled cutover date keep the project predictable.

Your PBX won't retire itself, and the next carrier renewal is closer than it looks. If you'd like a clear picture of what a Teams Phone migration would cost and involve for your team, book a free IT assessment and we'll map out the licensing, the porting, and the bilingual call flow with you.