Managed Microsoft Teams Phone Service
Managed Microsoft Teams Phone Service is monthly voice operations for a Teams Phone deployment that is already live: IT Partner handles moves, adds, changes, and deletes for users, numbers, call queues, and auto attendants; monitors call quality through Microsoft's Call Quality Dashboard and triages issues; liaises with your carrier or Operator Connect provider; keeps emergency (E911) addresses and dynamic emergency-calling locations current; and delivers a monthly usage report. It costs $4 per Teams Phone-licensed user per month, month to month with no long-term contract. Initial setup, PBX migrations, and contact-center builds are separate projects; PSTN carrier charges and Microsoft licenses are billed by the carrier and Microsoft, never through this fee.
What this engagement is
A phone system fails quietly and then all at once. The new hire cannot make outbound calls because nobody assigned a number. The main auto attendant still announces last year's holiday hours. A call queue rings to two people who left in March. Someone in the warehouse dials 911 from a Teams handset and the address that goes out is the head office, forty miles away. A remote user complains about choppy audio for three weeks before anyone opens the Call Quality Dashboard. Teams Phone is a dependable platform, but it is an operations platform, and after the setup project ends most organizations discover they have a voice system and no voice administrator. This service is that administrator. Each month IT Partner runs the whole operating rhythm. Moves, adds, changes, and deletes: numbers assigned and reclaimed, Teams Phone and calling licenses applied, calling and voicemail policies set, call queue agents and auto attendant greetings, schedules, holidays, and menus updated on an agreed intake, and common-area and desk phones signed in — all inside a clearly defined monthly allowance. Call quality: we watch the Call Quality Dashboard and per-user call analytics for the patterns that predict complaints — packet loss on a subnet, a bad wireless segment, a media-bypass or device driver problem — and triage the issues your users report with a diagnosis your network team can act on. Carrier liaison: for Calling Plan, Operator Connect, and Direct Routing estates we work the number ports, orders, and tickets with Microsoft, your operator, or your SBC vendor so you are not the go-between. Emergency calling: we keep validated emergency addresses and places current, maintain the network-to-location mapping that makes dynamic emergency calling work for existing sites, and keep the emergency calling policies and security-desk notifications that United States Kari's Law and RAY BAUM's Act obligations turn on. Reporting: a monthly usage report — call volumes, queue performance and abandonment, auto attendant paths, license-to-usage fit, quality trends, and the changes we made. The boundary is priced honestly. The per-user fee operates the estate you have. Standing up Teams Phone, migrating off another PBX, building a contact center, deploying a Session Border Controller, or opening a whole new office are projects, named as such and quoted in writing before anything starts. PSTN minutes, Calling Plans, and Microsoft licenses are billed by the carrier and Microsoft. Access is least-privilege GDAP that you approve, never standing global admin, and the service is month to month under IT Partner's published no-lock-in policy.
Success criteria
What you receive
How the work unfolds
Access is established through GDAP roles you approve — least-privilege, time-bound, never standing global admin. We inventory the voice estate end to end, verify emergency addresses and dynamic emergency-calling mappings, confirm carrier and operator contacts and Direct Routing vendors, and agree the intake channel and the named contacts who may raise changes. Anything already broken is flagged in writing and either absorbed into the first cycles or scoped as a project.
Your named contacts raise user, number, queue, and attendant changes through the intake. Routine per-user work is completed inside the fee; first response follows IT Partner's published SLA of 1 business hour. Requests beyond the monthly counts — or a whole new office, a bulk port, a redesigned call-flow tree — are identified at intake and quoted in writing before they start.
We review the Call Quality Dashboard and per-user analytics monthly and triage reported issues as they arrive: what the data says, whether the cause is client, device, network, or carrier, and what to change. Tenant-side fixes are applied; network or carrier fixes are handed over as a precise diagnosis and tracked to closure.
Number orders, ports, operator assignments, and trunk tickets are worked with Microsoft, your operator, or your SBC vendor. Emergency addresses and mappings are updated as sites change, and a quarterly verification confirms the emergency-calling posture and records it in the report.
The monthly usage report closes the cycle: volumes, queue and attendant performance, license fit, quality trends, and changes made. Quarterly, we step back with a short roadmap — features worth adopting, licenses worth reclaiming, and honest routing to the right project service where the monthly scope ends.
Prerequisites
Who does what
IT Partner
- Document the baseline and run the monthly moves, adds, changes, and deletes within the published response SLA.
- Monitor call quality, triage reported issues, and apply tenant-side fixes.
- Work number, port, operator, and trunk tickets with Microsoft, carriers, and SBC vendors on your behalf.
- Keep emergency addresses, places, mappings, policies, and notifications current and verify them quarterly.
- Deliver the monthly usage report and quarterly recommendations.
- Track Microsoft's Teams Phone changes that affect the tenant and flag them ahead of time.
- Name honestly, and quote in writing, any request that exceeds the monthly scope.
Your team
- Maintain Teams Phone, Calling Plan, and resource-account licensing, and pay carrier and PSTN charges directly.
- Approve the GDAP access request and keep named contacts for the intake.
- Tell us about joiners, leavers, office moves, and new sites early enough to plan — emergency-calling changes in particular.
- Own the network: apply the fixes our call-quality diagnosis identifies, or engage your network vendor to do so.
- Handle first-line end-user support, or subscribe to IT Partner's Remote Support Help Desk Service for it.
- Review the monthly report and decide on recommendations that require project work.
What's not included
Limitations & technical notes
Frequently asked questions
What is the Managed Microsoft Teams Phone Service?
It is a recurring monthly service in which IT Partner operates your existing Teams Phone deployment: moves, adds, changes, and deletes for users, numbers, call queues, and auto attendants; call-quality monitoring and triage; carrier and Operator Connect liaison; emergency (E911) address and location upkeep; and a monthly usage report. It costs $4 per Teams Phone-licensed user per month with no long-term commitment.
Who is this service for?
Organizations that completed a Teams Phone setup or a migration from RingCentral, 8x8, Zoom Phone, or a legacy PBX — with us or with anyone — and have no voice administrator afterward. If new hires wait days for a number, an auto attendant still announces last year's hours, or nobody has looked at call quality since go-live, this service is the missing role.
How does the per-user billing work?
The monthly bill is $4 for each Teams Phone-licensed user in scope that month — resource accounts for queues and attendants and common-area phones are not counted as users. Joiners and leavers are normal and handled through the intake; a material change in headcount is re-baselined by agreement so the bill always tracks reality.
What exactly is included each month, and where does a project begin?
Routine per-user moves, adds, changes, and deletes are included without a cap — numbers, licenses, policies, voicemail, queue membership, and changes to greetings, schedules, holidays, and menus on your existing queues and attendants. Each month also includes up to 2 new call queues or auto attendants, up to 2 new emergency locations with their dynamic emergency-calling entries, and up to 5 individual number ports or acquisitions. A project begins where those counts end, or with any change touching more than 10 users at once: a new office, a bulk port, a redesigned call-flow tree, a Session Border Controller change. We name the difference at intake and quote projects in writing before they start.
How is this different from Microsoft Teams Administrator on Demand?
Layer. Teams Administrator on Demand covers general Teams administration — meeting and messaging policies, external access, apps, and teams lifecycle — on an on-demand basis. This service is voice operations: numbers, queues, attendants, call quality, carriers, and emergency calling, run as a monthly rhythm with monitoring and a report. Many organizations use both; neither pretends to be the other.
Which PSTN connectivity models do you support?
All three Microsoft models: Microsoft Calling Plans, Operator Connect, and Direct Routing, including mixed estates. With Calling Plans we work orders and ports with Microsoft; with Operator Connect we manage assignments and tickets with your operator; with Direct Routing we work trunk issues with your SBC vendor or carrier. What we do not do is operate the Session Border Controller itself — that engineering is separate.
What do you do about call quality?
Monthly, we review Microsoft's Call Quality Dashboard and per-user call analytics for trends by site, subnet, and device — packet loss, jitter, and round-trip time patterns that predict complaints. When a user reports a problem, we triage it against that data and give you a written diagnosis: client, device, network, or carrier, and what to change. Tenant-side causes we fix; network causes go to your team or vendor with the evidence; carrier causes we raise and chase.
How do you handle emergency (E911) calling?
We keep your validated emergency addresses and places current, maintain the network-to-location mappings — subnets, wireless access points, switches, and ports — that let Teams send a dispatchable location automatically for existing sites, and keep the emergency calling policies and security-desk notifications in place. Every quarter we verify the posture and record it in the report. New sites are added inside the monthly allowance up to 2 per month. Whether Kari's Law, RAY BAUM's Act, or rules outside the United States apply to you is a question for your counsel; we implement and verify the configuration.
Do we still need our carrier's support?
You keep the commercial relationship and the bills; we do the talking. Number orders, ports, Operator Connect assignments, and trunk tickets are raised and chased by us, with you kept informed rather than in the middle. Carrier and Microsoft timelines are theirs, not ours — we work them daily and report status honestly.
Can staff manage their own call queues and auto attendants?
Yes, and we recommend it for greetings, holidays, and queue membership. Microsoft lets designated authorized users change those settings without an admin role — from Teams itself, and with the Queues app where licensed. We set up the voice-applications policies, assign the authorized users, and keep the structural configuration under our control, so an office manager can update a holiday greeting on Friday afternoon without waiting for a ticket.
What is in the monthly usage report?
Inbound and outbound call volumes, call queue performance and abandonment rates, auto attendant menu paths, licenses assigned versus actually used with reclaim candidates, quality trends by site, the emergency-calling verification status for the quarter, and every change made in the month. It is written for an office manager or IT lead to act on without translation.
We built our Teams Phone with someone else. Can you take it on?
Yes. Onboarding starts with a health review of the estate — users, numbers, queues, attendants, emergency addresses, and PSTN connectivity. Healthy configuration enrolls straight into steady-state care. Pre-existing faults — unvalidated emergency addresses, orphaned resource accounts, queues ringing to departed staff — are flagged in writing and either absorbed into the first cycles or, if structural, scoped as a project so the service starts from a known-good baseline.
How fast do you respond to requests?
First response within 1 business hour — IT Partner's published support SLA. We publish our monthly support statistics for every month since December 2023, including the months we missed, so you can verify the record instead of trusting the sentence.
What access do you need to our tenant?
Least-privilege GDAP that you approve — Microsoft's granular, time-bound partner access model. Our default request is Microsoft's standard starter relationship; anything more is requested per task and expires. We never ask for standing Global Administrator, and our default access policy is published for you to compare against what we actually request.
How does billing work, and can we stop?
Monthly, at $4 per Teams Phone-licensed user in scope, with no long-term contract: stop any month, and all we ask is payment of previously approved invoices. No lock-in in either direction is a published IT Partner term, not a promotional line — it is also why the monthly report has to keep earning the renewal.