Skip to content

Teams Phone: fix KYC timing, network, and device pitfalls for admins

Home
IT Services Blog
Teams Phone: fix KYC timing, network, and device pitfalls for admins

Teams Phone: fix KYC timing, network, and device pitfalls for admins

Isometric illustration of phone rollout obstacles

To enable Teams Phone across your organisation, assign Teams Phone licences, choose a PSTN connectivity option, obtain and assign numbers, configure emergency locations, deploy devices and policies, then verify calling end to end. Work through that sequence in the Teams admin centre and PowerShell in order, since skipping ahead usually backfires. The biggest scheduling risk isn’t technical at all: it’s KYC and number procurement, which can stall a launch date by weeks if left until the last minute.

TL;DR:

  • Choosing the correct PSTN connectivity option depends on your control needs, existing carrier contracts, and geographic calling requirements, with options including Calling Plans, Operator Connect, Teams Phone Mobile, and Direct Routing.
  • Number procurement and porting often cause delays and should be initiated early, with immediate KYC verification and prompt submission of port requests to avoid schedule slips.
  • Every voice user requires an emergency location, and thorough testing of emergency call routing and notifications is critical to ensure compliance and accuracy.
  • Device deployment fails mainly due to network issues such as unsupported proxies, improper QoS, or firmware problems, making network readiness checks essential before rollout.
  • Engaging a managed-services partner can greatly reduce project risks by coordinating licensing, cabling, device provisioning, and ongoing monitoring, helping ensure a predictable Teams Phone deployment.
Lancast
Plan A More Reliable Teams Phone Rollout
Lancast provides proactive IT infrastructure, managed services, security monitoring, and strategic consultancy for organisations navigating complex technology projects.

Talk to Lancast

Table of Contents

Prerequisites and licensing checklist for Teams Phone setup

Before touching phone numbers or hardware, get the licensing right. Teams Phone runs on top of Microsoft 365, and the Phone System entitlement is entirely separate from PSTN connectivity. That distinction trips up a lot of first-time deployments: you can enable internal Teams calling without ever giving users the ability to dial an external number.

Each voice user needs a Teams Phone licence, and if Microsoft is supplying the PSTN connection rather than a carrier, a Calling Plan licence on top of that, as Microsoft’s own add-on licensing guidance sets out. Voice-enabling itself happens in the Teams admin centre under Users, or in bulk through PowerShell using Set-CsPhoneNumberAssignment.

Before you provision anything, confirm:

  • A verified custom domain exists in your Microsoft 365 tenant
  • The right admin roles are assigned (Teams Administrator at minimum, Global Administrator for tenant-wide changes)
  • The tenant’s KYC page is completed if you’re using Calling Plans
  • Existing Microsoft 365 licences (E3, E5, or Business Premium plus the Teams Phone add-on) are confirmed for every voice user

Get this groundwork wrong and every later step, from number assignment to device sign-in, inherits the problem.

Which PSTN connectivity option should you choose?

Four models exist, and picking the wrong one for your organisation’s shape is the single most common source of regret six months into a rollout.

Microsoft Calling Plans bundle PSTN minutes directly into your Microsoft 365 tenant. It suits organisations that want the simplest possible administration and don’t have an existing carrier relationship worth preserving. Operator Connect lets you keep a local carrier while Microsoft handles the technical integration, a good middle ground for businesses with established telecom contracts. Teams Phone Mobile turns mobile numbers into first-class Teams endpoints, useful for field staff who already carry a work mobile. Direct Routing gives you full control by connecting your own Session Border Controller (SBC) to Teams, the option of choice for larger enterprises or anyone with complex existing telephony infrastructure they can’t walk away from.

Run through this checklist before deciding:

  • Do you need granular control over routing and carrier selection, or is simplicity worth more than control?
  • Does an existing carrier contract have penalty clauses for early exit?
  • Do your users need international calling coverage a Calling Plan doesn’t reach?
  • Will regulatory or KYC requirements slow down number procurement in your market?

Nothing stops you running a hybrid model, either. Head office on Direct Routing through an existing SBC, satellite offices on Calling Plans, mobile-first staff on Teams Phone Mobile. Mixed estates are common, not exotic.

Pro Tip: If you’re already committed to Direct Routing, get your SBC’s FQDN validated against your verified tenant domain and its certificates issued well before number porting starts. Certificate delays are a quieter but equally common cause of slipped go-live dates.

How do you get and assign phone numbers?

Number acquisition is where most schedule slippage actually happens, and it’s rarely a technical failure. It’s paperwork.

  1. Order numbers through the Teams admin centre under Voice > Phone numbers, or raise a phone number support request for volumes the self-service flow can’t handle.
  2. Start Know Your Customer (KYC) verification immediately if you’re using Calling Plans. Microsoft says most KYC reviews complete within three business days, but any “Action Required” status can delay both new number acquisition and porting from your existing carrier.
  3. Port existing numbers early. Porting timelines depend on your outgoing carrier as much as Microsoft, so submit port requests as soon as KYC clears rather than waiting for devices to arrive.
  4. Assign numbers to users and resource accounts by editing an unassigned number in the Teams admin centre, as detailed in Microsoft’s guidance on managing phone number usage, or automate bulk assignment with Set-CsPhoneNumberAssignment in PowerShell.

If you’re voice-enabling more than a handful of users, script the assignment step. Manual clicking through the admin centre for fifty or a hundred accounts invites mistakes.

How do you configure and test emergency calling?

Every PSTN-enabled user needs an assigned emergency location, no exceptions, regardless of which connectivity model you’ve chosen. This isn’t a nice-to-have compliance checkbox: if someone dials an emergency number from a Teams client, the system needs to know where they physically are.

Geometric emergency-location assignment process

Emergency calling policies in the Teams admin centre control two things: whether remote or hybrid staff can set their own address, and how your internal security desk gets notified when an emergency call goes out. Microsoft’s emergency calling policy documentation describes notification modes ranging from a simple chat alert to a security team joining the call unmuted. Direct Routing deployments need this configured at the SBC and gateway level too, not just in Teams.

Before go-live, run through this test checklist:

  • Assign emergency locations to a representative sample of users across every site
  • Perform supervised test calls during a low-risk window, ideally coordinated with your local emergency services in advance
  • Confirm routing reaches the correct Public Safety Answering Point (PSAP) for each site’s registered address
  • Verify the security desk notification actually fires and displays the right caller location

Pro Tip: Location accuracy matters more than the policy configuration itself. A perfectly configured emergency policy pointing at the wrong building address is worse than no policy at all, because it gives false confidence.

Setting up auto attendants and call queues quickly

An auto attendant is your automated front door: it greets callers and routes them by menu choice, business hours, or holiday schedule, with support from AI voice agents that answer the phone to enhance call handling efficiency. A call queue is what happens after that greeting, distributing live calls to a group of agents. Most organisations need both working together, not one instead of the other.

  1. Create a resource account for each auto attendant and call queue in the Teams admin centre, then assign it a Teams Phone Resource Account licence.
  2. Build the auto attendant with a recorded or text-to-speech greeting, business hours, and holiday overrides, then set the default call flow to route into your call queue.
  3. Configure the call queue’s routing method. Round robin distributes calls evenly; longest idle sends calls to whoever has waited longest since their last call, which tends to feel fairer to agents.
  4. Set overflow and timeout handling so calls don’t ring indefinitely when no agent is available.
  5. Monitor queue health through call analytics once live, watching abandonment rate and average wait time as your early warning signs.

Keep the first version simple. Add languages, secondary greetings, and complex routing logic only once the basic flow is proven in production.

Device deployment and network readiness checklist

Device rollouts fail more often on network and sign-in configuration than on the phones themselves. Microsoft’s network preparation guidance recommends roughly 100 kbps up and down per Teams Phone, which sounds trivial until you multiply it across a busy call centre floor on shared wireless.

Work through this before shipping a single handset:

  • Open the required ports and confirm QoS tagging is applied consistently across switches and Wi-Fi controllers, not just the core network
  • Avoid proxy servers that require authentication. Teams Phones don’t support authenticated proxies, and this single detail causes more failed sign-ins than any other network issue
  • Decide sign-in mode per device: UserSignIn for personal desk phones, CommonAreaPhoneSignIn or the Teams Shared Devices licence for meeting rooms and shared spaces
  • Confirm certificate trust chains are current, particularly on older firmware that ships with expired root certificates
  • Check vendor provisioning notes, since OEM firmware update cadences vary and some models need a manual firmware bump before they’ll accept Teams provisioning

Lancast’s hardware and software installation service covers exactly this kind of on-site configuration work, where device sign-in issues usually surface first.

How do you monitor and verify Teams Phone after rollout

Go-live isn’t the finish line. Set calling policies and IP phone policies per user group, tightening or loosening features like call forwarding and voicemail transcription depending on role.

  • Assign calling policies that match business need, not a single blanket default across the whole tenant
  • Use the call quality dashboard and call analytics to spot patterns before they become complaints, particularly jitter and packet loss on specific sites
  • Run representative test calls across each physical location and connectivity type after any network change
  • Script bulk policy assignments and verification checks in PowerShell so the same tests run identically next time, not from memory

Treat this as an ongoing operational rhythm, not a one-off task you tick off after launch week.

What usually derails a Teams Phone rollout

Most Teams Phone projects don’t stall on the technology. They stall on timing and on the parts nobody budgeted time for: KYC left until the week numbers were meant to go live, emergency location testing skipped because “we’ll do it after launch”, Wi-Fi that was never actually tested for QoS under real call load, and common area phones that sit unprovisioned because nobody worked out the sign-in mode in advance.

A managed-services partner earns its keep by front-loading exactly those risks: coordinating KYC and number procurement against your go-live date, handling SBC and Direct Routing integration where it’s needed, and running ongoing monitoring once the project team has moved on. When scoping a partner, ask for clear SLAs and a written verification deliverable, not just a promise that “it’ll work on the day.”

— Carl

How Lancast supports a Teams Phone rollout

Lancast is the alternative to piecing a Teams Phone rollout together department by department. As an HP Amplify Partner and Microsoft Cloud Service Provider with 30 years in Irish IT infrastructure, we coordinate the parts that typically go wrong in isolation: tenant readiness and Microsoft 365 licensing, structured cabling and Wi-Fi capacity for call quality, device provisioning, and Direct Routing or SBC integration where your existing carrier relationship needs preserving.

Lancast

That coordination is what turns a multi-week rollout into a predictable one. Our proactive managed services keep monitoring in place after go-live, catching call quality issues before users report them, and our team handles the KYC-to-provisioning timeline so number procurement doesn’t quietly become your critical path. If cabling or wireless capacity is a question mark for your site, our structured cabling service closes that gap before device deployment day.

It is advisable to get in touch with a managed-services provider to scope a Teams Phone rollout plan for your organisation and a realistic go-live date.

Official documentation and resources worth bookmarking

Sources

FAQ

How do I set up Microsoft Teams Phone from scratch?

Assign Teams Phone licences to your users, choose a PSTN connectivity option (Calling Plan, Operator Connect, Teams Phone Mobile, or Direct Routing), then obtain and assign phone numbers through the Teams admin centre. Configure emergency locations for every voice user before deploying devices, then verify calling with supervised test calls.

Can I connect my existing office phone to Teams?

Not directly in most cases, since traditional desk phones use different signalling. You’ll typically need a Teams-certified IP phone, a softphone client on a computer or mobile, or a Direct Routing connection through an SBC if you want to keep existing carrier trunks feeding into Teams.

What exactly is the Microsoft Teams Phone system?

Teams Phone is Microsoft’s cloud-based telephony platform built into Teams, replacing a traditional PBX with calling, voicemail, auto attendants, and call queues delivered through Microsoft 365. It handles internal calling on its own, and reaches external phone numbers once paired with a PSTN connectivity option like a Calling Plan or Direct Routing.

How much does Teams Phone with a Calling Plan cost?

Pricing for Teams Phone licences and Calling Plan add-ons is set by Microsoft and varies by region and plan tier, so current prices are best checked directly on Microsoft’s licensing pages rather than quoted here. For help matching licence tiers to your organisation’s actual usage, Lancast’s Microsoft CSP team can walk through the options against your current tenant.

Why is KYC verification needed before I can get phone numbers?

Know Your Customer verification confirms your organisation’s identity and address before Microsoft issues or ports phone numbers under Calling Plans, a regulatory requirement rather than an optional step. Most reviews complete within three business days, but starting it early avoids it becoming the bottleneck on your go-live date.