Control 4.3: Copilot in Teams Phone and Queues Governance
Control ID: 4.3 Pillar: Operations & Monitoring Regulatory Reference: FINRA Rule 3110 (Supervision), FINRA Rule 4511 (Books and Records), GLBA §501(b), FFIEC IT Examination Handbook Last Verified: 2026-09-24 Governance Levels: Baseline / Recommended / Regulated
Objective
Establish governance controls for Microsoft Copilot in Teams Phone calls and Teams Phone Agent/Queues scenarios to support firm-defined call recording, supervisory review, and customer-data protection controls in financial services environments.
Why This Matters for FSI
Financial services organizations conduct a significant volume of customer interactions over the phone -- account inquiries, trade instructions, advisory consultations, complaints, and service requests. When Copilot is enabled for Teams Phone calls, it can provide in-call assistance and AI-generated summaries when the required calling policy, license, transcription, or recording conditions are met. Teams Phone Agent and Copilot Studio voice-agent integration are separate, preview/gated scenarios that can route callers to call queues and should be governed separately from ordinary call queue configuration.
For broker-dealer populations, counsel and compliance should determine whether Teams Phone transcripts, recordings, call recaps, Copilot interactions, or Teams Phone Agent transcripts are firm records and which supervisory workflow applies. Do not treat an AI-generated summary as a substitute for the firm's authoritative call recording or books-and-records process unless counsel and records owners approve that mapping.
For banking and other customer-facing populations, phone conversations can include sensitive customer information. Treat Copilot call processing, Teams Phone Agent flows, and any Copilot Studio voice-agent integration as customer-data processing paths that require firm privacy, security, and vendor-governance review.
Teams Phone Agent with Copilot Studio presents additional contact-center considerations. The feature is currently documented as Frontier Public Preview/gated by Microsoft, and Copilot Studio voice agents require explicit tenant enablement before the Teams Phone channel appears. Verify feature availability, licensing, supported regions, authentication design, and transfer targets in the tenant before adopting it.
Disclaimer
This control is provided for informational purposes only and does not constitute legal, regulatory, or compliance advice. See full disclaimer.
Regulatory Applicability
Regulatory citations identify commonly referenced requirements and control considerations. Applicability, record classification, supervisory-source mapping, retention periods, and evidence sufficiency are firm- and counsel-determined. This framework does not assert that any regulation applies to, or is satisfied by, a Microsoft 365 Copilot configuration.
Control Description
Copilot in Teams Phone
Copilot in Teams Phone provides the following capabilities that require governance:
| Feature | Description | Governance Concern |
|---|---|---|
| Call Summarization | AI-generated summary after call completion | Retention, accuracy, supervisory review |
| Voicemail Transcription | AI transcription of voicemail messages | Retention, accuracy, privacy |
| In-call assistance | Real-time Copilot prompts during eligible calls | Data access scope, user training, record boundary |
| Action items and follow-ups | Tasks or follow-ups generated from call context | Record accuracy, attribution |
| Transfer summary | AI-generated summary shown to the transferee when enabled before transfer | Consent, completeness, access boundary |
Teams Phone Agent and Queues
Current Microsoft Learn documentation distinguishes ordinary Call Queues/Queues app from Teams Phone Agent. Call queues route callers to representatives; Teams Phone Agent extends auto attendants with AI-driven conversations and can hand off to call queues or people. Copilot Studio voice agents can be attached to Teams Phone Agent through a gated preview integration.
| Feature | Description | Governance Concern |
|---|---|---|
| Teams Phone Agent | AI-driven, human-like voice conversations for screening calls, answering questions, managing appointments, and routing callers | Preview/gated availability, caller disclosure, escalation accuracy |
| Copilot Studio voice-agent handoff | Custom voice agents published to the Teams Phone channel and selected under Teams Admin Center > Voice > Templates & Resources > Agents and Queues | Tenant enablement, licensing, authentication, supported regions, transfer target validation |
| Call queues / Queues app | Native Teams Phone queue management, real-time metrics, historical reporting, and supervisor assist features | Manager access, privacy, retention of operational reports |
| Agent summary / call context | Summaries or transcript-derived context available only when supported and configured | Completeness, consent, retention, tenant verification |
Call Recording Governance
When Copilot processes phone calls, the underlying recording and transcription infrastructure must be governed:
- Recording Consent: Some jurisdictions require notification or consent for call recording/transcription; determine the applicable rule set with counsel.
- Recording and transcript availability: Copilot after-call access depends on the Teams calling policy and whether recording or transcription started during the call.
- Recording Access: Only authorized personnel should access call recordings, transcripts, recaps, and Copilot-generated content.
- Recording Retention: Retention periods must align with the firm's approved records schedule and tenant evidence of where each artifact is stored.
Supervisory Review of Call Summaries
For firms that classify Copilot-generated call summaries as supervised business communications, define supervisory review in firm policy:
- Call summaries should be captured in the firm's supervisory review system
- Reviewers should compare AI-generated summaries against actual recordings for accuracy sampling
- Supervisory review SLAs should account for the volume of Copilot-generated call summaries
Copilot Surface Coverage
| Surface | Coverage | Notes |
|---|---|---|
| Teams Phone - Inbound PSTN | Full | Call summary and voicemail transcription |
| Teams Phone - Outbound PSTN | Full | Call summary post-call |
| Teams Phone - VoIP | Full | Same capabilities as PSTN |
| Teams Phone Agent - Voice | Preview / tenant-gated | AI-driven caller interaction and Copilot Studio voice-agent handoff; verify tenant enablement |
| Call Queues / Queues app | Operational | Queue routing, supervisor assist, and queue analytics; no direct Set-CsCallQueue -Copilot parameter verified |
| Teams Phone - Voicemail | Full | Transcription and summarization |
| Teams Phone - Call Transfer | Partial | Summary may be incomplete for transferred calls |
Governance Levels
Baseline
-
Define which user groups have Copilot enabled for Teams Phone via calling policies — Copilot can run during PSTN and 1:1 VoIP calls, and after-call access depends on recording or transcription. The
-Copilotparameter onSet-CsTeamsCallingPolicycontrols call-Copilot availability (Enabledis the documented default;EnabledWithTranscriptrequires a licensed user to start transcription before Copilot is offered;Disabledturns Copilot off for calls). For FSI recordkeeping,EnabledWithTranscriptpaired with-AllowTranscriptionForCalling $trueis the recommended baseline so call Copilot only runs when a transcript is captured. Configure via Teams Admin Center > Voice > Calling policies:Set-CsTeamsCallingPolicy -Identity "FSI-Calling-Compliant" ` -Copilot "EnabledWithTranscript" ` -AllowCloudRecordingForCalls $true ` -AllowTranscriptionForCalling $true ` -LiveCaptionsEnabledTypeForCalling "DisabledUserOverride"Note: This policy governs Teams Phone calls (1:1 PSTN and VoIP). Teams meeting Copilot is governed separately via
Set-CsTeamsMeetingPolicy(see Control 4.2). -
Configure call recording policies to align with regulatory and jurisdictional consent requirements — Portal: Teams Admin Center > Voice > Compliance recording policies
- Verify in the tenant which storage locations and retention scopes cover call recordings, transcripts, Copilot recaps, transfer summaries, voicemail transcripts, and Teams Phone Agent artifacts
- Document the data flow for Copilot-processed call content (where stored, who can access it, how long it is retained, and which evidence proves the location)
- Confirm that call recording consent notifications are active for all jurisdictions where the firm operates
- Restrict access to Copilot call summaries to the call participants and their supervisors
- Verify call queue and Teams Phone Agent scope —
Set-CsCallQueuehas no direct Copilot parameter in current Learn syntax; ordinary queue agents inherit Teams Phone Copilot availability through their assigned calling policy. Teams Phone Agent / Copilot Studio voice-agent integration is a separate Frontier Public Preview/gated feature and must be verified in the tenant before use. Portal: Teams Admin Center > Voice > Call queues; Preview path: Voice > Templates & Resources > Agents and Queues - Confirm auto-attendant scope — standard auto attendants use configured menus and voice commands; Teams Phone Agent is the AI-driven option documented for conversational self-service and routing.
Recommended
- Implement supervisory review procedures for Copilot call summaries involving regulated activities
- Configure information barriers and source permissions so Teams Phone Agent or Copilot Studio voice-agent experiences cannot surface restricted content to unauthorized agents
- Establish accuracy sampling procedures — compare Copilot call summaries to actual recordings quarterly
- Create retention labels specific to call recordings, transcripts, summaries, and Teams Phone Agent artifacts with periods approved by records management and counsel; do not hard-code a regulatory duration until the firm maps each artifact to its books-and-records schedule.
- Monitor Copilot Teams Phone usage through admin reports to identify adoption patterns — verify calling policy enforcement:
Get-CsTeamsCallingPolicy -Identity "FSI-Calling-Compliant" | Select-Object Copilot, AllowCloudRecordingForCalls, AllowTranscriptionForCalling, LiveCaptionsEnabledTypeForCalling - Train agents and supervisors on the limitations of AI-generated call summaries
- Verify whether certified compliance recording providers can capture or reference Copilot call artifacts alongside native recordings; document any provider gap — Portal: Teams Admin Center > Voice > Compliance recording policies
Regulated
- Integrate Copilot call summaries into the firm's communication surveillance platform
- Implement automated flagging of call summaries containing trade instructions, complaints, or MNPI keywords
- Configure electronic-recordkeeping storage for call artifacts according to the firm-approved records schedule and counsel determination
- Conduct quarterly audits comparing Copilot call summaries to actual call content for accuracy validation
- Require firm-approved authoritative recording for compliance-critical call lines; verify whether certified providers capture or reference Copilot-generated artifacts
- Implement approved monitoring for Teams Phone Agent or Copilot Studio voice-agent suggestions in regulated scenarios, where those features are enabled
- Maintain detailed audit trail of all access to call recordings and Copilot summaries
- Apply the firm's approved electronic-recordkeeping retention schedule to call recordings, transcripts, recaps, Copilot interactions, and Teams Phone Agent artifacts; document counsel's determination rather than asserting that any specific regulation is satisfied.
Setup & Configuration
Step 1: Configure Teams Phone Copilot Policies
In Teams Admin Center > Voice > Calling Policies:
- Create or modify calling policies to control Copilot availability:
- Enable Copilot call summarization for licensed users
- Configure voicemail transcription settings
- Set call recording policies per regulatory requirements
- Assign policies to user groups based on role and regulatory exposure
Step 2: Configure Call Recording and Compliance
- Recording Policy: Teams Admin Center > Voice > Call Recording
- Enable compliance recording for regulated users
- Configure recording storage location
-
Set notification and consent requirements per jurisdiction
-
Compliance Recording Integration:
- For firms using third-party compliance recording (e.g., Verint, NICE), verify that Copilot summaries are captured alongside native recordings
- Document any gaps between Copilot processing and compliance recording
Step 3: Configure Retention for Call Content
In Microsoft Purview > Data Lifecycle Management:
- Create retention policies covering:
- Teams call recordings
- Call transcripts
- Copilot recaps, transfer summaries, and call summaries
- Voicemail transcriptions
- Teams Phone Agent and Copilot Studio voice-agent artifacts where enabled
- Set retention periods according to the firm-approved records schedule and counsel determination for each artifact type
Step 4: Configure Queues Agent Assist
In Teams Admin Center > Voice > Queues:
- Configure knowledge base sources for Copilot agent assist
- Verify that knowledge base content is appropriately classified and access-controlled
- Test that information barriers prevent cross-wall content from surfacing to restricted agents
- Configure agent assist response templates to include required disclaimers
Step 5: Configure Supervisory Review
For FINRA-regulated firms:
- In Microsoft Purview > Communication Compliance, extend policies to capture call summaries
- Define keywords and conditions that trigger supervisory review for call content
- Assign supervisory reviewers with appropriate authority
- Document review SLAs and escalation procedures
Financial Sector Considerations
Broker-Dealers: Counsel and records owners should determine which telephone communications and Copilot-derived artifacts are firm records. Firms should evaluate whether Copilot summaries supplement, but do not replace, existing call recording obligations unless approved as part of the authoritative records program.
Wealth Management: Advisory calls with high-net-worth clients frequently involve sensitive portfolio discussions. Copilot summaries of these calls should be reviewed for accuracy before being stored as part of the client record. Inaccurate AI summaries could create liability if they mischaracterize investment advice or client instructions.
Banking Contact Centers: Banks processing customer service calls through Teams Queues must verify that Copilot agent assist does not surface information that violates need-to-know principles. Customer data from one account should not be surfaced during a call about a different customer's account.
Insurance Contact Centers: Claims-related phone calls processed by Copilot may generate summaries that become part of the claims file. State insurance regulators may review these records during market conduct examinations. Verify that summaries accurately reflect the conversation and include appropriate caveats about AI generation.
Call Consent Requirements: Financial institutions operate across multiple jurisdictions with varying call recording consent laws. Some states require all-party consent for recording. Because retained after-call Copilot content depends on transcription or recording, firms must verify that consent notices cover recording, transcription, and AI processing where applicable.
Verification Criteria
| # | Verification Step | Expected Result |
|---|---|---|
| 1 | Review Teams calling policies for Copilot settings | Copilot enabled only for approved user groups |
| 2 | Verify call recording consent notifications | Notifications active and compliant with applicable jurisdictions |
| 3 | Confirm retention policies cover all call content types | Recordings, transcripts, summaries, and voicemails under retention |
| 4 | Test information barriers in Queues agent assist | Restricted content is not surfaced to barriered agents |
| 5 | Search eDiscovery for Copilot call summaries | Call summaries are discoverable and searchable |
| 6 | Review supervisory review queue for call summaries (Regulated) | Flagged call summaries appear in review queue within SLA |
| 7 | Verify accuracy sampling results from most recent quarter | Sampling completed and documented with findings |
| 8 | Confirm compliance recording integration captures Copilot artifacts | Third-party recording platform captures or references Copilot content |
Additional Resources
- Manage Microsoft Copilot in Teams calls
- Manage Microsoft Copilot for Teams phones
- Configure call recording, transcription, and captions in Teams
- Teams Compliance Recording
- Teams Call Queues
- Planning - Overview of voice applications
- Planning - Agents and Queues for Teams Phone Agent
- Integrate voice agents with Teams Phone Agent (preview)
- Set-CsTeamsCallingPolicy
- Set-CsCallQueue
- FINRA Rule 3110 - Supervision
- FINRA Rule 4511 - Books and Records
- GLBA §501(b) and Interagency Guidelines Establishing Information Security Standards
-
Implementation Playbooks: Portal Walkthrough · PowerShell Setup · Verification · Troubleshooting
-
Related Controls: 4.2 Teams Meetings Governance, 4.1 Admin Settings and Feature Management, 3.4 Communication Compliance, 3.1 Audit Logging
FSI Copilot Governance Framework v1.8.0 - July 2026