Teams transcription for SMEs: Who can read it, and where is the data?

After a video call, a searchable record suddenly appears. Names, statements and timestamps are neatly arranged. It feels like a finished set of minutes. That is the first misunderstanding: a Teams transcript is an automatically generated record of speech. It is not automatically complete, approved or legally binding.

It is still useful. Someone who joins late can catch up. A project lead can find a figure mentioned in passing. Microsoft 365 Copilot may summarise statements and suggest tasks, depending on licensing, meeting options and access. The value only lasts if the organisation can answer three questions: When do we transcribe? Who may see the result? When is it deleted?

A Swiss SME rarely needs a thirty-page policy for this. A short, understandable rule and correctly configured Microsoft 365 options are usually the better starting point.

Several features sit close together in the Teams menu, but their implications for privacy, storage and later use differ.

Microsoft explicitly describes live captions as temporary while transcription creates a written record. A recording is different again: it contains video and audio and uses considerably more storage. A meeting can be transcribed without recording video.

An AI summary is not a new source of truth. It condenses existing material and can inherit transcription errors or incorrect speaker attribution. Important decisions should still be recorded in controlled minutes or the relevant business system.

Microsoft: Manage transcription and captions

For an ordinary scheduled meeting, Teams saves the recording in the organiser’s OneDrive, in the Recordings folder. According to Microsoft, this applies even when the organiser did not attend. For a channel meeting, the recording is stored in the team’s SharePoint document library, again in a Recordings folder. Transcripts are managed with meeting recordings in OneDrive and SharePoint.

This matters because the transcript does not simply live “in Teams” as an isolated object. The Teams interface sits on top of familiar Microsoft 365 controls: ownership, sharing links, retention, search, eDiscovery and the lifecycle of OneDrive or SharePoint content.

One-to-one and group calls have different ownership rules: the recording normally lands in the OneDrive of the person who started it. Shared mailboxes and organisers without OneDrive trigger fallback rules. If you use meeting templates or functional mailboxes, run a test instead of inferring storage from the name on the calendar invitation.

“In Teams” is not a sufficient answer to the data question. The actual OneDrive or SharePoint location, its owner and effective permissions are what matter.

Microsoft: Teams recording and transcript storage and permissions

For an ordinary non-channel meeting, internal invitees generally receive access to the recording and related content. The organiser owns the file, while co-organisers have edit rights. External participants do not automatically receive access; the organiser must explicitly add them to the share.

Channel meetings inherit permissions from the channel and its SharePoint site. That is convenient, but it can be surprising: people who did not attend the conversation may be authorised because they are channel members. A confidential conversation should not be placed in a broadly populated standard channel simply because that is where the team normally works.

The visible participant list is not the whole permission review. A forwarded invitation, changed channel membership or additional file share may alter reach. Before a sensitive meeting, check the meeting options; afterwards, inspect the effective sharing of the stored content. “Invitees only” is a business expectation. The permission on the saved item shows whether it is technically true.

Teams visibly notifies participants when transcription or recording begins. That matters, but it does not replace a clear organisational rule. People should know why the transcript is being created, who will receive access and how long it will remain. For external calls, include this information in the invitation or at the start of the agenda.

The Swiss Data Protection Act includes principles such as proportionality, purpose limitation and transparency when processing personal data. The appropriate legal basis and additional obligations depend on context, including employment conversations, health data, professional secrecy or international participants. This article is not legal advice.

The practical conclusion is nevertheless straightforward: “record everything just in case” is a poor default. If a simple note meets the purpose, a verbatim transcript is unnecessary. When a transcript provides real value, state that purpose before starting it.

Swiss Federal Act on Data Protection · FDPIC: Data protection basics

The first is false precision. Dialects, specialist terms, names and changing speakers can produce errors. A neatly formatted sentence looks convincing even when one word is wrong. Anyone using a transcript for a quotation, employment decision or contractual commitment must verify the relevant passage.

The second is excessive retention. A transcript is easy to leave behind because it uses little storage and has no obvious owner. Yet it can be more revealing than video: text is quickly searched, copied and analysed by AI. An old sentence may later be misunderstood without its tone and situation.

The third is the organiser’s lifecycle. When content sits in one person’s OneDrive, the company must know what happens after a role change or departure. A properly governed Teams channel may suit recurring business-critical meetings, provided its membership is appropriate.

Finally, a Copilot summary must not become an invisible source of truth. The accountable people need to confirm tasks, decisions and dates. AI can prepare; the business process creates authority.

1. Define three meeting classes. “Normal” allows transcription where it has a clear purpose. “Confidential” requires a conscious organiser decision. “Highly sensitive”, including many HR, health or legal conversations, starts without transcription or recording unless a reviewed exception applies.

2. Name the purpose and owner. State in the invitation or at the beginning why the meeting is transcribed. The organiser owns access, quality checks and deletion. “For notes” is vague; “for project decisions and actions” can be reviewed.

3. Set retention. Choose a short default period for ordinary project transcripts that matches the business purpose. Move decisions to the authoritative system first. Legal or contractual duties may require a different period; document them as justified exceptions.

4. Make external sharing deliberate. An external guest does not automatically receive the transcript. Decide whether an approved summary is enough. If the original is shared, use named recipients and a suitable expiry date.

5. Test deletion and permissions. Use two test accounts to check who can see the recap, transcript and recording. Delete a test item and confirm the expected behaviour. A policy without tested technology remains an assumption.

Select two real but non-sensitive meeting types: an internal project meeting and a supplier call. Decide in advance whether transcription genuinely helps. Start it deliberately, explain it clearly, and then inspect storage, permissions, download options and the recap.

Move only confirmed decisions and tasks into the authoritative system, such as the project list, CRM or approved minutes. Then spend ten minutes comparing transcript and conversation. Which names and specialist terms were wrong? Who had access? Was the summary useful? This small test teaches more than a lengthy debate about theoretical capabilities.

Then configure the appropriate Teams meeting policy. Microsoft lets administrators control transcription through user or group policies. Additional controls, such as restrictions on copying and forwarding, may depend on Teams Premium. Licensing and interfaces change, so verify assigned plans before treating a feature as a mandatory safeguard.

Teams transcription can improve accessibility and reduce meeting follow-up. It is not a neutral convenience, however. It creates searchable content containing names, statements and context. That content sits in OneDrive or SharePoint, inherits specific permissions and needs a lifecycle.

The right rule is neither “always transcribe” nor “never transcribe”. Decide according to purpose and sensitivity. Inform people clearly, inspect actual access, move confirmed outcomes to the correct system and delete the raw record when its purpose has ended. That turns a useful button into a controlled working process.