What changed
Third-party bots joining Teams meetings for the purpose of recording are restricted. The mechanism matters more than the headline: the restriction targets the pattern of an unmanaged participant capturing media, not the idea of transcription. Microsoft’s own recording, compliance recording, and anything running inside the tenant’s trust boundary are unaffected.
The motivation is not hard to read. A meeting bot that joins on a calendar invitation, captures everything said, and ships it to a third-party cloud is a data-governance problem for the tenant administrator who never approved it. Several vendors in this category have taken sustained criticism over exactly that.
Path one: compliance recording
Compliance recording is a first-class Teams capability. A recording policy is assigned to users by a tenant administrator, and a certified recorder receives the media stream through a supported interface. It is explicitly outside the restriction because it is invoked by the tenant, not by a participant.
What it costs you is the sales motion:
- It needs a tenant administrator to assign a policy, so an individual user cannot adopt it on their own.
- The recorder has to be certified, which is a process rather than an afternoon.
- It is usually deployed org-wide, which makes it a procurement decision rather than a trial.
For regulated buyers in finance, healthcare and the public sector, none of that is a downside. It is what they were going to ask for anyway.
Path two: client-side capture
Record the meeting from the machine of somebody who is already in it. No extra participant, no policy, no tenant onboarding. Audio comes from the browser tab or from the operating system’s audio graph, and the transcription happens afterwards exactly as before.
This is the path most notetaker vendors are moving to for Teams, and it has a genuine advantage beyond compliance: it works for the meeting that was never on a calendar, and for the half of a conversation that happens after the formal call ends.
It also has a real limitation. It captures what the recording user’s machine can hear. If they drop off, the recording stops.
What to ask a vendor
- 1Which capture path do you use for Teams specifically: compliance recording, client-side capture, or a participant bot?
- 2If it is a bot, what is your plan for the restriction, and what is the date on it?
- 3Does Teams support degrade differently from Google Meet support in your product? It almost certainly does; a vendor that says otherwise has not looked.
- 4Where is the audio processed, and does it leave the region the tenant is in?
The fourth question catches something unrelated to Microsoft and more consequential for most European buyers: nearly every product in this category sends audio to a speech-to-text provider in the United States, whatever region the application servers are pinned to.
Where NeurTask is
Honestly: Teams works today through a participant bot, and we treat that path as at risk rather than settled. Browser capture is available now and is the option we would point a Teams-first team at. Compliance recording is on the roadmap and is not built, which is worth knowing before rather than after.