Migrating Teams Calling Bot (EchoBot) from VMSS to Windows Containers / ACI?
Hi everyone, I have built a Microsoft Teams Calling Bot using Application-Hosted Media based on the official C# EchoBot sample: https://github.com/microsoftgraph/microsoft-graph-comms-samples/tree/master/Samples/PublicSamples/EchoBot Currently, our signaling logic is fully serverless and runs efficiently on Azure Functions. However, the actual media processing (using the C# Calling SDK which relies on native Windows media binaries) is deployed on VMSS with Windows Server, just like the repository's default deployment guide suggests. Running these Windows VMs continuously is becoming extremely expensive, and we are looking for a cheaper, modern, or "on-demand" alternative to handle the media pipeline. Since raw audio processing strictly requires these native Windows-based Media binaries, I would like to ask the community: 1. Windows Containers (ACI / AKS): Has anyone successfully run this C# EchoBot/Media SDK inside Windows Containers (such as Azure Container Instances or AKS)? If so, how do you handle the public IP and port-binding requirements for the media sockets (since the platform needs direct public connectivity for UDP/TCP traffic)? 2. On-Demand Provisioning: Are there any known architectures or best practices for spinning up the media processor only when a call starts (e.g., triggering an ACI instance via the Azure Function signaling bot) and tearing it down afterwards to keep costs near zero when idle? 3. Alternative Approaches: If you have solved this high-infrastructure cost problem for a real-time raw audio bot in production, what architecture did you end up using? Any documentation, GitHub references, or architectural advice would be highly appreciated! Thanks!
Teams Freezes ~90 seconds into a 1:1 Mac OSX
Teams video and audio starts freezing 90 seconds into a 1:1 call, and then it comes back to normal and wont happen again. This started about 3 weeks ago and it happens only during 1:1 calls wont happen when there are more then 2 people in a call. Mac OSX 26.5.1 (25F80) Teams Version 26149.1804.4788.5681
How can I report an error in MS Teams documentation?
Hey all, how can I report an error that I noticed in MS teams documentation? On this site: https://learn.microsoft.com/en-us/microsoftteams/phone-reference/manage-numbers/phone-number-management-for-slovenia There is a LOA request that is named: "Letter of Authorization (LOA) for Slovania (all numbers) (v.1.0)". This is of course an error - it should say Slovenia, not Slovania. How do I report this to MSFT for checking and fixing the Learn docs? I cannot seem to edit or submit a PR for MS teams. Thanks! BR TimUsing the Small Window for Incoming Teams Calls
A recent improvement is the introduction of a small window for incoming Teams calls. It doesn’t sound like a great step forward, but switching to the small window is a surprisingly useful step. The sad thing is that many users won’t know that the option to switch exists because it’s buried in Teams settings. If you’re a busy person who takes lots of Teams calls, switching is definitely recommended. https://office365itpros.com/2026/06/30/incoming-teams-call-window/Microsoft Teams API Capabilities
Good morning, We are contacting you to find out whether it is possible to achieve the following functionalities through the Microsoft Teams API: Start a scheduled meeting automatically Through a voice command, a meeting scheduled in a room's calendar is automatically started, and all the necessary equipment and services are activated without any user intervention. Automatically answer an incoming call in a meeting room When a call is placed to a specific account, the room automatically answers the call without requiring any user action. Add participants to an ongoing call or meeting Allows new attendees to be added to an active meeting or call in progress. Thank you in advance for your assistance. Kind regards,Engage customers with Teams Phone Agent and custom voice agents built in Copilot Studio
It’s often difficult for businesses to serve every customer right away during surges in call volumes. Callers sit on hold while staff race to work through the backlog. Meanwhile, agentic voice AI is opening entirely new ways to serve customers, such as getting answers to questions or even enabling them to pay a bill over the phone, including after hours and on weekends. We are excited to announce Teams Phone Agent, along with the ability to bring custom voice agents your organization builds in Microsoft Copilot Studio to Microsoft Teams Phone. For customer-facing organizations using Teams Phone, like healthcare clinics or bank branches, these agents take repetitive calls off the plate of employees so they can focus on the conversations that truly need a human touch. All this enables faster issue resolution for customers. How Teams Phone Agent works Teams Phone Agent greets callers and resolves common requests with these skills. Questions and Answers: Using configured knowledge bases that support file uploads and URLs, Teams Phone Agent answers callers' questions in natural conversation, so customers get answers quickly instead of being placed on hold or hunting through a website. Appointment scheduling: Teams Phone Agent enables callers to book new appointments, reschedule or cancel existing ones, and find upcoming appointment details so customers can lock in a time without playing phone tag. Conversational Routing with intelligent transfers: Teams Phone Agent supports the same tried and tested routing from traditional auto attendants, such as user or extension lookup and transfer to a user, call queue, and more through conversation. When additional assistance is needed, Teams Phone Agent passes the caller along with the full context of the conversation to the right individual or department. Customers can skip cumbersome phone menus and don’t have to repeat themselves. Multilingual: Teams Phone Agent supports multilingual conversations across 60+ supported languages, allowing callers to interact naturally in their preferred language and helping organizations deliver global voice experiences at scale. Automate what’s unique to your business with Copilot Studio voice agents When you need to automate processes unique to your business, like letting patients fill a prescription over the phone, custom voice agents that your organization builds in Copilot Studio step in. Teams Phone Agent can seamlessly hand off a call to custom voice agents whenever those specialized skills are needed. Alternatively, you can set things up so customers can dial a Copilot Studio custom voice agent directly through a Teams Phone line. Voice agents with Teams Phone in action Here are a few illustrative use cases for how Teams Phone Agent and Copilot Studio voice agents can help organizations engage their customers: Answer routine questions without making callers wait. A healthcare clinic can use Teams Phone Agent to answer common questions about hours, locations, accepted insurance, and appointment preparation, helping patients get answers quickly while staff focus on care coordination. Book and reschedule appointments over the phone. A home services company can use Teams Phone Agent to help customers schedule, confirm, or change appointments for plumbing or electrical repairs in natural conversation, helping reduce back-and-forth calls and freeing employees from repetitive scheduling work. Route customers to the right expert with context. A bank branch can use Teams Phone Agent to understand what type of support a caller needs, such as assistance with completing a mortgage loan application. Teams Phone Agent can then transfer the call to the right team with the conversation context included. Complete business-specific tasks with a Copilot Studio voice agent. A pharmacy can use a Copilot Studio custom voice agent to help customers request a prescription refill by phone and check order status, giving customers a simpler way to manage routine needs without waiting for staff assistance. Support customers after hours. A utility provider can use a Copilot Studio custom voice agent connected to Teams Phone to let customers report an outage or get billing help outside normal business hours. Launch Demo An expanding ecosystem of voice agents for Teams Phone We want customers to have choice across first-party and third-party voice agents. That is why we are working with select solution developers to integrate their voice agents with Teams Phone. AudioCodes is announcing general availability of its voice agent for Teams Phone today, with additional solutions expected in the future. Get started Teams Phone Agent and the ability to integrate custom voice agents built in Copilot Studio with Teams Phone are now accessible through the Frontier program. Join Frontier so that your organization can get early access to Microsoft’s latest AI innovations. Teams Phone admins can set up Teams Phone Agent through Teams admin center. Learn more. Copilot Studio makers can navigate to Microsoft Copilot Studio to set up a voice agent and then assign it to Teams Phone Agent or a Resource Account to be called directly. Learn more. Licensing during the Frontier preview Teams Phone Agent is available via the Frontier program. Service limitations may apply. Custom Copilot Studio voice agent experiences—whether reached through a Teams Phone Agent hand-off or by direct dial—are accessible via the Frontier program and are billed consumptively at a rate based on the orchestration type your organization selects when building the agent in Copilot Studio. Learn more. Billing for Copilot Studio voice agent experiences in Teams Phone will roll out by early July, and usage will not be charged prior to this rollout. Service limitations may apply. When the billing experience is rolled out, all Frontier preview users will be required to set up billing to continue using Copilot Studio voice agents for Teams Phone. Tenants must also meet standard Teams Phone prerequisites, including a properly configured Teams Phone resource account. Learn more. All licensing, pricing, and service limits are subject to change. Additional information will be communicated at general availability.How much should Teams presence influence call routing
One thing I've noticed recently is that many Teams Phone environments still treat presence as a destination state rather than a routing input. A typical flow might look like: Caller selects an option Call is transferred User is unavailable Caller ends up in voicemail or another queue Technically the routing worked. From the caller's perspective, it often didn't. I'm curious how others are approaching this. Are you using Teams presence as part of your call-routing logic? For example: Available → transfer immediately Busy → offer an alternative path In a meeting → capture context Offline → route elsewhere Or are traditional queues and escalation paths still sufficient for most scenarios? Interested to hear what people are doing in real deployments.
Stop Automatic Calling when Screensharing
I screenshare a lot in my position; I call the coworker (Phone/Headset) and train them on what I need them to look at. I am in a large office building, and the automatic calling of the receivers' PC is disruptive, as I do not was the whole office to hear my conversation or have people hear my trainee. I see no way to disable the team auto-call once I start to screen share or in the Options. All my coworkers feel this frustration as well. I do use the computer microphone/speaks aspect when working from home, but would disable it totally, if it would stop the auto-call. I do not want it to affect meeting invites to others, as others around the country can use their PC speak/microphone, if they want. Please advise.
Regarding Teams Meeting Media Transport Behavior in VDI Optimization Scenario
Hello Microsoft Teams Engineering Team, I am currently working on a Browser Content Redirection / media offload implementation for a VDI environment, where WebRTC media transport is handled through a local native component while the Teams application continues running inside the virtual desktop session. While testing, I observed that: 1:1 calls successfully receive audio and video media But in meetings auido / video RTP is never forwarded despite successful ICE, DTLS, and SRTP establishment DTLS ApplicationData traffic is present during meetings, suggesting DataChannel/SCTP activity Based on transport-level observations, it appears that Teams meetings may rely on SCTP/DataChannel communication for SFU video subscription management, while 1:1 calls do not require the same subscription flow. I wanted to ask whether: Teams meeting video forwarding depends on active bidirectional SCTP/DataChannel connectivity Meeting video subscriptions are expected to be coordinated over the WebRTC data channel/control plane Split ownership of media transport and control-plane transport could affect expected Teams meeting behavior in VDI optimization scenarios Thank you for your time and guidance. Best regards,Rajdev
