Starting in August 2026, Microsoft Teams administrators will gain a powerful new capability: the automatic recording and transcription of every call handled by a Call Queue. The feature, which has appeared on the Microsoft 365 roadmap, allows IT teams to configure individual queues so that interactions between agents and callers are captured without manual intervention. Once enabled, each call answered by a representative will be recorded and transcribed, then stored securely in SharePoint for later review. This long-awaited addition promises to reshape how organizations handle compliance, agent training, and performance analytics, closing a significant gap in the Teams Phone experience.

Until now, call recording in Teams was limited to ad hoc or policy-based activation for 1:1 and group calls, while meeting recordings were a separate function. Call Queues—essential for customer support, help desks, and sales lines—lacked a built-in mechanism to capture conversations automatically. Admins relied on third-party compliance recording solutions or instructed agents to manually start recording, an error-prone process that risked missing critical interactions. With this update, Microsoft bakes recording and transcription directly into the Call Queue fabric, giving organizations a reliable, integrated alternative.

How Automatic Call Queue Recording Works

The core of the update is administrative control. For each Call Queue, an admin can toggle automatic recording on or off. When activated, the system will record every call that is connected to a live agent, from the moment the agent picks up until the call ends. The recording will include all audio streams—both the caller and the agent—and the accompanying transcript will be generated in real time using Microsoft’s speech recognition engine. Notifications will play to inform participants that the call is being recorded, aligning with regulatory requirements in many jurisdictions.

Microsoft has designed the feature for flexibility. While the roadmap entry suggests a simple on/off switch, deeper configuration is expected to follow. Admins may be able to set recording profiles based on business hours, queue length, or caller attributes. For instance, a healthcare organization might choose to record only calls from patients with scheduled appointments, while a financial services firm could enable blanket recording for all queues. Integration with Power Automate or Azure Logic Apps could also trigger custom workflows—such as flagging a recording for review if certain keywords are detected in the transcript.

SharePoint Storage and Microsoft 365 Integration

Recordings and transcripts will be saved to SharePoint, making them first-class citizens in the Microsoft 365 ecosystem. Unlike meeting recordings, which land in the organizer’s OneDrive or the channel’s SharePoint based on context, Call Queue recordings demand a dedicated location. Microsoft is likely to provision a document library within a SharePoint site associated with the Teams channel or a centralized compliance site. Admins will have control over where files land, with options to set retention policies, access permissions, and archival rules at the library or folder level.

Storing recordings in SharePoint unlocks robust search and discovery. The transcript file, typically in WebVTT or Word format, will be indexed alongside the video. A supervisor can search for a customer’s name, order number, or phrase like “cancel my account” and retrieve the exact call with a timestamped link. This transforms voice data from an opaque black box into a queryable asset, cutting the time needed to audit interactions or resolve disputes from hours to minutes.

AI-Powered Transcripts and Analytics

Transcripts will leverage the same AI that powers live captions and post-meeting transcripts in Teams. They will include speaker separation—labeling the agent and the caller—along with confidence scores and time stamps. For organizations with advanced compliance needs, sensitive data masking (e.g., redacting credit card numbers or social security numbers) may be available through Microsoft Purview integration. While not confirmed in the initial rollout, this capability already exists for meeting transcripts and would be a natural extension.

The searchable transcript also feeds into broader analytics. Contact center supervisors can aggregate call data to identify trends: common customer complaints, average call resolution time, agent sentiment, or compliance risks. Because the transcript lives in SharePoint, it can be processed by Power BI, Microsoft Viva Insights, or custom solutions using Microsoft Graph APIs. This turns each recorded call into a data point for performance management.

Compliance is arguably the biggest driver for automatic recording. Many industries—finance, healthcare, insurance, and government—require retention of customer communications. With recordings in SharePoint, organizations can apply Microsoft 365 retention labels that keep files for a defined period (e.g., seven years) and then automatically delete them. Legal holds can be placed on specific recordings when litigation is anticipated, preventing accidental deletion. eDiscovery tools can crawl the document library, collect recordings, and export them in a legally defensible format.

Audit logs track who accessed each recording, when, and what actions they took. This supports internal governance and regulatory audits. Furthermore, Data Loss Prevention (DLP) policies can scan transcripts for sensitive information and trigger alerts or block sharing outside the organization. For example, a DLP rule might detect a credit card number in a transcript and automatically encrypt the file with restricted permissions.

The ability to configure recording at the queue level also simplifies compliance architecture. Instead of provisioning recording policies for hundreds of individual users, an admin can apply a single queue-wide setting. As agents join or leave the queue, they inherit the recording rule automatically, closing gaps that arise from manual policy assignment.

Privacy Considerations and User Experience

Announcement of recording is standard in Teams, but automatic queue recording raises the stakes. When a caller enters a queue that is set to auto-record, they will hear a pre-recorded message: “This call is being recorded for quality and training purposes.” The agent may also receive a visual indicator in the Teams client. Microsoft will need to ensure that callers who object have an option—perhaps a menu to opt out or be transferred to an unrecorded line. How this is implemented remains unclear, but organizations must plan for scenarios where recording consent is required by law.

For agents, the knowledge that all calls are recorded can be a mixed blessing. It provides a safety net for disputes but may also feel intrusive. Transparency about how recordings are used—for coaching, not just punishment—will be critical to adoption. Managers can leverage the transcripts to highlight positive interactions and coaching opportunities, not only compliance failures.

Preparing for the August 2026 Rollout

Organizations running Teams Phone should start planning now. First, review existing Call Queue configurations and identify which queues warrant automatic recording. Not every queue may need it—an internal IT help desk might benefit, while a casual company news hotline might not. Consider storage costs: call recordings, especially with video, can consume significant SharePoint storage. Ensure your Microsoft 365 subscription includes enough quota or adjust retention settings to archive older recordings in cold storage.

Policy readiness is another step. If your industry requires specific recording notices or consent mechanisms, work with your legal team to draft compliant announcements. Test the feature in a pilot environment once Microsoft makes it available in preview—typically a few months before general availability. Pay attention to bandwidth and network impact; simultaneous recording of multiple queue calls could strain gateways if not properly scaled.

The Bigger Picture: Teams as a Complete Contact Center Platform

Automatic Call Queue recording is another milestone in Microsoft’s steady push into the contact center space. Teams already offers voice, video, chat, and collaboration in one app. Features like Power Virtual Agents for chatbots, Dynamics 365 Customer Service integration, and now intelligent recording, position Teams as a lightweight alternative to traditional contact center platforms. Small and medium businesses, in particular, stand to benefit from eliminating separate recording appliances and consolidating on a single Microsoft 365 stack.

Looking ahead, we can expect Microsoft to infuse more AI into these recordings. Sentiment analysis could flag calls where the customer expressed frustration. Summarization could give supervisors a one-paragraph digest of a 20-minute call. Integration with Viva Insights could surface workload metrics for queue managers. The transcript data, combined with voice analytics, could eventually predict customer churn or identify training needs across the agent pool. For now, the August 2026 update lays the foundation by making the raw material—recordings and transcripts—easily available and manageable.

Microsoft has not published a specific date in August 2026, but the timeline aligns with the company’s annual planning cycle. As always with roadmap features, delays are possible. IT decision-makers should follow the Microsoft 365 roadmap (feature ID to be assigned) and the Teams admin center message center for official confirmation.