Does Teams Use Read AI? How to Connect It
Read AI is a meeting intelligence tool that can join Microsoft Teams calls to generate transcripts, summaries and follow-up items. Here is how the connection works, what participant consent requires, and how to review its outputs before acting on them.
Updated 5 min read
Read AI works with Microsoft Teams by joining meetings as a bot, which records audio, generates a transcript and produces a meeting summary with action items afterward. Teams does not bundle Read AI; it is a separate product that you connect to your Teams account. A tool like fenbs gives you a place to store the decisions and source links that come out of those meetings, so the next assistant or team member can find what was agreed without reopening a recording.
How Read AI connects to Microsoft Teams
Read AI joins a Teams meeting as a bot participant. When a meeting starts, the bot receives an invitation, joins the call and begins recording audio for transcription. It does not require a Microsoft 365 admin to install a Teams app for the whole organization; individual users can connect their Read AI account to their calendar, which allows the bot to join meetings they organize.
Check Read AI's help center (opens in a new tab) for current setup instructions, since the connection steps and available permissions change as both products update. The general flow is: sign in to Read AI, connect your Microsoft account, and set the bot to auto-join or to join only when manually invited.
How to connect Read AI to Teams
- Create a Read AI account at read.ai if you do not already have one.
- In Read AI's settings, connect your Microsoft account to give Read AI access to your Teams calendar.
- Choose whether the bot joins meetings automatically or only when invited. For automatic joining, Read AI reads your calendar and sends the bot to every Teams meeting. For manual joining, you invite the bot by adding it to a specific meeting.
- Before the next meeting, confirm the bot is set to notify participants when it joins. Read AI shows a visual indicator in the Teams call when the bot is present.
- After the meeting, log in to Read AI to view the transcript, summary and action items. Check them before forwarding to participants.
Participant consent and privacy
Recording a meeting requires that participants know it is happening. Read AI displays a notification in Teams when the bot joins, which informs participants that the call is being recorded. Depending on your state and the states of other participants, consent requirements vary: check the rules that apply to your location and your organization's policies before enabling automatic recording.
If a participant does not consent, they should be able to continue the meeting without being recorded. Consider setting the bot to join only when you have confirmed consent in advance, rather than auto-joining every call. Some organizations use a standard notice in meeting invitations that describes the recording practice.
For Teams used in a professional context with external clients — in law, finance or healthcare — check whether recording practices need to align with your professional obligations. Many professional associations publish guidance on AI transcription in client meetings.
Review Read AI outputs before acting on them
Transcripts from meeting bots are rarely perfect. Technical terms, proper nouns and cross-talk between speakers introduce errors. Read the transcript alongside the AI-generated summary rather than treating the summary as a definitive record of what was said.
Action items extracted by Read AI are useful as a starting list, but they benefit from a human review before they become tasks or commitments. An AI may extract an item from a hypothetical discussion or miss the context that made something conditional. Confirm the action items against your memory of the call before forwarding them.
Keep meeting source links and accepted decisions in one place
After reviewing a Read AI summary, record the decisions that were made and the links to the relevant recordings or summaries in fenbs. Links and listings keeps the source alongside the decision so the next assistant or team member can find both. Where we left off records what was agreed and what comes next. fenbs does not connect to Read AI; it keeps the record of what matters after the meeting.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
When Read AI is not the right fit
Read AI is a good fit for recurring meetings where a searchable transcript and action item list save time. It is less suited to sensitive discussions where participants would prefer no recording, to highly technical conversations where the transcript quality is poor, or to very short calls where setup outweighs the benefit.
If your team needs AI for strategy or adoption questions beyond meeting notes, see the guides on AI strategy for your team and AI adoption for your team.
How to do this with fenbs
- Create a free account and add a project for a recurring meeting series or working group.
- After each meeting, review the Read AI summary and action items. Add the confirmed decisions to fenbs as Decisions and rules, linking to the Read AI summary as the source.
- Add accepted action items as tasks in fenbs with their current status and who is responsible.
- Connect a supported AI assistant over MCP from Integrations. At the start of the next session, ask it to read the project context so it knows what was agreed in previous meetings.
- Use Where we left off on the project to record what was resolved in the last meeting and what the next meeting needs to address.
fenbs does not import Read AI data automatically. You add what is worth keeping — the decisions, not the entire transcript. For a broader view of tools that help teams work with AI assistance, see AI for teams.