Microsoft Teams Automatic Recording for Call Queues (MC1401299/565215): What You Need to Know

Introduction

Earlier this year, we wrote about Compliance Recording for Call Queues in Microsoft Teams and why applying recording at the queue level is often a much more practical model than relying exclusively on policies assigned to individual users.

Microsoft has now taken that idea a step further. In August 2026, Microsoft made Automatic Recording for Call Queue ¹ available, providing a first party Teams capability for automatically recording and optionally transcribing inbound calls handled through a call queue.

When recording is enabled, inbound queue calls are automatically recorded when a Teams user answers, and the recording stops when the call ends. Transcription can be enabled separately.

The resulting recordings and transcripts are stored in SharePoint. With Shared Call History enabled, authorised users and representatives can access them through the Queues App, subject to the permissions configured for the recording template.

This is an important development, particularly for the many organisations using Microsoft Teams call queues as a lightweight contact centre. A small customer service team may simply want every incoming queue call recorded without relying on an agent to remember to start recording manually. Microsoft can now address that requirement natively because recording is configured for the queue and begins automatically when an agent answers.

It also changes the discussion around platforms such as Argus Archive. Automatic capture is now available natively, so a dedicated platform needs to provide value beyond simply creating a recording.

How Microsoft Teams automatic recording for call queues works

Microsoft describes Automatic Recording for Call Queue ² as a first party Teams capability for automatically recording and transcribing inbound call queue calls.

Recording and transcription are configured independently and are disabled by default when an Automatic Recording template is created. Once recording is enabled and the template is assigned to a call queue, inbound calls are automatically recorded when a representative answers.

Administrators can configure the announcement played to callers. Microsoft’s default announcement can be used, or replaced with an audio file or text to speech greeting.

Recording is configured against the queue rather than the individual person answering it. This is useful where the queue itself represents a particular business activity, such as customer service, claims, sales or support.

The people answering those calls do not need individual recording policies for Automatic Recording. They do, however, need to meet Microsoft’s normal call queue requirements. Microsoft states that representatives receiving calls from a call queue must be Enterprise Voice enabled.

Access to recordings is controlled separately. Administrators can determine whether representatives can view recordings and transcripts. Shared Call History must be enabled for access through the Queues App, and access to the Queues App requires Teams Premium.

The distinction is important from a licensing perspective. A person does not need Teams Premium simply to answer a call queue call because Automatic Recording has been enabled. Teams Premium becomes relevant when that person needs the Queues App functionality used to access the recordings and transcripts.

For many smaller call centres, Microsoft’s native recording may be enough

Not every organisation using Teams as a contact centre needs a dedicated recording platform.

Consider a customer service team with ten people answering calls. Recordings might primarily be used for training, occasional quality review, resolving customer disputes or maintaining a history of important interactions.

Microsoft can now automatically record answered inbound queue calls, optionally create transcripts and store the resulting material in SharePoint. Where the requirement is primarily to capture calls and retrieve individual conversations when necessary, this may be enough.

A recording archive is relatively simple to use when somebody already knows which interaction they need. A customer provides a date and approximate time, for example, and a supervisor retrieves the relevant recording.

The economics and complexity of introducing another platform simply to reproduce those capabilities would be difficult to justify.

The limitations become more relevant as the organisation places additional requirements on the recordings themselves. Storage location, retention, privacy requests, investigation, quality assurance and regulatory recording can all change what is required from the architecture.

Practical considerations when enabling Automatic Recording for Call Queues

Automatic Recording is relatively straightforward to enable, but organisations should consider how it fits into their wider business requirements before deployment. Its scope is limited to inbound call queue calls, while the use of SharePoint introduces decisions around storage, data residency, retention and privacy.

These considerations become more important where Teams is used for other customer communications or recordings contain personal or regulated data. We cover the wider privacy considerations in our guide to GDPR and Call Recording: What Businesses Need to Know in 2026.

SharePoint storage and data residency

Automatic Recording stores recordings and transcripts in SharePoint, with no supported alternative storage destination. When the recording template is created, the administrator selects the SharePoint host and site, as detailed in Microsoft’s Automatic Recording for Call Queue configuration guidance ¹.

The site must be provisioned through the template creation process, and manually created sites are not supported. Once the template has been created, its SharePoint host and site cannot be changed, although the same site can be reused across multiple recording templates.

Microsoft also warns that changing the site structure, filenames or permissions can cause access issues or recording failures.

For global organisations, the SharePoint location also determines where the recording data resides. Microsoft 365 Multi-Geo allows eligible organisations to maintain SharePoint sites in different geographies, with content stored in the geography associated with the site.

An organisation with a US Microsoft 365 environment but a European service line, for example, may need to consider where the recording site is provisioned if those calls are required to remain in Europe. The location of the telephone number, call queue or person answering the call does not determine where the recording is stored.

This makes the SharePoint location an important design decision before Automatic Recording is deployed, particularly where recordings are subject to geographic data residency requirements.

Retention, deletion and privacy requests

Storage location is only one consideration. Organisations also need to decide how long recordings should be retained, when they should be deleted and how they will respond to requests involving an individual’s recorded communications.

Microsoft Purview retention policies and retention labels can be applied to the recordings and transcripts stored in SharePoint, allowing organisations to retain or delete content according to defined policies.

Deletion can become more complicated where a recording is subject to a retention policy, retention label or legal hold. Removing the file from its normal SharePoint location does not necessarily mean that it can be permanently deleted.

Privacy requests introduce a similar challenge. If a customer asks an organisation to locate or delete recordings containing their personal data, the relevant conversations need to be identified before the organisation can determine how the request interacts with its retention policies, legal obligations and any applicable holds.

For organisations recording significant volumes of customer calls, the ability to search, identity and delete recordings consistently becomes an important part of managing the SharePoint archive.

Automatic Recording Only Covers Inbound Call Queue Calls

Automatic Recording has a deliberately narrow scope. It records inbound calls answered through the configured call queue, but does not extend automatic recording to a user’s direct Teams calls, outbound PSTN calls or Teams meetings.

This matters when the same representatives communicate with customers in different ways. A queue call may be recorded automatically, while a follow up call made directly from Teams falls outside the feature.

Recording is also controlled at the queue level. Once Automatic Recording is enabled, representatives cannot pause or stop the recording during the call. Organisations that need broader coverage or greater control over how communications are captured may therefore need to consider Microsoft’s Compliance Recording architecture.

Fail Closed and Compliance Recording

Some organisations cannot allow a call to continue if the recording system is unavailable. Microsoft addresses this through strict recording within its separate Compliance Recording for Call Queues ⁴ architecture. The recording bot can be required before a call is answered and throughout the conversation; if that requirement cannot be met, the call is disconnected.

This is particularly relevant in regulated environments where missing a required recording creates a compliance risk. We cover the wider differences between native and compliance recording in Microsoft Teams Native Recording vs Policy-Based Compliance Recording.

Microsoft Teams Automatic Recording for Call Queues vs Argus Archive

For organisations that want to remain within the Microsoft ecosystem, Automatic Recording can form part of a capable recording solution. SharePoint provides the repository, Microsoft 365 provides search and governance capabilities, and Copilot can add natural language search across supported content.

This may be a good fit where recording requirements are relatively simple and the organisation already has the necessary Microsoft 365 licensing and expertise.

The distinction becomes more significant as the recording estate grows. Different business units may require separate storage locations, retention periods and access controls. Regulated recordings may need stronger protection against modification or deletion, while security and compliance teams may require detailed audit history, legal hold, supervision and controlled access to sensitive communications.

Microsoft 365 can address some of these requirements, but doing so can involve a combination of SharePoint, Purview, Copilot and additional governance capabilities, with licensing and configuration varying according to the controls required.

Argus Archive provides these capabilities within a platform designed specifically for recorded communications. Recordings, transcripts and call metadata are managed together, with communications specific search, retention, access control, audit, investigation and supervision applied across the archive.

The same archive can also be used for quality assurance and conversation analysis, including identifying required procedures, classifying calls and finding conversations that require review.

For organisations recording only inbound Call Queue traffic with straightforward governance requirements, Microsoft’s native approach may be entirely sufficient. It keeps recordings within the Microsoft 365 environment and can be extended with SharePoint, Purview, Copilot and other Microsoft 365 services as requirements grow.

The trade off is that capabilities such as AI search, retention, records management, audit and more advanced governance can span several services, licences and administrative policies. This may be perfectly reasonable for organisations already invested in the Microsoft ecosystem, but becomes more complex as recording requirements expand across teams, regions and use cases.

Argus Archive provides these capabilities within a dedicated communications archive, with AI analytics adding semantic search, AI assisted investigation and conversation analysis. It also addresses requirements beyond Automatic Recording, including broader call and meeting coverage through Microsoft’s Compliance Recording architecture, strict recording controls and communications specific supervision.

Final thoughts

Microsoft’s Automatic Recording for Call Queues is a significant improvement to Teams Phone. For organisations with straightforward inbound recording requirements, it provides a practical way to capture calls and transcripts while keeping them within Microsoft 365.

Its limitations become more important as requirements expand beyond inbound Call Queues or involve more complex storage, retention, access and compliance controls. Microsoft 365 can address many of these requirements through additional services, while Microsoft’s Compliance Recording architecture provides the route for organisations that need broader control over recording and archiving.

For organisations looking beyond recording, the next step is connecting communications with the wider Microsoft ecosystem without losing the governance applied to the archive. We explore this in Extending Microsoft 365 Copilot with Governed Communications Intelligence.

Frequently Asked Questions

References

1. Microsoft Learn: Setup – Automatic Recording template for Call Queue: https://learn.microsoft.com ↩︎
2. Microsoft Learn: Recording voice applications calls. https://learn.microsoft.com ↩︎
3. Microsoft Learn: Setup – Automatic Recording template for Call Queue: https://learn.microsoft.com ↩︎
4. Microsoft Learn: Setup – Compliance Recording for Call Queues template https://learn.microsoft.com ↩︎