Published April 10, 2026 · Last reviewed April 10, 2026 · EvalSuite Team
EvalSuite for Microsoft Teams: Capture, Assign Later, and Reassign
This guide explains the current Teams capture contract clearly: what is supported today, what still requires Microsoft-side setup, and what EvalSuite does not claim yet.
Audience
Managers, org admins, and Microsoft 365 operators who want transparent Teams capture expectations before rollout.
Open Support · Read calendar guide · Read Capture Inbox guide
Current Teams requirements
Microsoft connection
Use a connected Microsoft work or school account in EvalSuite so organizer-linked Teams capture can resolve into the right workspace.
Manager or org-admin access
Later assignment and reassignment happen in the manager/admin Capture Inbox, not from a teammate self-service flow.
Teams capture availability
What EvalSuite resolves depends on the Teams transcript, recording, or live-capture artifacts Microsoft makes available for that organizer and meeting.
Before you start
EvalSuite supports Teams after-the-fact capture resolution today, but it does not currently claim Teams as a fully shipped meeting provider for creating and hosting meetings directly from EvalSuite.
That means the Microsoft/Teams contract is clear: scheduling and join-link creation are different from capture resolution. Teams capture can still become useful meeting memory in EvalSuite even when the meeting was not created inside EvalSuite.
- Supported today: later assignment to completed 1:1s, historical 1:1 creation, assignment to existing sync occurrences, historical sync creation, and reassignment.
- Not promised today: Teams-native meeting-provider scheduling or join-link creation from EvalSuite.
- If EvalSuite can identify the organizer or meeting context but not the exact target meeting yet, the artifact lands in Capture Inbox instead of being dropped.
Connect Microsoft first
Use the Microsoft calendar connection when the meeting organizer works through Microsoft 365 and you want EvalSuite to recognize the organizer and related event context.
- Open `Settings -> Integrations -> Calendar` in EvalSuite.
- Connect the Microsoft Calendar account for the organizer or manager who owns the Teams meetings.
- Return to EvalSuite and confirm the connection shows `Connected` before depending on Teams capture resolution.
Assign Teams capture later
Use this when a Teams transcript, recording, or live capture reaches EvalSuite but the final 1:1 or sync target was not obvious up front.
- Teams uses the same later-assignment path as Zoom once the capture is in EvalSuite.
- You do not need to force every Teams call through EvalSuite scheduling just to keep the capture usable later.
- Open `/capture-inbox` and stay on `Unassigned`.
- Find the Teams item and choose `Resolve`.
- Attach it to an existing completed 1:1 or sync occurrence, or create the historical meeting from the captured session.
Reassign or create historical meetings
Use reassignment when the first meeting target was wrong, or historical creation when the right EvalSuite meeting did not exist yet.
- Reassignment writes a new active assignment and keeps the old attachment audit-visible.
- Historical sync creation supports either an existing standing sync or an ad hoc past sync.
- Active transcript and evidence reads follow the latest active Teams assignment after the move.
Troubleshooting and support
Use Support if the Microsoft connection is healthy but Teams capture still never lands in the Capture Inbox, or if you need help separating Teams capture behavior from Microsoft calendar behavior.
- General support and FAQs: `/help`
- Microsoft calendar setup: `/docs/calendar-connections-google-microsoft-and-ical`
- Capture Inbox workflow: `/docs/capture-inbox-assign-later-and-reassign`
Need help with a Teams rollout decision?
Open Support if you need to confirm whether your current Microsoft setup is sufficient for Teams capture resolution inside EvalSuite.