To translate speech in a Microsoft Teams meeting, use live translated captions where the meeting organizer or participant has eligible Teams Premium or Microsoft Copilot access. Open meeting caption settings, select the appropriate spoken language and choose Translate to for the target language where available. For a retained record, distinguish Teams live translated transcript views from the original transcript and any separate translated recap.
People searching for Microsoft Teams live translation, Teams translated captions, translate Teams meetings or Microsoft Teams translated transcript download need to understand eligibility and what is actually stored. A participant may read translated text during the call while the original-language transcript remains the stored source afterward.
This guide explains live caption controls, Teams Premium and Copilot licensing distinctions, multilingual speech recognition, Interpreter, meeting recap, technical vocabulary, permissions and practical accuracy checks. Specific features depend on current account settings and Microsoft documentation, not one universal button available to every user.
Quick answer: enable translated captions and confirm what is retained
Open the Teams meeting controls and choose captions and language settings. Use Translate to if the feature appears and the meeting is eligible. For post-meeting documentation, inspect the original transcript and supported recap outputs separately. Microsoft’s multilingual meetings guidance explains organizer and participant licensing rules and the distinction between live translated text and stored records.
Fifteen decisions that make Teams translation reliable
Turn on translated captions in a Teams meeting
In an eligible Microsoft Teams meeting, use More actions and the caption controls, then open the caption language settings and select Translate to or the appropriate target-language control. Microsoft’s multilingual meetings guide describes preferred spoken and translation languages, and its live caption help describes the available meeting controls. Interface steps can vary with Teams clients and updates.
Translated captions are a reading aid. The original spoken content can be misrecognized before it is translated, especially names, acronyms, quantities and overlapping dialogue. Ask a speaker to confirm high-impact details in chat or a verified document rather than treating live captions as an official agreement.
Understand what licenses let participants use translation
Microsoft currently documents live translated captions as a feature of Teams Premium or eligible Microsoft Copilot licensing. When a meeting organizer holds a qualifying license, all meeting participants can use translated captions without each purchasing that same license; if only an individual participant is licensed, access may be limited to that licensed participant. Admin policy and client capabilities still apply.
This organizer-versus-participant distinction matters before planning an international class or client meeting. Do not assume every Microsoft 365 plan grants every participant the feature. Confirm the real meeting organizer, license, language settings and administrative permissions, then run a test meeting with a person reading in the target language.
Separate basic captions, translation and multilingual recognition
Basic live captions recognize speech. Live translation provides a target-language rendering. Multilingual speech recognition can allow speakers to use several supported languages in one meeting and is associated with Teams Premium or eligible Copilot. Microsoft’s current multilingual recognition guide lists English, Spanish, French, German, Italian, Portuguese, Chinese, Japanese and Korean for that particular recognition feature.
Do not interpret the recognition list as the full list of possible translation targets. The supported sets can differ, as can licensing and availability. A participant reading a target language does not establish that the speaker can choose any source language without consequence. Verify both spoken and translated settings.
Interpreter is a separate speech-to-speech function
Microsoft’s Interpreter agent is designed for real-time speech-to-speech interpretation in supported languages under its licensing and organizational requirements. It is distinct from text captions and from the original audio recording. Some meetings may use live translated text, some may use interpretation audio, and some may combine features where supported.
When promoting a multilingual meeting, state what attendees can actually hear and read. A transcript translated into French does not create French audio, and Interpreter does not mean every recording will contain the interpreted voice. Microsoft documents original meeting audio as the recording source for this feature.
Understand live translated transcripts versus stored originals
Microsoft’s transcription help distinguishes live translated transcription from the underlying stored record. Its guidance states that past live translated transcript views are not stored by that basic workflow; the original meeting transcript is retained when transcription is enabled according to permissions. Other paid or admin-configured translation outputs may exist, but should not be assumed.
This is one of the most important facts for a reader searching ‘download Teams translated transcript’. Seeing a German translation live does not prove a permanently retained German transcript is waiting after the meeting. Check the actual recap and authorized export route, and clearly label any post-meeting translation created separately.
Multilingual recap and post-meeting availability
Microsoft describes translated recaps when multilingual speech recognition or Interpreter has been used and the meeting’s settings and eligible features support it. Its guidance also mentions admin-enabled transcript translations for some organizational workflows, which are not the same as saving a participant’s live caption scrollback.
For a final record, identify whether you have an original transcript, translated recap, authorized generated translation or manually reviewed document. Do not conflate these artifacts. Recap notes select and summarize; they need their own checking for actions, figures, attribution and unresolved discussion.
Before the call, verify the organizer and meeting settings
The meeting organizer or authorized staff should verify Teams Premium or Copilot eligibility where needed, the Enable multilingual speech recognition meeting option if appropriate, and transcript or recording permissions. A participant may control their preferred read language but not the entire tenant’s capture policy. This distinction determines whether a person can enable a feature or should ask the host.
Prepare a short technical and language test before an important meeting: one name, a numerical amount, an example term and a sample interaction. Confirm that attendees can see the correct target language and can still access audio. Do not rely on another organization’s screenshots or settings guide.
Protect the speaker’s authority and the action’s status
A project lead suggesting a timetable is not the same as the owner approving a new delivery date. In a multilingual Teams call, people may respond quickly and the captions may attribute a sentence to the previous speaker. For decisions, note actor, action, condition, due time and confirmation. If an approval is unclear, seek a written authorized statement.
Translated minutes should not assign tasks to the wrong participant or convert a discussion into unanimity. Make a clear action register for readers in each language, and preserve objections or unresolved questions when they affect implementation. A polished recap that changes authority is inaccurate.
Keep numbers, units and time zones together
Automatic speech transcription can confuse fifteen with fifty or omit a negative sign in a verbal instruction. A financial or technical meeting can be materially changed by one incorrect digit. Language formatting may also make decimal points and commas look unfamiliar. Preserve the numeric value, currency and unit without silently converting anything.
If people are in different time zones, anchor meeting schedules and deadlines to a confirmed date and named zone. An unqualified ‘tomorrow at 8’ is not a reliable international instruction when read later. Use actual calendar details and validate conversions separately.
Translate chat, screen sharing and slides as separate material
Live captions follow spoken meeting content; they do not automatically translate every cell of a shared spreadsheet, image-based instruction, slide annotation or message in the meeting chat. If the presenter says ‘look at the red series’ but the chart labels are in another language, the target reader may still need a translated figure legend.
Protect technical identifiers, software commands, file names and links. A target-language support summary should not translate code into invalid syntax. Keep the actual artifact and verified source facts accessible to authorized attendees so they can reconcile captions against what the presenter displayed.
Consent, retention and access are part of the workflow
Starting transcription, enabling a recap and allowing live captions are not identical data-handling actions. Some meetings involve private student discussions, legal documents, health information or confidential company strategy. Account policy and applicable rules determine who may start, stop, store or download records and whether participants need notice or consent.
Translation should not widen the permitted audience. Use the minimum necessary source material when creating target-language notes, and avoid sending private conversations to unapproved external tools. The existence of a recap link does not mean every user is authorized to redistribute its contents.
Make complex technical language verifiable
A Teams meeting may involve software architecture, scientific terminology, product model numbers or financial instruments. Speech recognition can invent a familiar-sounding expansion for an acronym. Translation then produces a coherent sentence about the wrong technology. Prepare a glossary and verify uncertain words against approved slides, docs and named speakers.
Keep model codes and version numbers exact. Where an experiment is preliminary, preserve its evidential status; where a product supports selected devices, do not say all devices. For health, safety or legal passages, qualified human review should precede consequential decisions.
Accessibility means participants can genuinely follow
Caption positioning, font size and presentation pace matter. Teams supports live caption settings and some caption pop-out functionality in eligible experiences. A line of translated text that covers an essential diagram may defeat the purpose of the feature even when words are correct.
Encourage speakers to take turns, avoid talking over colleagues and pause before important actions. Provide agendas and source documents in usable formats where appropriate. Human interpreting may be more suitable when detailed interaction cannot tolerate caption latency or recognition uncertainty.
Review the source recording or transcript when available
A translated transcript produced after the meeting should start from a verified authorized record rather than a guessed summary. Confirm speaker turns, numbers, dates, negation, quotes and the duration covered. A late participant might only have a partial live view even when the organization has a fuller source record.
Label the output carefully: original transcript, translated transcript, summary, or action list. A summary is not a verbatim quotation and should not be used to invent words a person never said. Store and share the result according to actual tenant permissions.
Use a decision-based multilingual quality test
Give a reader the approved target-language recap and ask what must happen next, who owns each item and which decisions still need approval. Compare those answers with the meeting’s authorized source. Any mismatch needs correction, not a prettier sentence.
For recurring multilingual meetings, maintain a verified terminology glossary and review lessons learned after major caption errors. Consistency develops through careful source checking, not through assuming one translation run proves future accuracy.
Main rule
Translate what actually happened, with the correct speaker and level of certainty. The presence of live text translation does not create an audio dub, authorize meeting retention or make an AI summary a verbatim transcript.
Official and related references: Microsoft Teams Multilingual Recognition · Teams Live Transcripts · Teams Interpreter · Google Meet Translation · Master Art of Translation.
Thirty-one worked cases in Microsoft Teams translation
These fictional situations show why translation quality must be tested against the real meeting and actual Teams capabilities, not merely the elegance of an AI-generated sentence. Each case protects a factual or procedural distinction that can matter to attendees.
1. The organizer has Premium but a guest does not
Situation: An international webinar is scheduled by a Teams Premium organizer, while a visiting participant has an ordinary Teams account.
Risk: Microsoft distinguishes organizer-licensed translation access from personally licensed access. Saying every viewer must purchase Premium may misstate the documented organizer-based eligibility; saying no license matters is equally unreliable.
What to verify: Verify the organizer’s actual entitlement and current meeting settings in a test call. Tell guests which target languages and controls work in that meeting rather than making blanket plan claims.
2. Only one attendee has a qualifying license
Situation: A regular Teams organizer invites several colleagues, while one attendee has an eligible Copilot or Premium license.
Risk: The individual may receive an available Translate to option without every unlicensed colleague receiving it. A translated announcement claiming universal access would disappoint others.
What to verify: Check the organizer and individual licensing scenario in Microsoft’s current documentation and test from both kinds of account before planning a mandatory multilingual session.
3. Multilingual recognition is mistaken for all-language support
Situation: A host reads that multilingual speech recognition supports nine languages and tells guests every possible language is accepted as spoken input.
Risk: The recognition language set and the target caption translation choices are distinct. Participants speaking unsupported dialects might receive poor transcription even if the target-language list seems broad.
What to verify: Identify actual supported speech and target languages separately, confirm the configured meeting options and provide alternative interpretation where a language pair is not supported.
4. Interpreter is mistaken for text captions
Situation: The team turns on an Interpreter audio feature and assumes all participants now have downloadable translated transcripts and dubbed recordings.
Risk: Speech-to-speech interpretation, live text translation and saved records are separate products with different output and licensing constraints.
What to verify: Tell users which languages they will hear, which captions they can read and which artifacts will exist afterward. Microsoft’s Interpreter guidance says recordings retain original meeting audio rather than interpreted audio.
5. A live translation is treated as a stored German transcript
Situation: A German-speaking attendee reads translated transcript lines during an English meeting and expects the exact German history to be saved after the call.
Risk: Microsoft’s basic translated-transcription guidance distinguishes live target text from the retained original transcript. A separate recap or paid post-processing capability might exist, but cannot be assumed.
What to verify: Find the actual authorized original transcript and create a reviewed translation as a separate deliverable when needed. Do not label an AI recap as an exact record of the live German lines.
6. A translated recap changes a decision
Situation: A meeting ends with a conditional proposal to start procurement after approval; the AI recap describes procurement as approved.
Risk: The target-language audience may place orders the decision-maker never authorized. This is a change of governance, not merely sentence style.
What to verify: Check the authorized original record and obtain the appropriate approval. Keep conditional, recommended, approved and completed as separate decision statuses in every language.
7. The wrong person is assigned an action
Situation: A department head asks Analyst A to assemble figures while Analyst B will prepare a summary. The generated notes swap the assignments.
Risk: Both tasks remain plausible in the target language, so a grammar review will not reveal why one employee receives the wrong task.
What to verify: Compare the action ledger to the original conversation and obtain confirmation where speaker attribution is uncertain. Retain task owner, deliverable, date and dependency.
8. An interruption changes who approved something
Situation: A manager begins to say ‘I agree’ but is immediately interrupted by another participant clarifying the conditions.
Risk: The auto-transcript may merge both voices into an unconditional approval made by the manager. The translated record could then falsely certify a sensitive decision.
What to verify: Review speaker turns and the interruption, or ask for a written decision. Preserve incomplete utterances or uncertainty rather than smoothing fragments into a firm commitment.
9. Fifteen is recognized as fifty
Situation: A speaker reports fifteen outstanding support tickets. Captions display fifty after noisy audio recognition.
Risk: A downstream translation faithfully renders the wrong source number, affecting workload and customer expectations.
What to verify: Use the verified ticket dashboard and ask the speaker to confirm the number. Correct the original transcript before producing a formal target-language status update.
10. A percentage loses its reference population
Situation: A researcher states that 18% of 200 respondents selected a particular answer. The translated summary retains 18% but omits 200.
Risk: Readers may infer a much larger or different surveyed population, giving an unsupported scope to the claim.
What to verify: Preserve denominator, sample period and what the percentage measures. Reconcile the target statement with the study table or approved presentation.
11. A price changes currency without conversion
Situation: A salesperson quotes a contract amount in Singapore dollars and a multilingual note substitutes the euro symbol before the same digits.
Risk: A symbol change without arithmetic conversion changes the apparent obligation and could mislead customers or procurement teams.
What to verify: Keep the original currency or use a separately approved rate, conversion date and rounding method. Do not let language translation make financial commitments on behalf of the parties.
12. An event begins at ten, but in whose time zone?
Situation: A Teams call includes colleagues in Singapore and California discussing a deadline for the following morning.
Risk: A translated note that says ‘tomorrow at ten your time’ can refer to multiple different calendar instants.
What to verify: Get an approved meeting date and named zone. Record the exact obligation and test two geographic interpretations before inviting people or assigning deadline-dependent work.
13. A proposed project delay is reported as final
Situation: A participant asks whether the delivery can move by one week. The chair says finance must first evaluate the consequences.
Risk: A translated recap may announce a new deadline because a question sounded like a decision.
What to verify: Keep the request and unresolved dependency. Only an authorized later confirmation should replace the existing project deadline.
14. A transcript started after the first decision
Situation: A host enables Teams transcription halfway through a meeting after the team has already adopted one resolution.
Risk: The saved original may omit the first decision, despite the later transcript looking complete over its actual capture period.
What to verify: Identify the start and stop times of the authorized record. Supplement early decisions only from appropriately confirmed notes, and do not claim the transcript covers speech that it did not capture.
15. A late joiner reads only translated conversation from arrival
Situation: An attendee joins after an hour and expects the live translated transcript pane to reconstruct all earlier target-language discussion.
Risk: Microsoft documents limitations to live translated transcript visibility when joining late. Past translated target lines are not necessarily stored and waiting.
What to verify: Provide a properly authorized approved recap of earlier agenda items. Do not infer complete history from the pane seen by one attendee.
16. A chat URL is translated like prose
Situation: During a support meeting, someone posts a repository URL with a long technical parameter string.
Risk: A translator substitutes familiar words into its path, leading to a nonexistent repository or a different issue.
What to verify: Keep literal URLs, issue IDs, filenames and code untouched. Translate explanatory labels, then open the final target link to confirm it reaches the intended resource.
17. A shared spreadsheet includes outdated figures
Situation: The presenter notices an old value on screen and orally provides a corrected amount.
Risk: Translated meeting notes built exclusively from the shared screen may preserve the wrong figure, while audio-only notes can omit useful context.
What to verify: Use a corrected authorized source table and note that an earlier slide was superseded. Check target notes and final file display the same verified number.
18. A transcript says a task is complete when still pending
Situation: The speaker says ‘We have not yet received supplier confirmation’ but caption punctuation or recognition drops ‘not yet’.
Risk: The target statement changes unresolved procurement into an achieved milestone, which can trigger premature next steps.
What to verify: Treat negative and pending phrases as a special review class. Ask the supplier owner to confirm the status and correct all affected meeting recaps.
19. The meeting uses unsupported overlapping speech
Situation: Two speakers debate technical specifications at the same time and recognition produces a single invented sentence.
Risk: The target may attribute a number or decision to someone who never said it, and translation can conceal the uncertainty behind fluent prose.
What to verify: Request turn-taking during consequential discussion, then verify ambiguous sections with authorized audio or follow-up emails before publishing.
20. A professional title is mistranslated
Situation: The presenter introduces an external adviser, while target notes call the person the company’s managing director.
Risk: This may imply decision-making authority and legal responsibility the adviser does not have.
What to verify: Keep the actual name and role. Verify professional titles from attendee records or direct confirmation, not a phonetic guess.
21. A medical statement is made too certain
Situation: A clinician says limited evidence suggests a potential benefit for selected patients, but the translation announces a universal proven cure.
Risk: The evidentiary status, population and certainty are all wrong, which can affect patient or policy decisions.
What to verify: Preserve trial size, conditional language and scope; use qualified clinical review for consequential passages. Machine captioning is not medical certification.
22. An interpreter voice is absent from the recording
Situation: A multilingual session uses real-time interpretation to help a participant hear another language.
Risk: Afterward, the team advertises the Teams recording as having every participant’s interpreted audio tracks.
What to verify: Microsoft’s documented Interpreter limitations mean original meeting audio is the captured recording source. Do not promise a translated audio archive if none was produced.
23. A participant chooses the wrong spoken-language setting
Situation: A Japanese speaker’s client is configured to recognize English speech while they deliver a long Japanese explanation.
Risk: Recognition may produce meaningless text that downstream translation makes deceptively grammatical.
What to verify: Verify the meeting and individual spoken-language settings where supported. Test a sentence containing a name, figure and technical concept before high-stakes discussion.
24. A chat message is mistaken for a formal vote
Situation: During a planning meeting, several participants react to a suggestion with emoji while formal approval has not occurred.
Risk: A translated AI summary may count reactions as unanimous official consent.
What to verify: Maintain the formal approval mechanism and the authority required for a decision. Reactions can be meaningful but do not automatically define contractual or governance outcomes.
25. A customer account number appears in a public summary
Situation: A private Teams meeting discusses support cases with customer IDs and contact details.
Risk: Copying the full translated transcript into a public report can expose information to a wider audience, regardless of language quality.
What to verify: Use authorized access controls and redact extraneous personal information. A concise public-facing status can preserve service meaning without publishing private identifiers.
26. An unlicensed user receives an inaccurate setup guide
Situation: A participant without the translation feature is told to find Translate to in a menu that does not appear for their account.
Risk: The person may waste the first part of the meeting troubleshooting a capability they cannot enable.
What to verify: Check license and organizer configuration first; offer a qualified alternative such as an interpreter or prepared bilingual notes rather than inventing a universal button path.
27. A pop-out caption covers an essential graph
Situation: A viewer expands live captions to improve readability but the floating window hides the bottom axis of a shared diagram.
Risk: A technically accurate sentence is not useful when it conceals the visual evidence the speaker is explaining.
What to verify: Use caption layout customization, reposition supported pop-out windows or share the chart separately. Verify full comprehension at the screen size the attendee uses.
28. A channel meeting lacks a specific option
Situation: An organizer expects a feature documented for ordinary Teams meetings to work identically during a channel meeting or town hall.
Risk: Microsoft notes feature differences among meeting types, including limitations for some multilingual recognition configurations.
What to verify: Verify the actual event type and current supported options. Do not conflate a standard meeting, webinar and town hall in documentation for multilingual guests.
29. A deadline includes a conditional dependency
Situation: The team agrees to deliver a report Friday provided external audit data arrives Wednesday.
Risk: The translated task list says Friday is guaranteed without mentioning the audit dependency.
What to verify: Retain the condition and identify who must confirm it. A target-language reader should know whether late source data changes the commitment.
30. An AI-generated recap is quoted as someone’s words
Situation: A manager’s nuanced suggestion is paraphrased by the recap, then quoted in another language as an exact transcript.
Risk: The new quotation attributes words the speaker never said and can change tone or meaning in a professional dispute.
What to verify: Keep summary prose labelled as editorial. Use verified original speech for direct quotations and explain any authorized corrections separately.
31. A translated document becomes stale after an update
Situation: The organizer changes next week’s meeting time in the source notes but forgets the secondary-language version distributed by email.
Risk: Different audiences receive different actionable schedules and may miss the meeting.
What to verify: Maintain a release version and identify which fields changed, then update all approved target copies or issue a clear correction. Translation quality includes maintenance.
A practical Microsoft Teams multilingual workflow
Confirm the actual meeting environment
Check who is the organizer, which Teams plan and Copilot or Premium licenses are involved, whether an administrator allows translation, what languages will be spoken and what type of meeting will occur. Test with a target-language guest before the official session.
Choose which language service attendees need
Live captions, translated captions, multilingual recognition, Interpreter audio, original transcripts and translated recaps serve different purposes. Explain them in the invitation so guests know what will be readable, audible and retained.
Prepare names, terms and figures
Collect a short verified glossary with speaker names, product codes, project acronyms, key amounts and event time zones. Display consequential figures in writing. Ask participants to speak clearly and take turns for decisions.
Run the session with visible authority
Identify the chair or decision-maker, clarify when a suggestion becomes approved and record conditions and unresolved questions. Do not rely on automatically translated reactions as a formal vote.
Validate the post-meeting source
If an authorized transcript exists, check its capture interval, speakers, numbers, negation and timestamps against allowed evidence. Distinguish original transcript, AI recap and any translated target summary; do not call them interchangeable.
Publish an action-oriented target deliverable
Use a clearly marked action list with owner, task, date, dependency and status. Confirm consequential changes with the people responsible and share through authorized access controls. Keep target versions updated when decisions change.
Frequently asked questions
How do I translate live captions in Microsoft Teams?
In an eligible meeting, open the caption language controls and use Translate to for an available language. The interface and licensing conditions depend on the actual tenant and meeting.
Does every Teams attendee need Premium?
Microsoft’s current guidance distinguishes organizer-held eligibility, which may enable participants broadly, from individually licensed attendees. Confirm actual license and admin policy.
Can Microsoft 365 Copilot support translation?
Microsoft describes eligible Copilot licensing for translated captions and multilingual speech recognition, subject to account and feature requirements.
Is Interpreter the same as translated captions?
No. Interpreter is speech-to-speech interpretation; translated captions are text. The saved recording may contain only original audio.
Can Teams translate multiple spoken languages?
Eligible multilingual speech recognition supports a documented set of source languages and meeting configurations. Check specific support; translation targets and recognition languages are distinct.
Will Teams save all translated transcript text?
Do not assume so. Microsoft documents that live translated transcripts are temporary and the original transcript is the standard stored record, with separate post-meeting translation features in some organizations.
What if the Translate to option is missing?
Check organizer and participant licensing, administrative permissions, client and language support, then ask the host. Do not invent an interface step.
Can AI recaps serve as verbatim legal records?
A generated recap is editorial and may omit, paraphrase or misattribute speech. For consequential quotations or decisions, review approved primary evidence.
Why should numbers be independently checked?
Automatic recognition can confuse quantities, currency units and dates. A natural target sentence does not prove the number is correct.
What is the ultimate accuracy test?
A reader relying on the target version should identify the same actual speaker, decision, owner, deadline and condition as someone with the authorized source record.
Final Teams translation checklist
Review the organizer’s licensing, correct meeting type, available languages, caption controls, actual recording and retention rights, source audio, technical glossary, participant identities, amounts, time zones, privacy, action ownership and exact decision status. Distinguish real-time translation, Interpreter, stored transcript and AI recap. Where translation creates uncertainty, seek human confirmation rather than presenting a machine result as formal approval.
Official references and further reading: Teams Multilingual Speech Recognition · Teams Transcription · Teams Interpreter · Google Meet Translation · Master Art of Translation.
Troubleshooting when translated captions are missing
When Translate to does not appear, troubleshoot in a reliable order. First confirm you joined the intended meeting using the expected account and not a different guest identity. Then ask the organizer whether their eligible Teams Premium or Copilot license and administrative settings support translation in that meeting. Check whether the meeting type allows the desired feature, whether the spoken language is configured correctly, and whether your app provides the current caption controls. Distinguish missing live captions from missing live translation; both may have different causes. A guide should not advise buying a particular subscription unless eligibility for the real use case has been verified with Microsoft or the organization’s administrator.
If translated text appears but seems nonsensical, check the audio source before rewriting it. Can participants hear the speaker clearly? Is the selected spoken language correct? Are several people talking at once? Does the specialist vocabulary appear on a shared slide or a glossary? Try a short test sentence containing a clear name and number, then ask the speaker to confirm any uncertainty in writing. Changing only the target language cannot fix source transcription that has recognized the wrong content.
What to distribute after a multilingual Teams meeting
For everyday teamwork, a concise approved decision list may be more useful than a raw transcript. Include the meeting date, time zone, decisions actually adopted, actions, owners, due dates, dependencies and questions still open. Identify the source and who approved the summary. When a true transcript is required, retain the original under the meeting’s authorized access controls, then commission or review its target-language translation separately. Mark editorial paraphrases as paraphrases rather than presenting them as verbatim quotations. This helps the team communicate accurately without promising that live translated caption history is stored indefinitely or visible to everyone.