Teams Phone can become a routed customer-service platform without replacing the Teams calling experience. This guide covers the three Microsoft-certified integration models, where Operator Connect fits, what each Luware Nimbus module actually buys, the full licensing stack, implementation work, integrations, limitations, and where a Teams-native design beats a standalone CCaaS platform or loses to one.
Written by Foretel Solutions, powered by Bridgepointe Technologies
Luware Nimbus is a strong fit when Teams Phone is already the company phone system and inbound service is the center of gravity. It preserves the Teams calling experience, uses Microsoft presence and identity, and scales from departmental routing to a formal contact center. Its modular pricing is less intuitive than a single CCaaS seat, and buyers needing predictive outbound, a deep native WEM suite, or a non-Microsoft operating model should compare it with Five9, Genesys, and NICE. We implement Nimbus through Momentum, so treat this as a disclosed recommendation, not a claim that it wins every use case.
Teams Phone is a strong business phone system. With Teams Phone you get auto attendants and call queues, so a caller can press 1 for sales and land in a small group. What you do not get is the machinery a support or sales operation runs on: skills-based and priority routing, queue callbacks, real-time wallboards, historical reporting, quality management, and channels beyond voice such as web chat, email, and social.
A contact center for Teams adds that machinery. Microsoft runs a certification program so the providers that plug in meet its quality and reliability bar, and it defines three ways they can connect. The models are not just packaging. They decide the media path, the agent experience, and which supplier systems enter your security and compliance review.
Microsoft certifies three models for connecting a contact center to Teams. The plain-English difference is where the call and its media end up.
| Model | How it connects | Where the call & media live | Native to Teams? |
|---|---|---|---|
| Connect | Certified session border controllers and Direct Routing bridge the provider's own contact center to Teams. | The call is routed out to the provider's cloud. Agents often work in a separate app next to Teams. | No. Integrated, but the call leaves Teams. |
| Extend Native | The provider uses the Microsoft Graph Cloud Communications APIs to direct calls without ever taking them over. | The call and media stay inside your Teams tenant. Agents answer in the Teams client they already use. | Yes. This is the native model. |
| Unify (Power) | The provider builds on Azure Communication Services to create a new, tightly coupled CCaaS app. | Calls run on Azure Communication Services infrastructure rather than the Teams calling stack. | Partly. Microsoft-cloud based, but a separate app, not the Teams client. |
Most large standalone CCaaS platforms integrate through Connect, while a smaller group, including Luware, holds Microsoft's Extend certification. Extend means Teams remains the calling client and the media path stays on the Teams calling stack. It does not mean no supplier cloud processes data: Nimbus is an Azure-hosted SaaS application that processes routing records, configuration, user state, conversation context, and other operational metadata. Security review should cover both the media architecture and the Nimbus data boundary.
Certification status checked August 17, 2026 against Microsoft's certified contact center list. Data categories are disclosed in Microsoft 365 App Certification.
There is a second, separate question that often gets tangled up with the integration model: how do outside phone numbers reach Teams in the first place? This is the PSTN layer, and it is independent of which contact center you choose. Any of these can sit underneath a native Extend contact center.
Pick a participating carrier straight from the Teams admin center. They provision your numbers and manage the trunk. No session border controller for you to run, and fast to stand up.
Connect your own or a partner's SIP trunk through a certified SBC. More control over carriers, porting, and least-cost routing, in exchange for more to configure and manage.
Buy minutes and numbers directly from Microsoft as an add-on license. Simplest to buy, though it is not available everywhere and can cost more at scale.
The phrase people search for, native Operator Connect contact center, is really two good ideas stacked together. Operator Connect (or Direct Routing) brings the numbers into Teams, and the Extend model keeps the resulting call inside Teams. Put together, the call is born in Teams and never leaves it.
The voice call stays on the Teams calling stack instead of being hairpinned through a second CCaaS voice cloud. Nimbus still processes the metadata needed to route and report on the interaction.
Agents answer, transfer, and collaborate in the Teams client they already live in. No second softphone, no swivel-chair between two apps.
With Operator Connect underneath, there is no session border controller or extra voice infrastructure for your team to buy, patch, and babysit.
Teams presence, the full company directory, and one-click expert transfers are native, so agents can pull in a back-office colleague without leaving the call flow.
Identity, endpoints, presence, and the Teams client are already in place. A contained queue can move quickly, while a multi-service build still needs workflow, number, reporting, integration, and acceptance work.
Microsoft remains responsible for Teams calling and identity; the carrier owns PSTN access; Luware owns Nimbus routing. A managed provider can coordinate those boundaries, but the design still involves all three.
Nimbus is not one monolithic edition. It is a set of service and user licenses that can coexist in one tenant. That matters: a reception desk, an internal IT queue, and a formal customer-care team should not all be licensed the same way. We deliver Nimbus through Momentum, which can coordinate the Luware subscription, PSTN, implementation, and support under one managed design.
| Module | Licensed by | What it is for | Important dividing line |
|---|---|---|---|
| Advanced Routing | Service / queue | Departmental call flows, IVR, announcements, availability routing, queue position, and outbound service calls. | Routing layer, not a formal agent-management seat. |
| Enterprise Routing | Service / queue | Adds richer workflow logic, conversation context, Power Automate integration, external tasks, and broader automation. | Best for an “informal contact center” where Teams users still work as ordinary employees. |
| Contact Center | Named user | Skills and priority distribution, agent states, after-call work, work profiles, supervision, omnichannel tasks, and deeper reporting. | This is the formal agent and supervisor tier. |
| Attendant Console | Named user | Receptionist workspace with queue visibility, directory and presence search, notes, parking, and safe, consultative, or blind transfer. | Separate role-based tool; it can stand alone or sit beside routing/contact center licenses. |
Module boundaries summarized from Luware's current Nimbus feature matrix. Confirm every workflow and add-on in the order form; feature availability follows both the service license and the user's role.
Drag-and-drop workflows, IVR, time and availability checks, queue position, callbacks, skills, priority, and preferred-user logic.
A full receptionist and operator console for high-volume call handling, with presence-aware transfers across the directory.
Email, web chat, WhatsApp, and external tasks can enter the same distribution model. Exact channel support and connectors depend on the selected service tier and add-ons.
Real-time dashboards plus listen, whisper, and barge-in for authorized supervisors. Historical analysis uses the Nimbus reporting model and Power BI.
Agents can call on behalf of a service, work callbacks, and receive scheduled outbound tasks. This is not the same category as a high-volume predictive dialer.
Momentum handles design, provisioning, PSTN, and ongoing support as one managed service, so it is not another platform for your IT team to own alone.
The integration story is strongest when your automation team already works in the Power Platform. Nimbus exposes trigger events and actions through a Microsoft-certified Power Automate connector, supports provisioning through an API, and publishes historical data for Power BI. That makes the building blocks accessible, but it does not make a CRM integration automatic: someone still has to design data lookup, screen-pop, write-back, failure handling, and API consumption.
Use caller ID or IVR answers to retrieve a record, set routing parameters, open a Salesforce or Dynamics contact, create a ServiceNow or Freshdesk ticket, and write after-call data back.
The premium connector can create callbacks and external tasks, manage address books, read opening hours, update active tasks, and react to Nimbus events.
A ready-made report template sits on the Nimbus reporting model. Role and organizational-unit permissions determine which session and user-state data a viewer can retrieve.
Microsoft currently documents a limit of 100 API calls per connection every 60 seconds for the Luware Nimbus connector. A screen-pop flow might use several actions per interaction, so high-volume designs need concurrency, retry, throttling, and failure-queue testing before production. The connector is also unavailable in GCC, GCC High, DoD, Azure Government, and China regions.
See the Microsoft connector reference and Luware's CRM integration overview.
Nimbus removes a second agent softphone; it does not remove contact-center design work. A small, single-queue pilot can move quickly when Teams Phone and numbers are already stable. A production rollout is governed by the number of services, integrations, countries, recording policies, reports, and migration waves, not simply the number of agents.
Inventory numbers, call flows, hours, skills, languages, recordings, reports, integrations, and exception paths.
Confirm Teams Phone, PSTN, resource accounts, Entra roles, app permissions, security review, and Luware region.
Provision services, assign modules, create workflows, configure profiles, dashboards, recording, and integrations.
Test every route, transfer, failure, callback, holiday, overflow, emergency path, report, and permission boundary.
Port or reassign numbers in waves, train agents and owners, monitor live traffic, and retain a rollback route.
Luware's installation documentation requires an Entra Global Administrator for setup, a Nimbus tenant administrator, the Nimbus app manifest and permissions, Teams Phone licensing, resource accounts, and PSTN configuration. Luware also documents an external-access dependency on the luware.com domain and a presence-policy requirement. Those are governance decisions, not last-minute technical chores.
Prerequisites checked against Luware's current installation prerequisites and installation guide.
The Nimbus deployments below cluster in the public sector, where government bodies run citizen-facing lines at thousands of users and hundreds of services. Regulated European finance and insurance also appear, where Teams-native routing, recording, residency, and governance requirements feature prominently in the published case studies.
National and local bodies moving citizen phone lines off older on-premises systems, at large user counts and with heavy seasonal peaks.
Regulated Swiss firms that needed routing and recording to sit inside Teams while still satisfying financial supervisors and data residency rules.
Providers running their own support hotlines inside Teams, with live queue visibility for the desk and coaching tools for supervisors.
Standardizing many separate service lines and offices onto one routing and reporting model, with overflow to outside partners at peak.
A clinical crisis line using Teams-native routing, live reporting, and call recording, with the deployment and outcomes documented by Luware.
Routing and queue management handled in Teams by a builder with staff spread across many divisions, with recording used for coaching.
Every organization above is named publicly at the linked source. ContactCenterGuide.com is not claiming any of them as a reference.
If your company already runs on Microsoft 365 and Teams Phone, a native contact center is almost always the cleaner path than bolting on a separate CCaaS cloud. We deploy Luware Nimbus via Momentum for exactly this. If Teams is not your center of gravity, or you need a heavy outbound dialer or the deepest omnichannel suite, a best-of-breed platform may fit better, and we will tell you so. Get an estimate and we will map it to your setup.
Luware now publishes USD list prices, which makes the starting point clearer. The wrinkle is the unit: routing is licensed per service, while formal contact center and attendant licenses are per named user. A “service” is a routed line or workflow such as customer care, claims, or the main switchboard, not an agent.
| Nimbus license | Published USD list | Metric | Published volume condition |
|---|---|---|---|
| Advanced Routing | $85 / month | Per service | For 25 services or more |
| Enterprise Routing | $170 / month | Per service | For 25 services or more |
| Contact Center | $85 / month | Per named user | Up to 199 users |
| Attendant Console | $105 / month | Per named user | Up to 199 users; includes five CC Voice services |
Vendor list prices viewed August 17, 2026 on Luware's pricing page. They are not a reseller quote and exclude Microsoft, carrier, implementation, support upgrades, add-ons, usage, taxes, and any different term or volume band.
Choose service licenses for each routed workflow and named-user licenses for formal agents, supervisors, and attendants. Add-ons and premium support can sit above these rates.
Every call-handling user needs Teams Phone and Enterprise Voice enabled. Each Nimbus service using PSTN needs a Teams Phone Resource Account license; Calling Plans add their own entitlements.
Operator Connect, Direct Routing, or Microsoft Calling Plans supply numbers and outside calling. Price DIDs, ports, minute bundles, toll-free, international, emergency calling, and concurrency.
Budget discovery, workflow build, integration, number migration, reporting, training, project management, and ongoing managed support. These are scoped, not included in vendor list.
Twenty agents serving two queues is a different bill from twenty agents serving thirty branch numbers. Ask for both counts and map every queue to Advanced, Enterprise, or Contact Center.
Show Microsoft, Nimbus, carrier, support, implementation, add-ons, storage, and annual increases as separate lines. Include expected service and agent growth by year.
The public $85 Contact Center rate is useful for comparison, but it is not a complete per-agent total. See our wider CCaaS pricing guide, or request a modeled Nimbus estimate using your service count, agent roles, Microsoft entitlements, countries, and PSTN design.
The shortest way to qualify Nimbus is to ask whether Microsoft Teams is a requirement or merely an integration checkbox. If agents, experts, identity, telephony, and governance already live in Teams, Nimbus removes duplication. If the contact center needs to operate as its own global platform with industrial outbound and deep workforce tooling, the Microsoft-native advantage may not outweigh a broader CCaaS suite.
Ask Luware to show your hardest overflow route, supervisor intervention, after-call state, CRM failure, callback, outbound scenario, recording retrieval, Power BI row-level access, holiday change, and disaster route live. Then map each one to its required service license, user license, add-on, Microsoft entitlement, and support owner.
Teams Phone includes auto attendant and call queues, which cover a basic internal help line. It is not a full contact center on its own. For skills-based routing, omnichannel, wallboards, and reporting you add a certified contact center that integrates with Teams through one of three Microsoft models: Connect, Extend, or Unify.
A native Teams contact center uses the Extend integration model. The provider orchestrates routing through Microsoft APIs while Teams remains the calling client and media path. The supplier still processes the operational data required to route and report on the interaction, so “native” should not be read as “no third-party data processing.”
No. A small group of providers build on the native Extend model, but most large CCaaS platforms integrate through the Connect model (which takes the call out of Teams) or the newer Unify model (a separate Azure Communication Services app). Luware Nimbus is an Extend-certified, Teams-native platform, and it is the option we deploy and manage through our partner Momentum.
Both bring outside phone numbers (PSTN) into Teams. Operator Connect lets you pick a carrier from the Teams admin center and have them provision numbers with no session border controller to manage. Direct Routing connects your own or a partner's SIP trunk through a certified SBC, which gives more control at the cost of more setup. Either one can sit under a native Extend contact center.
Luware's published US list pricing is $85 per month for each Advanced Routing service, $170 for each Enterprise Routing service, $85 for each named Contact Center user, and $105 for each named Attendant Console user. The published routing prices assume at least 25 services and user prices cover up to 199 users. Microsoft licenses, PSTN, implementation, support upgrades, add-ons, usage, and taxes are separate.
A contained pilot can move quickly when Teams Phone, PSTN, numbers, and security approvals are already in place. A production timeline follows the number of services, workflows, integrations, countries, reports, recording policies, migration waves, and testing requirements, not just the agent count. Ask for a milestone plan based on those inputs rather than a generic “days to deploy” promise.
No. Extend keeps Teams as the calling client and media path, but Nimbus is an Azure-hosted supplier application that processes operational data such as routing records, configuration, user states, conversation context, and reporting data. Recording and retention architecture also depends on the selected solution. Review Luware's data residency, subprocessors, permissions, retention, and recording design during security diligence.
Nimbus can integrate with CRM and ticketing platforms through its Microsoft Power Automate connector and APIs. Common patterns include Dynamics or Salesforce screen-pop, ServiceNow or Freshdesk ticket creation, caller-data lookup, skills or preference routing, callbacks, address books, and after-call write-back. Power BI is used for historical reporting. Treat these as integration building blocks that still require design, licensing, testing, and support ownership.
An independent advisor scopes a Teams-native build against the alternatives that match your channels, volume, and licensing. Free, no vendor bias.
844-506-2299 · Free advisory · No obligation