Bot-Free Notetaker for Microsoft Teams | Reline

If you have ever watched an AI notetaker get bounced out of a Microsoft Teams call — "this app is blocked by your organization" — you already know the problem. The notetaker tried to join the meeting as a bot, your tenant policy said no, and you ended up taking notes by hand anyway. Reline takes a different path: it never joins the meeting. Instead it records your microphone and the system audio playing through your computer, locally, while you sit in the call like any other participant. That single design choice is why it keeps working in tenants where bot-based tools quietly stop functioning. This post explains the policy shift driving the change, why join-the-call notetakers break, and how to capture a Teams meeting with Reline in a way that survives the block.

Microsoft is rolling out policies that can block third-party recording bots in Teams

Microsoft has been steadily tightening what third-party apps may do inside a Teams meeting. Tenant administrators can restrict which apps are permitted, block apps that request media access, and disable the "compliance recording" and meeting-bot surfaces that AI notetakers depend on to hear the room. In many enterprise tenants these controls are on by default now, and security teams are switching them on deliberately: a bot that joins your call is, from their point of view, an external recorder sitting inside a confidential conversation. The result is that an admin policy — not a missing feature — decides whether your notetaker works. You can install the slickest AI meeting tool on the market and still get nothing if your tenant says third-party bots are not allowed in. That is the wall a growing number of Teams users now hit, and it is the reason "does it need a bot?" has become the first question worth asking.

Why bot-based notetakers break under these policies (the bot cannot join)

A bot-based notetaker works by sending its own participant into the call. Tools like Otter join as a visible attendee — you see them in the participant list, and so does everyone else. To do that, the bot needs the meeting platform to admit it and grant it audio access. That is exactly the surface Teams policies clamp down on. When an admin blocks third-party apps or media-capable bots, the notetaker simply never gets a seat: it requests entry, the tenant refuses, and the recording never starts. There is no workaround inside the bot model, because the model itself depends on the one thing IT has decided to disallow. You can give the bot calendar access, you can pre-authorize it, you can pay for the enterprise tier — none of it matters if the policy says no external participant may join with media. The failure is structural, and it lands precisely on the calls that matter most: the regulated, confidential, high-stakes ones where IT locked the door in the first place.

Why local capture survives the block (Reline records audio on your device, nothing joins Teams)

Reline never asks Teams for anything. It records two audio streams straight from your own machine — your microphone (your voice) and the system audio your computer is already playing (everyone else, coming through your speakers). On macOS this uses the documented ScreenCaptureKit API; on Windows it uses WASAPI loopback. From Teams' perspective nothing changed: there is no extra participant, no app requesting media access, no entry for a tenant policy to deny. You are simply a person in a meeting whose laptop happens to be recording its own audio output, the same way a screen recording captures whatever is on your display. Because the capture lives entirely outside the meeting platform, the admin controls that stop bots have no surface to act on. That is the whole trick: it survives the block not by defeating the policy, but by never triggering it.

For a fuller walkthrough of how no-bot capture works across every platform, see /no-bot — it covers Zoom, Google Meet, and phone systems too, since the mechanism is identical regardless of what is playing through your speakers.

Step-by-step: record a Teams meeting with Reline

1. Download and open the Reline desktop app (macOS, Windows, or Linux) before your meeting starts. There is no web-conferencing plugin to install and nothing to add inside Teams.
2. Grant the one-time audio permission the first time you record — screen-and-system-audio access on macOS, or the loopback prompt on Windows. You only do this once per machine.
3. Join your Teams call normally, as yourself. On macOS, Reline can auto-detect that a meeting started and offer to record; otherwise hit record manually.
4. Speak as usual. Reline streams a live transcript while the call runs, mixing your mic with the system audio so both sides of the conversation are captured.
5. End the recording when the meeting wraps. Reline finalizes the transcript, generates a citation-backed summary, and saves the audio so you can scrub back through it later.
6. Share the note into a workspace or folder with the access controls you choose. The recording stays under your control, not a bot vendor’s.

Honest privacy scope: local capture, cloud transcription/storage/AI

We will not pretend the audio never leaves your device, because it does. What is local is the capture step: your mic and system audio are recorded on your own machine, and nothing joins the Teams call. Everything after that is cloud. The audio is sent to for transcription, the resulting recordings and transcripts are stored in cloud object storage (Cloudflare R2), and the summaries and chat answers are generated by cloud AI models. There is no on-device transcription and no on-device AI in Reline today. We are spelling this out because "bot-free" gets marketed as if it meant "fully private and offline," and it does not. The real, accurate claim is narrower and still useful: no third party joins your meeting, and your tenant’s anti-bot policy cannot block you. If your requirement is that audio physically never leave the machine, Reline is not that tool — and we would rather tell you now than have you find out in a security review.

What you get: multilingual transcript, Me-vs-Other labels, citation-backed summary, playback with click-to-seek

A captured Teams meeting turns into a note with a live, then finalized, transcript — in 60+ languages, with automatic language detection. Speakers are labeled as "Me" versus "Other," derived from which stream the audio came in on (your mic versus the system output) rather than named diarization, so you will not see "Sarah said" — you will see your side cleanly separated from everyone else’s. From there the summary is grounded: every claim links back to the transcript segment and timestamp that justifies it, so you can verify rather than trust. And the recording is fully playable — a timeline scrubber, click any line of transcript to seek the audio to that exact moment, and per-speaker isolation so you can replay just your side or just theirs. You can also chat with the recording, and the answers cite the timestamps they came from. See /product for the full picture of what each captured meeting becomes.

Consent and IT policy: notify participants and follow your org rules

Recording without a bot does not mean recording without consent. Because Reline does not announce itself in the participant list, the other people in the call will not automatically know you are capturing — which makes it your responsibility to tell them. Many jurisdictions (two-party-consent states in the US, much of the EU) legally require disclosure, and even where it is not required, a quick "I am taking AI notes on this, all good?" is good practice and usually welcomed. Just as important: the fact that your tenant’s bot block does not stop Reline is not the same as permission to ignore your organization’s recording policy. If IT blocked bots because the company prohibits recording certain meetings, capturing them locally is still against the rules. Treat the technical capability and the policy permission as two separate questions, and clear both before you hit record. This is especially true for the regulated, client-facing work where bot-free shines — which is exactly the audience we wrote /solutions/consultants for.

Download Reline and try it free

Reline runs on macOS, Windows, and Linux as a desktop app, plus a web app — notably wider than the Mac/Windows-only field most no-bot tools play in. There is no mobile app. The Free plan is $0 and enough to capture and review meetings. Professional is $15 per month (or $140 a year, about $12 a month) and Enterprise is $32 per month (about $26 a month annually) with SSO via WorkOS for Google and Microsoft and private-by-default, five-level access controls on notes and folders. See /pricing for the full breakdown, then download and record your next Teams call without waiting on a bot to be let in.

FAQ

Common questions

Will this work if my company blocks recording bots in Teams?

Yes. Reline does not join the meeting as a bot, so a Teams policy that blocks third-party recording bots does not stop it. Reline records your microphone and system audio locally instead. Always follow your organization’s recording policy.

Does Reline appear in the Teams participant list?

No. Nothing joins the meeting, so there is no bot in the attendee list and no has-joined notification from Reline.

Is the audio kept only on my device?

No. Capture is local, but the audio is transcribed in the cloud, stored in cloud storage, and summarized by cloud AI. Reline does not run on-device transcription or AI.

Which platforms are supported?

macOS, Windows, and Linux desktop apps, plus a web app. There is no mobile app.

What languages can it transcribe?

60+ languages, with automatic language detection — not English only.

Does Reline have SSO and admin controls for IT?

Reline supports SSO via WorkOS (Google and Microsoft). It does not currently advertise SAML/SCIM/Okta or SOC 2/HIPAA certification. Reline does offer private-by-default, 5-level access controls on notes and folders.