Control 4.3: Copilot in Teams Phone and Queues Governance — Verification & Testing
Test cases and evidence collection procedures for Copilot governance in Teams Phone and call queues.
Test Cases
Test 1: Call Transcription and Summary Generation
- Objective: Verify that Copilot generates accurate call summaries with transcription
- Steps:
- Place a test call using Teams Phone with a Copilot-enabled user.
- Discuss predefined test content (e.g., account review, product inquiry).
- End the call and wait for Copilot to generate the call summary.
- Review the summary for accuracy, completeness, and appropriate detail level.
- Expected Result: Call summary accurately reflects the conversation content with key topics and action items.
- Evidence: Call summary output with comparison to the actual conversation content.
Test 2: Call Summary Access Controls
- Objective: Confirm that call summaries are only accessible to authorized parties
- Steps:
- Generate a call summary from a test client call.
- Verify only the call participants can access the summary.
- Verify the supervisor has appropriate oversight access.
- Confirm external callers do not receive the AI-generated summary.
- Expected Result: Call summaries are restricted to authorized internal users only.
- Evidence: Access permissions documentation for call summary storage.
Test 3: Transcript/Artifact Compliance Coverage
- Objective: Validate whether tenant DLP, retention, eDiscovery, or Communication Compliance policies cover call transcripts and Copilot call artifacts
- Steps:
- Place a test call and verbally mention test sensitive data (test SSN, account number).
- Wait for transcription to complete.
- Verify which compliance policies detect the sensitive information in the transcript or artifact.
- Document unsupported artifact types as gaps rather than assuming DLP coverage.
- Expected Result: Tenant evidence shows which transcript/artifact types are covered and which require compensating controls.
- Evidence: Policy match, eDiscovery result, or documented unsupported-path finding.
Test 4: Teams Phone Agent / Queue Scope Verification
- Objective: Verify ordinary queue-agent policy inheritance and, where preview is enabled, Teams Phone Agent behavior
- Steps:
- Route a test call through a configured call queue.
- Have an agent answer the call and verify the agent's calling policy controls Teams Phone Copilot availability.
- If using Teams Phone Agent, verify the voice-agent handoff, tags, escalation path, and artifact capture.
- After the call, verify which summaries/artifacts are generated and who can access them.
- Expected Result: Queue behavior, Teams Phone Copilot availability, and any Teams Phone Agent artifacts match the approved tenant design.
- Evidence: Agent experience screenshots, policy export, and artifact access evidence.
Evidence Collection
| Evidence Item |
Source |
Format |
Retention |
| Calling policy configuration |
Teams Admin Center |
Screenshot |
With control documentation |
| Call summary samples |
Teams Phone |
Redacted screenshots |
Per retention policy |
| Compliance coverage results |
Purview / Teams / eDiscovery |
CSV or screenshot |
Per firm-approved records schedule |
| Queue configuration |
Teams Admin Center |
Screenshot |
With control documentation |
Compliance Mapping
| Regulation |
Requirement |
How This Control Helps |
| FINRA 3110 |
Phone communication supervision |
Supports compliance with supervisory review of phone-based interactions |
| SEC 17a-4 |
Communication record retention |
Can support firm-defined controls for record retention for AI-summarized phone communications |
| FINRA 4511 |
Books-and-records for communications |
Supports record-keeping of AI-generated call summaries |
Next Steps