Testing Copilot and agents in Teams
Test Teams Copilot with your licences, meeting policies, transcripts and agent permissions, and verify summaries before using them as work records.

Copilot can help summarize material and propose follow-up work in Teams, but the result depends on the feature, licence, policy and content available. A meeting assistant and an agent connected to another system don’t have the same scope.
Use a fictional meeting and test accounts to check the behaviour before relying on it for business records. Keep sensitive conversations outside the initial trial.
Confirm the feature you plan to use
Ask IT to confirm which licences and settings the pilot users have. A Teams subscription, Teams Premium, Copilot Chat and Microsoft 365 Copilot aren’t interchangeable entitlements.
Microsoft’s Teams AI overview distinguishes built-in features, Copilot and other AI tools. Check current documentation and the tenant’s configuration. Feature lists in older articles go out of date quickly.
Record whether the trial is for meeting assistance, chat summaries or a specific agent. Define the intended input and output for each.
Test during-meeting and after-meeting behaviour
Create an internal test meeting with a known agenda, fictional decisions and a deliberately unresolved question. Check what the assistant can answer while the meeting runs and after it ends.
Microsoft’s meeting-policy documentation distinguishes using Copilot only during a meeting from use with a saved transcript. Verify the organizer’s options and the administrator policy together.
Don’t assume turning off recording disables every AI feature. Test the selected configuration explicitly, including who can start it.
Check where records remain
List the transcript, meeting chat, generated notes, exported documents and any shared workspace the trial creates. Verify access with an ordinary participant and a person who wasn’t invited.
Microsoft’s guidance on use without transcription says prompts and responses may still be retained under organizational policies. Information can still be kept with the transcript turned off.
The meeting-note access guide covers the wider privacy review. Tell participants before the meeting how Copilot will be used.
Review the proposed record
Compare the summary with the known discussion. Check decisions, names, qualifications and anything attributed to a person. Ask whether the unresolved question was incorrectly presented as settled.
Have a participant confirm action owners and dates. A suggested task doesn’t mean anyone has taken it on, or that it’s in the right system. Once the notes are confirmed, save them where the team keeps meeting records.
Review an agent’s access separately
Before adding an agent, identify its owner, knowledge sources, connectors and permitted actions. Check its use of shared information and any external service. Microsoft’s agent-management guidance describes administrative controls.
Test read access and action limits using fictional records. Verify how an agent is disabled and how a failed action is reported. A Teams conversation shouldn’t be able to set off purchases, account changes or external messages without a person signing off.
Keep the pilot bounded
Record quality, correction effort, feature costs and outstanding limitations. Roll out only the workflow you tested, with a named owner and fallback. Recheck when licences, policies, connected services or feature behaviour change.


