Day 1 was Satya Nadella owning an outage and handing agents a seat in Teams. In our day 1 round-up, I called it a meter without receipts. Day 2 was about giving those agents a voice, and a bigger room to work in. Here's my verdict: Microsoft is turning Teams into the place agents answer the phone and join the project, while the Teams Phone and Rooms roadmap stayed quiet.
Voice Agents Pick Up the Phone in Teams
The biggest UC news came out of Foundry. Microsoft says voice agents in Foundry Agent Service are now generally available, and they can connect to existing telephony and contact center systems, including Teams Phone, Twilio and Genesys. Gulf Air is the named customer.
For context, Microsoft's Contact Center Intelligence (CCI) went GA on day 1. It layers Microsoft's voice and digital agents on top of a contact center a company already runs, as we covered in the Dynamics 365 announcement. Foundry is the developer route. CCI is the buy-it route.
There's a third door, run by partners. NiCE says Cognigy is among the first to complete certification for Microsoft's Teams Unify model for voice agents, answering inbound Teams Phone calls and handing callers to the right person, queue or department with context. Microsoft's own certification page lists AudioCodes, CentrePal, Heedify and NiCE/Cognigy, and says Microsoft supports voice agents only from certified partners.
The fair case for Microsoft: your numbers, queues and PSTN stay in Teams Phone while a voice agent handles routine calls. The catch is who you call when the agent mishears a customer. The answer is the partner first, then Microsoft.
Interpreter Gets Quicker
Microsoft also updated the Live Interpreter API in the Foundry post: a new model that translates while people are still talking, with 30% fewer translation errors, end-to-end translation in under 3 seconds and the speaker's own voice preserved. On the Teams side, Microsoft's Interpreter support page describes simultaneous interpretation for meetings of up to 1,000 participants. I'm not going to claim more for large Teams Events until Microsoft puts it in writing.
Copilot Workspaces and Autopilot Share the Room
Workspaces, the evolution of Copilot Notebooks, is now available in Frontier. On day 1, Microsoft's post on X pitched it as a multiplayer experience for people and agents. The Copilot blog spells out the idea: an agent drafts a section, you review, you comment, and an agent picks it up. The collaboration continues in Teams.
“Workspaces makes it a truly multiplayer experience, where people and agents drive towards a common goal, with shared context.”
Microsoft Copilot blog, Ignite 2026
Autopilot is the other half. Microsoft describes it as a trusted autonomous agent that is personal to you, always on, and lives in your tenant. You can @mention it in Teams, Outlook, chats and channels like a colleague. Each Autopilot has its own Microsoft Entra Agent ID and a named manager, IT can scope its access and block it, and its actions are logged under its own name. It's starting to roll out in Frontier, and Microsoft says you can check with it before key actions. Coming soon, teams will bring Autopilots into Workspaces.
Meanwhile, at the desk, someone will find their colleague's Autopilot has more follow-ups scheduled than they do. Both are Frontier, so not yet something your service desk has to support.
Salesforce is now inside this, too. Microsoft and Salesforce's Copilotforce announcement puts Salesforce in Copilot, with Sales Cloud in Teams in pilot. Marc Benioff posted on X that real-time CRM collaboration is live in Microsoft Teams.
Viva Engage Communities Land in Teams
Quietly, Communities in Teams is generally available. Employees can join communities and share knowledge alongside their daily work, so the conversation moves to where staff already are.
Agent 365 Hits 50 Million and Asks the Hard Question
Microsoft says organizations have registered more than 50 million agents in Agent 365 since its May 2026 launch. It then asks the question IT is already asking.



