Microsoft Teams Compliance Recording for Call Queues: A More Practical Model

Introduction

Microsoft has introduced compliance recording for call queues in Microsoft Teams¹, enabling recording to be applied at the queue level rather than only to individual users.

Recording inbound calls is a requirement in many regulated environments. However, organisations also record calls for a range of other legitimate business reasons, including quality assurance, training, dispute resolution, fraud investigation, and customer experience analysis.

In Microsoft Teams, recording for regulated scenarios has traditionally been implemented through user-level compliance recording policies. While that model can work in simple environments, it becomes harder to manage in contact centres where agents rotate between teams, calls are transferred frequently, and workflows are dynamic.

Microsoft’s introduction of compliance recording for call queues² represents a meaningful structural improvement. Instead of tying recording to individual users, recording can now be attached to the queue itself – aligning recording scope with the business function handling the call.

To understand why this matters, it helps to first look at how Microsoft Teams call queues operate.

Understanding Microsoft Teams Call Queues

A Microsoft Teams call queue³ distributes incoming calls to a defined group of agents rather than a single individual.

In a typical inbound scenario, a call first reaches an Auto Attendant, which handles business hours, menu options, and initial routing. Once the caller selects an option – for example, Sales or Support – the call is delivered to a call queue.

At that point, the queue manages the call according to predefined rules. It may place the caller into a waiting experience, play announcements, evaluate agent availability, and distribute the call using routing logic such as longest idle or round robin.

The important structural point is that the queue represents a business function. It might correspond to a support desk, a claims intake team, a customer service line, or a regulated advisory desk. The queue groups calls under a specific operational workflow, independent of which individual agent ultimately answers.

This distinction becomes significant when determining how recording should be applied.

The Call Queue as a Recording Boundary

In many organisations, the decision to record calls is based on the function being performed, not the person performing it:

• A customer support queue may be recorded for quality assurance.
• A financial advice line may be recorded to meet regulatory requirements.
• A fraud reporting line may be recorded for evidential purposes.

The common factor is that recording is tied to the business activity associated with the queue.

From a technical standpoint, the queue already defines a handling boundary. Once a call is delivered to it, routing, waiting rules, and escalation logic are governed centrally. Applying recording at that level is therefore structurally consistent with how call handling is designed.

This is what makes queue-level recording both practical and predictable.

Limitations of User-Level Compliance Recording

Under a user-level compliance recording model, recording policies are assigned directly to individual agents.

In stable, highly structured environments this can be workable. In modern contact centres, however, it quickly becomes difficult to manage.

Agents move between queues. Teams provide temporary coverage. Calls are transferred across departments. Consultations involve colleagues outside the original group. Each of these scenarios increases administrative overhead and raises the risk of configuration gaps.

More importantly, user-level recording assumes that all calls handled by a given individual should be recorded. In practice, that is often not the case.

An agent may participate in:

• Regulated client conversations
• Internal collaboration calls
• Operational discussions
• Training sessions
• Informal team communications

Recording every conversation may be unnecessary or even undesirable. Attempting to filter out non-recordable calls at the user level can become complex, particularly when the same individual handles both regulated and non-regulated interactions.

This creates a mismatch between the business logic and the technical enforcement model. The underlying requirement is usually simple: calls handled by a specific team or business function should be recorded. Tying recording to individuals instead of workflows makes that requirement harder to enforce consistently.

Moving Recording Responsibility to the Queue

Compliance recording for call queues shifts the control point from the individual to the operational workflow.

When recording is applied at the call queue level, any call handled through that queue is subject to recording. Individual user-level compliance recording policies are ignored for those calls. The recording decision is based on where the call is processed, not who answers it.

This approach aligns recording with the business function. If a queue represents a regulated advisory desk, a trading line, or a customer support function subject to quality monitoring, recording is applied consistently to calls entering that workflow – and only to those calls.

This also solves the problem of selective recording. Agents can continue to participate in internal calls or non-recordable conversations without those interactions being captured, while calls routed through designated queues are recorded as required.

Operationally, administration becomes simpler. Agents can rotate between queues without requiring policy adjustments for inbound queue calls. The recording boundary remains stable even as staffing structures evolve.

For regulated firms, this reduces the risk of inconsistent capture and unintended gaps. For organisations recording calls for quality assurance or operational oversight, it provides a cleaner and more targeted control model – one that reflects how teams and workflows are actually structured.

Recording Behaviour During Transfers and Consultations

Call flows rarely remain linear. Calls may be transferred, escalated, or placed into consultation.

With user-level recording, such movements can create edge cases. If a call is transferred to someone without the appropriate policy, recording behaviour may change unexpectedly.

With queue-level recording, recording is applied from the perspective of the call’s lifecycle. Once the call has entered a queue configured for recording, it remains recorded for the duration of that interaction, even if it is transferred or consulted with other users.

This ensures continuity of capture and avoids partial recordings that may undermine compliance, quality review, or evidential requirements.

Managing Recording Announcements

In some jurisdictions, callers must be informed that their call may be recorded. In other cases, organisations choose to provide notification as a matter of transparency.

When recording is tied to individual users, announcement behaviour can become inconsistent or duplicated.

With compliance recording for call queues, the notification can be handled directly in the queue greeting. The caller hears the announcement once, at the point of entering the recorded workflow. This creates a predictable and centrally managed notification model.

Configuring Compliance Recording for Call Queues

Configuration is currently performed using PowerShell.

A certified compliance recording bot must first be created as an application instance within the tenant. A compliance recording template is then defined, specifying how the recorder behaves during calls. That template is assigned directly to the call queue.

1. Create a Compliance Recording Bot Instance

New-CsOnlineApplicationInstance `
  -UserPrincipalName cr.bot@contoso.onmicrosoft.com `
  -DisplayName ComplianceRecordingBot `
  -ApplicationId <RecordingAppId>

New-CsOnlineApplicationInstance `
  -UserPrincipalName cr.bot@contoso.onmicrosoft.com `
  -DisplayName ComplianceRecordingBot `
  -ApplicationId <RecordingAppId>

Docs: New-CsOnlineApplicationInstance

2. Create a Compliance Recording Template

New-CsComplianceRecordingForCallQueueTemplate `
  -Name "QueueRecordingTemplate" `
  -BotApplicationInstanceObjectId <BotObjectId>
  -RequiredDuringCall $true

New-CsComplianceRecordingForCallQueueTemplate `
  -Name "QueueRecordingTemplate" `
  -BotApplicationInstanceObjectId <BotObjectId>
  -RequiredDuringCall $true

Templates define how the recorder behaves – for example, whether it must be present before the call connects and remain throughout the call.

Docs: New-CsComplianceRecordingForCallQueueTemplate

3. Assign the Template to a Call Queue

To list the first 100 call queues, run the following command:

Get-CsCallQueue | Select Name, Identity

Get-CsCallQueue | Select Name, Identity

Now you can assign the the compliance recording template to the call queue:

Set-CsCallQueue `
  -Identity <QueueId> `
  -ComplianceRecordingForCallQueueTemplateId @(<TemplateId>)<br>

Set-CsCallQueue `
  -Identity <QueueId> `
  -ComplianceRecordingForCallQueueTemplateId @(<TemplateId>)<br>

Once assigned, all calls handled by that queue are subject to compliance recording.

Docs: Get-CsCallQueue, Set-CsCallQueue

4. Configure the Recording Announcement

Set-CsCallQueue `
  -Identity <QueueId> `
  -TextAnnouncementForCR "This call may be recorded for compliance purposes."

Set-CsCallQueue `
  -Identity <QueueId> `
  -TextAnnouncementForCR "This call may be recorded for compliance purposes."

A failure announcement can also be configured if required.

Once configured, calls handled by that queue are recorded according to the template settings.

It is important to note that outbound calls made directly by agents are treated as user calls and still require user-level recording policies if they must be captured. Queue-level recording applies specifically to calls processed through the queue. Additionally, queues must be configured in conference mode for the feature to function.

Frequently Asked Questions

Final Thoughts

Microsoft Teams compliance recording for call queues does not change an organisation’s obligations. It does not determine whether calls must be recorded, nor why they are recorded.

What it changes is the control model.

By attaching recording to the queue – the point where business functions are defined and managed – Microsoft Teams aligns recording enforcement with operational structure. This reduces configuration complexity, improves consistency, and provides a clearer administrative boundary.

For organisations recording calls for compliance, quality assurance, training, or investigative purposes, this represents a more durable and maintainable approach.

In modern cloud-based contact centre environments, the queue defines the workflow. It is therefore a logical place for recording control to reside.

References

On this page

↑ Back to top