NiCE announced what it calls a significant strengthening of its collaboration with Microsoft, launching two new solutions meant to let AI and human agents work as one workforce. The announcement is vendor-authored. Business Wire distributed it as a paid press release. The benefits it describes are claims, not measured results.
Two announcements, not one
The press release bundles two separate things.
1. Cognigy as a certified Teams Phone voice agent
NiCE says Cognigy is among the first providers to complete certification for the Teams Unify integration model for voice agents, bringing its AI-driven customer experience automation to Teams Phone. Built on Teams Phone extensibility, the integration lets enterprises add Cognigy as an Intelligent Voice Agent. It answers inbound calls, automates conversations and, when needed, hands callers to the right person, queue or department with context.
NiCE also says Teams Phone keeps providing the telephony underneath. That covers phone numbers, PSTN connectivity and call queues, so customers don't have to change their existing telephony setup. That is NiCE's description of its own solution. Microsoft's documentation confirms the general extensibility model but not every detail of NiCE's implementation.
2. A Cognigy, Azure, Teams and Dynamics 365 integration
NiCE Cognigy is also announcing a new integration connecting Cognigy with Azure, Teams and Dynamics 365 Customer Service. In the workflow NiCE describes, inbound calls go to a Cognigy AI agent that handles routine requests in natural, multilingual conversations. When human expertise is needed, the AI reaches out to a colleague on Teams in real time. The employee guides it behind the scenes and the AI relays the answer to the customer.
The release says this can reduce blind transfers, hold times and repeated explanations. It gives no benchmarks, customer deployments, pricing, language list or configuration steps. It doesn't say what data moves between Cognigy, Teams and Dynamics 365. It doesn't say what permissions or human-oversight controls apply, or whether the employee exchange is a call, a chat or something else. I won't guess at any of those.
What Microsoft's documentation adds
Microsoft's Teams Learn page for the Unify voice-agent model is the main way to check the certification claim.
- The listing is real. Microsoft's certified voice-agent table lists Audiocodes, CentrePal, Heedify and NiCE/Cognigy. The page was last updated on November 4, 2026, so the listing predates the press release.
- What certification means. The program verifies that each participating provider's solution offers the quality, compatibility and reliability Microsoft expects. The page says certified voice agents can answer calls, authenticate callers and capture intent. They can then route to a Teams Phone destination such as an Auto Attendant, Call Queue, individual Teams user or contact-centre live agent, while keeping the caller context.
- Where it can be used. Microsoft's planning page lists three places: Teams Phone Agent or auto attendant routing, call queue exception handling, and routing directly to a third-party voice agent.
- Context handoff. Microsoft's planning page says structured metadata flows through the Context Pane in the Teams call client. That metadata includes caller identity, intent, topic, conversation summary and sentiment. This is Microsoft's description of the platform model, and the release doesn't say how Cognigy fills those fields.
- Under the hood. Microsoft's Azure Communication Services overview describes an Auto Attendant or Call Queue transferring a call to a third-party voice bot. The bot uses Call Automation APIs and can transfer the call or add a human participant. That is a general pattern, not a Cognigy configuration guide.
The support boundary admins should read first
Certification doesn't mean Microsoft will troubleshoot everything. Microsoft says it supports voice-agent solutions only from certified partners. The documentation says you contact the voice-agent partner first, and the partner escalates to Microsoft through internal channels if needed. Microsoft may reject cases involving a noncertified solution, or ones its investigation shows the partner can address.
In practice, a bad call transfer or a failed context handoff probably starts with a ticket to NiCE, not Microsoft. That is my reading of the support language, not a stated NiCE policy.
Licensing needs separate checking too. Microsoft's planning page says third-party voice-agent partners have their own licensing requirements. Nothing I found sets out NiCE's terms.
How Unify differs from other integration models
Microsoft's contact-center documentation describes three models: Unify, Extend and Connect. Unify lets providers build native Azure Communication Services-based contact-centre applications on Teams calling infrastructure. Extend uses the Teams client platform and Graph APIs. Connect uses certified session border controllers and Direct Routing.
The same page lists NICE inContact under Connect, not Unify. It was last updated in April 2026. That is a different product from the Cognigy voice-agent certification, so don't treat the two NiCE listings as one thing. The Dynamics 365 integration is also separate from the certified voice-agent model. NiCE hasn't said it carries the same certification.
Availability and the Ignite demo
NiCE says Cognigy solutions are available on Microsoft Marketplace. The release says Microsoft will demonstrate the integration at Ignite on November 19, 2026, in San Francisco. That demo is scheduled and hadn't happened when this was written. The release gives no separate availability date for the new Dynamics 365 integration.
Analysis: who should care
Teams Phone shops adding AI voice. The pitch is that you keep your numbers, PSTN and queues and add a voice agent in front. That is attractive if you already run Auto Attendants and Call Queues. The proof will be how cleanly the escalation and context work in your environment.
Dynamics 365 Customer Service teams. The "AI asks a colleague on Teams" idea is the more novel part. It is also the vaguer one, because the release gives no operational detail. Ask where the conversation record is stored, who can be pulled in, and what the AI says to the caller while waiting.
Security and compliance leads. The release doesn't cover call recording, data residency or retention. Ask NiCE directly.
A balanced view. The Microsoft quote supports the Azure, Dynamics 365 and Teams positioning. It is still a partner-announcement quote, not a test result. Phrases like "market-leading" are marketing. The solid facts are the certification listing, the documented routing model and the support boundary.
Pre-rollout checklist
- Confirm NiCE/Cognigy appears on Microsoft's current certified voice-agent list.
- Ask NiCE for its prerequisites, licensing and deployment steps for your Teams Phone setup.
- Map where the agent would sit in your call flow: Auto Attendant, Call Queue overflow or direct routing.
- Check which context fields reach your human agents, and test a handoff.
- Ask whether the Dynamics 365 integration is generally available, and what it needs.
- Settle who handles support first. The documentation says it is the partner.
The Unify listing is verifiable and worth knowing about. The Dynamics 365 collaboration story is, for now, mostly a promise awaiting details.
References
- NiCE Unites AI and Human Agents with Microsoft on One Connected Customer Service Stack - Directors Club News - Directors Club News - · 2026-11-18T16:37:25+00:00
- Planning - Third-party voice agents - Microsoft Teams | Microsoft Learn learn.microsoft.com
- Teams Voice Agents integration - Microsoft Teams | Microsoft Learn learn.microsoft.com