All insights

Teams Phone Standard or Teams Phone with Calling Plan: what is the difference?

5 min readBy Brendon Whiting, Founder · 13 March 2026

Teams Phone Standard is the phone system on its own: it turns Teams into a PBX with numbers, queues, transfers and voicemail, and you supply the call carriage from a carrier of your choosing. Teams Phone with Calling Plan bundles Microsoft's own carriage. For most Australian businesses, Standard plus a local carrier works out better.

The distinction confuses people because in most other phone products the system and the calls arrive together. Microsoft separates them, and once you see why, the choice becomes straightforward. The phone system is software: the intelligence that rings the right person, holds the queue, takes the message. Call carriage is the connection to the public telephone network that actually delivers a call to a mobile in Adelaide. Microsoft will sell you both or just the first.

Bringing your own carriage is done through what Microsoft calls Direct Routing, where your provider connects SIP trunks from an Australian carrier to your Teams tenant. This is the arrangement most Australian businesses end up in, for three reasons. Local carriers price Australian calling competitively for local conditions. You keep a relationship with a telco who can be held accountable for line quality. And your existing numbers usually stay where they are and simply point at Teams, which removes the most fragile part of a migration.

Microsoft's own calling plan has its own appeal, and it is not the wrong answer for everyone. One vendor, one bill, one support path, and setup that is genuinely simpler because there is no session border controller and no carrier relationship to manage. For a small business that values simplicity above optimising the call spend, that is a defensible trade, particularly if call volumes are low enough that carriage cost barely registers.

Where the decision gets made in practice is usually call volume and existing arrangements. A business making heavy use of the phone will find carriage cost material enough to justify Direct Routing. A business making a handful of calls a day will find the difference trivial and should optimise for simplicity instead. And a business already holding numbers with a carrier it is happy with has a strong reason to keep that relationship rather than porting everything to Microsoft.

One thing to be clear about regardless: Teams Phone is an add-on, not something included with your Microsoft 365 plan, however senior that plan is. Being able to hold a Teams meeting is not the same as having a phone number that a customer can ring, and the assumption that Business Premium covers telephony is a common and expensive misunderstanding at budget time.

Audio quality is worth a sentence because it is the thing users judge everything by. Teams calls run over your internet connection like everything else, so voice traffic needs prioritising on the network and the connection needs enough headroom at the busiest time of day. Businesses that skip this spend months blaming Teams for a saturated link, and the fix is network configuration rather than a different phone platform.

The setup work also differs and is worth knowing before you choose. A calling plan is largely a licensing and number exercise. Direct Routing involves a session border controller, carrier configuration and routing rules, which is more engineering and normally handled by your provider rather than by you. Both end in the same place for the user, who simply has a phone number in Teams, and neither should be attempted piecemeal, since half-configured routing produces calls that work in one direction only.

One licensing subtlety is worth confirming before budgeting, because it changes the arithmetic on both paths: shared devices and common-area phones, the handset in a reception area or a warehouse, are licensed differently from a named user. Businesses with several communal phones sometimes assume each needs a full user licence and over-budget significantly. Ask your provider to price the communal handsets separately from the people.

The honest caveat is that Teams telephony is competent rather than exceptional, and if your business runs a busy reception desk or a genuine contact centre, a dedicated phone system will handle call flow better regardless of which carriage model you pick. Teams Phone shines where calls are a normal part of work rather than the work itself. If you want the right combination set up against your actual call patterns, call 1800 456 567.

Work out which combination fits

We set up Teams Phone with the carriage arrangement that suits your call patterns, whether that is a Microsoft plan or your own SIP trunks.

Frequently asked questions

It is the arrangement that lets Teams Phone use a carrier of your choosing rather than Microsoft's calling plan, connecting your SIP trunks to Teams through a session border controller your provider manages. For Australian businesses it is usually the better-value path, and it is the reason Teams Phone Standard exists as a separate product.

Yes, through porting, and the route differs by arrangement. With Direct Routing your numbers stay with your carrier and simply point at Teams, which is generally the simpler path. With a Microsoft calling plan the numbers port to Microsoft, which works and is a more involved process worth starting early.

No. Teams Phone is a separate add-on regardless of which Microsoft 365 plan you hold, and the ability to run meetings in Teams is not the same as the ability to make and receive calls on a normal phone number. Budget for it separately rather than assuming the higher plan covers it.

Questions? Let's talk.

Call 1800 456 567 or fill out the form.

  • 30-minute discovery — no jargon, no pressure
  • Plain-English Essential Eight Cyber Security Scorecard
  • A clear plan tailored to your business

Prefer to talk?

Call 1800 456 567

Powered by Calendly — your data is handled securely.

Our office · Level 2, 25 Grenfell Street, Adelaide

By submitting, you agree to our terms and privacy policy. No spam — ever.