TEAMS + TIER 1 TELEPHONY
Microsoft Teams Phone Integration for Enterprise
Bring Tier 1 calling into Microsoft Teams while preserving enterprise call routing, numbers, queues, support, reporting, and provider flexibility.
There Is More Than One Way to Add Calling to Teams
Microsoft Teams can become a primary user interface for business calling without forcing every organization into the same carrier or architecture. The correct model depends on how native the experience must be, which PBX capabilities must remain authoritative, licensing, endpoint strategy, emergency calling, support ownership, and rollout risk.
Bringing a qualified PSTN provider to Teams can support cost control, customized call handling, established support and SLA relationships, traffic optimization, continuity during migration, and tailored billing and reporting. Those benefits are real, but the implementation model determines which Microsoft licenses and technical components are required.
Embedded Calling App
A Tier 1 calling experience runs inside Teams. It requires an existing Microsoft Teams entitlement and a Tier 1 seat, but not a separate Teams Phone add-on.
Native Teams Dial Pad
A PBX Connector/Direct Routing design uses the native Teams calling experience. It requires Microsoft Teams and Teams Phone licensing plus the Tier 1 service; a Microsoft Calling Plan is not required.
Preserved PBX Control
Tier 1 can remain authoritative for phone numbers, call flows, queues, voicemail, recording, routing, and support while Teams becomes an endpoint.
Choose the User Experience First
The embedded Calling App is often the practical choice when users want to place and receive Tier 1 calls without leaving Teams and the organization wants to avoid an additional Teams Phone license. It is an app-style experience inside Teams rather than the native Microsoft Calls dial pad.
The PBX Connector is appropriate when the native Teams dial pad and deeper Teams Phone experience are requirements. It uses a Direct Routing-style architecture and therefore requires Teams Phone licensing. Document the expected interface before pricing either model.
Decision questions
- Embedded app or native dial pad?
- Existing Teams licensing?
- Teams Phone licenses owned?
- Desk phones still required?
- Which PBX features must remain?
Provider value
- Existing numbers and contracts
- Customized routing and features
- Defined SLA and support path
- Billing and usage reporting
- Phased migration options
Keep the Provider and Calling Features That Fit
Bringing a provider to Teams can preserve existing numbers, negotiated services, support relationships, routing logic, call queues, recording, voicemail, reporting, and specialized integrations. It can also support a phased transition instead of replacing every workflow on day one.
Microsoft documents four broad PSTN connectivity models—Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing. The Tier 1 design should be compared against the organization’s technical, licensing, geographic, compliance, and support requirements. See Microsoft’s current PSTN connectivity guidance.
Plan Identity, Network, E911 and Support Together
A Teams calling project crosses Microsoft 365 administration, telephony, networking, security, emergency calling, endpoint management, and user support. Assign ownership for tenant permissions, licenses, user synchronization, number assignment, caller ID, policies, location management, and troubleshooting.
Validate audio quality from real office, home, mobile, VPN, and wireless scenarios. The application may be Teams, but the caller still depends on endpoint performance, network paths, PSTN connectivity, call routing, and accurate E911 information.
Shared workstreams
- Microsoft tenant and identity
- Tier 1 user and number mapping
- Network and media readiness
- E911 and location policy
- Tiered support ownership
Pilot evidence
- Sign-in and provisioning
- Inbound and outbound PSTN
- Transfer and queue behavior
- Voicemail and recording
- E911 and failover tests
Roll Out by Persona and Workflow
Not every user needs the same endpoint. Knowledge workers may prefer Teams, reception and contact-center staff may need dedicated controls, common areas may use desk phones, and executives or field teams may require multiple devices. A mixed-endpoint design is often more effective than a forced replacement.
Pilot with representative personas, validate inbound and outbound calls, transfer behavior, caller ID, voicemail, queues, E911, recording, presence expectations, mobile behavior, and support escalation before expanding.
What Direct Routing Onboarding Actually Involves
The connection is provider-assisted, but Microsoft tenant readiness still matters. Tier 1 creates the enterprise onboarding invitation and coordinates the telephony-side setup. The customer’s Microsoft Global Administrator completes the tenant-side Microsoft SSO and consent steps and supports domain, license, policy, and user-readiness tasks. Administrative credentials should remain with the customer and should not be shared with Tier 1.
Typical connection sequence
- Confirm tenant and domain health. The selected Microsoft domain must be verified, healthy, and ready for Teams voice services.
- Reserve an onboarding license. At least one eligible, available and unassigned user license containing Phone System—or a comparable Teams Phone add-on—is needed for the initial Direct Routing setup.
- Authorize the connection. Tier 1 sends the enterprise invitation to the customer’s Microsoft Global Administrator. That administrator signs in through Microsoft SSO, completes the required tenant authorization, and selects the appropriate domain during the connection workflow. The enterprise administrator identity can use the organization’s verified primary domain; it does not have to use an onmicrosoft.com address.
- Monitor provisioning. The initial connection normally progresses within a few minutes. Status and email notifications indicate when the telephony-side connection is complete.
- Configure the PBX and users. Tier 1 completes provider-side work, then maps users, numbers, policies, call flows, E911, and pilot scenarios.
Microsoft and provider interfaces change over time, so Tier 1 validates the current workflow during project discovery instead of relying on screenshots from an older setup guide.
Direct Routing Licensing: Two Ways to Qualify
Direct Routing connects Microsoft Teams to the public telephone network through Tier 1 instead of a Microsoft Calling Plan. Each person using the native Teams dial pad still needs Microsoft Teams and the Phone System capability now sold as Teams Phone. There are two common ways to meet that requirement:
1. Inclusive Microsoft License
The assigned Microsoft license already includes Teams Phone/Phone System. Examples may include qualifying Microsoft 365 E5, Office 365 E5, A5, and certain government G5 plans. No separate Teams Phone add-on is needed when the required capability is already present.
2. Base License + Teams Phone Add-On
A qualifying base plan—such as many E3, Business, F-series, A3, or government G3 plans—is combined with the appropriate Microsoft Teams Phone add-on. The result supplies the same Phone System capability required for native Direct Routing.
What Tier 1 Verifies During Setup
The Direct Routing onboarding process checks the user’s assigned Microsoft service plans for an eligible Phone System capability. If Microsoft introduces a compatible license that is not yet shown in an older reference list, the eligibility check can identify it and the supported-license list can be updated.
Do not substitute a Virtual User license for an individual user’s Teams Phone license. Resource-account, common-area, and meeting-room licensing should be matched to the intended account and device type rather than assigned as a workaround for a person.
Microsoft product names and bundles change. Confirm current eligibility in the customer’s Microsoft tenant during discovery instead of relying only on a static SKU list.
Quick Licensing Recap
- Inclusive license: proceed with Direct Routing setup.
- Non-inclusive license: add Teams Phone first.
- Tier 1 supplies PSTN service; no Microsoft Calling Plan is required.
- Embedded Calling App: separate model that does not require the Teams Phone add-on.
- Validate actual assigned licenses before rollout.
Teams Calling Evaluation Checklist
Get the interface, licenses, PBX authority and support boundaries in writing.
- Choose embedded Calling App versus native Teams dial pad.
- Inventory existing Microsoft Teams and Teams Phone licenses.
- Identify numbers, users, queues, voicemail and recording requirements.
- Define whether Tier 1 or Microsoft is authoritative for each function.
- Map E911, caller ID, identity and user-provisioning responsibilities.
- Test office, remote, mobile, VPN and wireless call quality.
- Pilot representative users and mixed endpoint types.
- Document Microsoft, Tier 1 and customer support ownership.
Continue Planning Your Enterprise Phone System
Frequently Asked Questions
Can Tier 1 calling work inside Microsoft Teams?
Yes. Tier 1 can provide an embedded calling-app experience inside Teams or a native Teams Phone experience through the PBX Connector, depending on requirements and licensing.
Does Tier 1 Teams integration require a Microsoft Teams Phone license?
The embedded Calling App requires an existing Microsoft Teams entitlement and a Tier 1 seat, but not the separate Teams Phone add-on. The native PBX Connector/Direct Routing option does require Teams Phone licensing.
Do we need a Microsoft Calling Plan?
Not when Tier 1 supplies the PSTN service. For a native Direct Routing design, users still need the appropriate Teams Phone licensing even though the calling service and numbers come from Tier 1.
Can we keep our existing numbers and call flows?
Usually, yes. Number portability and technical eligibility must be confirmed, and existing call flows should be documented and tested as part of the migration.
Does every employee need to use Teams as the phone?
No. An enterprise design can mix Teams users, desk phones, mobile apps, common-area devices, conference rooms, and contact-center endpoints according to each role.
Choose the Right Teams Calling Model
Tier 1 can compare the embedded Calling App and native PBX Connector, map licensing, preserve the right PBX workflows, and plan a controlled pilot. Call (866) 808-4371.