v2.4.0
Authenticated Microsoft Teams bots
- 2new
- 2improved
- 3fixed
Bots can now join Microsoft Teams meetings signed in as a real Microsoft account rather than as an anonymous guest, which gets them into meetings that refuse guests and names participants correctly. Teams speaker attribution was reworked in the same release.
New Features
- Authenticated Microsoft Teams bots. Register a workspace with
POST /v2/teams-workspacesand the accounts under it withPOST /v2/teams-logins, then send a bot withteams_config.credential_idto pin one account, orteams_config.email_groupto draw from a pool.teams_config.fallbackchooses what happens when no account is free:fail(default) oranonymous. See Authenticated bots for Teams. - Authenticated Teams bots join as the signed-in user, record with the bot's avatar on camera, stay muted on entry, and keep the chat rail out of the recording.
Improvements
- Teams transcripts attribute speech to the right participant far more reliably, using the meeting's own dominant-speaker signal rather than an indirect one that could latch onto whoever spoke first.
- Real-time transcription parameters are validated when the bot is created, so an unusable configuration is refused up front instead of failing silently mid-meeting. See Streaming.
Bug Fixes
- An authenticated Teams bot no longer falls back to joining as a guest after signing in successfully.
- A Teams sign-in that times out transiently is retried instead of failing the bot.
- A failed Teams bot releases its account back to the pool, instead of holding the slot permanently.