Should Your Multi-Site Business Move to Microsoft Teams Voice?
If your business runs from more than one site, the phone system tends to be the last thing anyone wants to think about. It works, mostly: a PBX at head office, a couple of branches on their own handsets, a hosted-PBX contract someone signed years ago, a bill from a different supplier than the internet. This post is for ops leads, IT leads, and finance or general managers at multi-site SMEs deciding what to do about that. By the end you will know what Microsoft Teams Voice is, the three ways to deploy it, where a legacy phone system falls short across several sites, and whether to keep, consolidate, or replace what you have. Already know what you need? See our Microsoft Teams Voice page.
What Microsoft Teams Voice is, and the three ways to deploy it
Microsoft Teams Voice is Microsoft Teams Phone with a way to make and receive calls to ordinary phone numbers. Your team already uses Teams for chat, meetings, and presence; Teams Voice adds the dial pad, so the same app rings their desk, laptop, or mobile on one business number. Microsoft sells the product as Microsoft Teams Phone; Metwide calls it Microsoft Teams Voice because that is how buyers in Australia tend to describe it. Calls stop living in a box on the wall and start living where the rest of the conversation already does. Analogue and specialist lines, such as lift phones, alarm and EFTPOS lines, paging, and common-area handsets, are a separate piece of work and need their own plan.
What Teams Phone does not include is the connection to the public phone network, and there are three ways to provide it.
- Microsoft Calling Plans: Microsoft is the PSTN carrier, with numbers and porting handled through Microsoft’s own admin tools and support. Simplest to turn on; number availability and porting flexibility can be narrower than a local carrier offers.
- Operator Connect: a Microsoft-certified operator, usually a telco or managed-services partner, supplies the calling plan and numbers, with the link into Teams provisioned through Microsoft’s own console. Operator Connect in Australia has matured over the last couple of years and suits businesses that want one managed voice supplier without a bespoke build.
- Direct Routing: a Session Border Controller, or SBC, sits between an operator’s SIP trunks and Teams, the most flexible model and the most involved to design. Direct Routing in Australia is common where a multi-site dial plan or inherited number ranges make the off-the-shelf options too rigid.
Which model fits which kind of business is an engineer conversation, because the differences that matter sit underneath: who supplies the numbers, who you call for carrier support, how emergency calling is set up, and how much design flexibility you get. For your staff the call experience looks much the same across all three: calls in Teams, on one number, across every site.
Where a legacy phone system falls short for multi-site businesses
Most multi-site SMEs are not starting from a clean sheet. The usual starting point is an on-premise PBX at head office with branch extensions on copper tails, a hosted-PBX vendor running a phone instance per site, a scatter of NBN-VoIP softphones and old handsets bought one at a time, or a mix. None of that is wrong on its own: a site with a working hosted PBX, clean call quality, and a contract with a year to run is not a problem to solve. The friction shows at the seams. Separate dial plans, so extension ranges clash. Billing from more than one supplier. A different vendor to call depending on which site has the fault. A phone system that knows nothing about Teams chat, meetings, or presence, so a customer call and the conversation about that customer sit in different tools. No single call-recording or analytics view. And any ISDN tails still on copper are on borrowed time, because the network they depend on is being switched off.
What consolidating onto Teams Voice adds
The headline is simple: calls live where chat and meetings already do, and everything else follows. One dial plan across every site, designed once. Presence and call forwarding tied to a person’s Microsoft 365 identity rather than a desk handset, so a rep at the Gold Coast site is reachable on the same number at the desk, in a meeting room, or driving between branches. A softphone that travels with the person. One platform Metwide supports alongside your connectivity and security, instead of three suppliers pointing at each other. Per-site call routing and per-site reporting in one place. And, where compliance requires it, Teams compliance-recording integration with a certified recording solution, with storage, retention, and call-notice handling set by the policy you choose rather than left to a portal nobody can find the login for.
Want a second opinion on your current phone system? Talk to a Metwide engineer.
The PSTN switchover, number porting, and emergency calls
This is not manufactured urgency. The ISDN sunset has worked through most Australian sites, and the broader PSTN switchover is well advanced, though timing varies by exchange and by service. If you still have ISDN or PSTN copper services in a disconnection path, the decision is forced: those services are being retired and something has to replace them, and Teams Voice is one PSTN replacement that businesses moving off legacy lines consider. If you are already on a hosted PBX or NBN VoIP, nothing is being switched off under you, and the question is whether consolidation earns its keep against the contract you already pay for.
Two operational items come up on every voice migration. Number porting, sometimes called local number portability, moves your existing business numbers across through the chosen model’s operator; it usually completes within standard industry lead times, but can run long if the losing carrier disputes or the records do not match, so plan a porting window with a documented fallback rather than a same-day cutover. Emergency calls are the other: a call to 000 from Teams Voice depends on emergency-calling configuration and a current site address held against the user or device, so the call can be routed and the registered location made available to the operator, which is more involved for a laptop softphone that moves between sites. For people on the move, a 000 call from a mobile is usually the faster and more accurate path than the Teams desktop or laptop app, so e000 from Teams Voice tends to be the desk-bound fallback rather than the primary route. The Australian Communications and Media Authority, or ACMA, sets the framework, and unresolved complaints reach the Telecommunications Industry Ombudsman, or TIO; confirm during the project what location is passed for each user and device, and who keeps it current, rather than treating it as an afterthought.
Licensing and the rest of the Microsoft 365 stack
On licensing, the user needs a Teams Phone capability on their licence, usually the Teams Phone Standard add-on on top of their Microsoft 365 plan or included with an E5, plus a separate path to the public phone network through a calling plan, Operator Connect, or Direct Routing. In practice, Metwide deploys Teams Phone alongside Microsoft 365 Business Premium, E3, or E5; the SKU mix is confirmed during scoping. The exact bundle varies by tenant and Microsoft updates its licensing periodically, so treat any specific SKU as something to confirm at the time. The Microsoft Teams Phone licence in Australia is sold the same way as elsewhere; what changes is the PSTN connection underneath it.
The payoff for staying inside Microsoft 365 is the integration: voicemail in Exchange and in email, recorded calls governed by your chosen recording policy, Teams meetings, SharePoint, and Power Automate workflows to build on. If Microsoft 365 is already the standard for the people who answer and manage calls, and for many businesses it is, adding voice is a smaller step than standing up a separate phone platform and wiring it back in. This is also where Metwide’s managed IT services and the voice side meet: the licensing, the tenant configuration, and the phone system stop being two separate conversations.
Legacy phone system vs consolidated Teams Voice: side by side
| Capability | Legacy PBX or basic VoIP | Consolidated Microsoft Teams Voice |
|---|---|---|
| Dial plan across sites | Often one per site | One plan, designed once |
| Where calls live | Separate handset or app | Same app as chat and meetings |
| Reaching a person between sites | Tied to a desk number | Follows the person on laptop or mobile |
| Suppliers to manage | Often one per site or service | Usually one, alongside connectivity and IT |
| Call recording and analytics | Per system, where available | Via Teams compliance-recording integration |
| Multi-site reporting | Manual, per site | Per-site reporting in one place |
| Microsoft 365 integration | Usually none | Voicemail to email, meetings, workflows |
| ISDN or PSTN exposure | Legacy tails on borrowed time | Not dependent on switched-off services |
One-line verdict. A single, well-run hosted PBX already does some of what the right column lists; the contrast that matters is with a phone estate that grew site by site. If every site has clean call quality and a contract with time left, there is no rush. If you are juggling suppliers, dial plans, and an ISDN tail, or Microsoft 365 is already the standard across the business, consolidation is usually easier to justify, through less admin, clearer supplier accountability, and one number to call.
Teams Voice is also only as good as the connectivity underneath it: call quality depends on a business-grade link with sensible quality-of-service handling, which in 2026 usually means business NBN, fibre, or Enterprise Ethernet rather than a consumer plan.
How to decide: keep, consolidate, or replace
A multi-site phone system is almost always something a business inherited rather than scoped from scratch, so the decision comes down to keep, consolidate, or replace. Six questions get you most of the way there.
- Where is your current PBX contract in its life? Two years left with a vendor still supporting the platform is very different from an on-premise PBX the manufacturer stopped updating years ago.
- Do you already run Microsoft 365 across the business? If most staff are already there, the gap to add voice is small and the case is stronger.
- What do you need from multi-site call routing? Shared dial plans, after-hours routing between sites, presence visible to a receptionist across locations: the more you need, the less a per-site phone estate serves you.
- Do you have call-recording or retention obligations? Regulated work often requires recorded calls and defined retention, which favours a governed recording model over a patchwork.
- How much number-porting risk and lead time are you carrying? Older number ranges, multiple carriers, and a hard cutover date all argue for planning the port early with a fallback.
- Who owns emergency calling and site addresses afterwards? Someone has to keep the e000 site data current; decide who before the project.
The answer usually falls out. Keep if the contract has time left, call quality is fine, and the multi-site pain is annoyance more than cost. Consolidate if the case is there but the timing is set by a contract or a site schedule, moving site by site. Replace if the PBX is end-of-life, the contract is rolling off, an ISDN tail is on the clock, or Microsoft 365 is already the standard across the business.
Teams Voice for Brisbane and Gold Coast multi-site businesses
A professional services firm with offices in Brisbane CBD, Southport, and Robina. Microsoft 365 already deployed firm-wide, a hosted-PBX contract up for renewal. Consolidating means one dial plan across the three offices, a softphone for staff who split their week between sites, voicemail in their inbox, and call recording governed by the policy the firm chooses. The renewal date sets the timing; the migration is planned around the porting window, with a documented fallback for the main line.
A retail or hospitality operator with five to eight sites and a mixed phone estate. A small head-office IT lead who also looks after the point-of-sale gear, the WiFi, and the tills, and a phone setup that grew one site at a time. Here the win is less about Teams chat and more about stopping the bleed: one supplier instead of several, one view of what each site runs, presence so head office can tell whether the Broadbeach store is on a call, and a rollout that goes site by site. Teams Voice for a Brisbane head office that ties the outer sites together is the practical version of “one platform”. Most multi-site businesses across South East Queensland land somewhere between those two once they stop running each site as its own phone island.
What drives cost and scope
Beyond the keep, consolidate, or replace call, three things shape the project. Site count and licensing scope: how many users across how many sites, and how much Microsoft 365 licensing they already hold, usually the largest line and often partly paid for already. Which deployment model fits: Microsoft Calling Plans, Operator Connect, and Direct Routing carry different setup effort and different ongoing profiles, and the right one depends on your number ranges, your routing needs, and how much you want managed for you. Migration window and porting complexity: older number blocks, multiple losing carriers, and a tight cutover date all add effort and risk, and they are better scoped up front than discovered mid-migration.
What a Metwide Teams Voice consultation looks like
A Metwide voice and connectivity engineer starts with what you have: the current phone system or systems, the contracts and their dates, the Microsoft 365 licensing in place, the connectivity at each site, and what is and is not working across locations. From there you get a written view: which deployment model fits, the licensing picture, how number porting and the migration window would be handled, how emergency calling and site addresses would be set up, and a recommended order if a staged rollout makes sense. Metwide most often deploys Teams Voice through Direct Routing, with SBC fabric in Sydney and Queensland data centre presence, though Operator Connect and Microsoft Calling Plans are scoped where they fit a particular customer better. You also get an honest read on whether now is the time at all; if the answer for a site is to renew the current contract and revisit in a year, we will say so. From there you decide what to do next, on your timeline. The broader voice and video services page has more on where Teams Voice sits alongside the rest of the stack.