Teams Meeting Shared Files: what the documentation states, and how a shared file becomes an answer in the meeting

On 8 September 2026 Microsoft added feature 570427 to the Microsoft 365 roadmap. The entry reads, in full:

The new Meeting Shared Files feature allows users to add relevant files and links to their meeting for easy access and to automatically share that content with all meeting participants. AI in the meeting, like the Facilitator agent, uses these files for targeted grounding to answer questions and enhance skill functionality.

It is a mechanic worth having. Files stop being messages that scroll away, and the AI in the room answers from the deck the room is actually looking at.

This post is two documented maps. First: what Microsoft's own pages say about the feature and about the AI that reads those files — the license it needs, the meetings it works in, who can switch it on, the language it answers in. Second: how the same job works in InterMIND today, mechanic by mechanic — a file dropped into the meeting, the summary that appears by itself, and Mia, the meeting's AI participant, answering questions grounded on that file aloud, each participant hearing her in their own language. Vendor facts are quoted from Microsoft's roadmap and support pages, checked September 2026; links are in the footer.

What the roadmap entry states

The roadmap row is the primary document, so it is worth reading as data rather than as an announcement. Fetched from Microsoft's roadmap API on 9 September 2026, feature 570427 carries:

Two things the entry does not state, as of the check: it names no access rule for participants who are not in the tenant, and it names no language behaviour for the shared content or for the AI answers grounded on it. The product tag "Microsoft Copilot (Microsoft 365)" is the entry's own; what that tag implies for licensing is documented elsewhere, on the Facilitator page.

The AI that reads the files is licensed and scoped

The roadmap entry names the Facilitator agent as the consumer of shared files. Microsoft's support page for Facilitator states the boundaries, and each of these is a quote:

The license. "A Microsoft Copilot license is required to add Facilitator to a meeting or turn it on during a meeting. However, any meeting participant (excluding external participants) can see all real-time updates in Chat and Notes."

The meeting types. "Facilitator can only be added to scheduled meetings, and can't be added to channel meetings, instant meetings, or Teams calls."

What it does with files. Among its listed features: "Create a high-quality word document based on the meeting discussion, chat history and shared files."

The condition for asking it afterwards. "To prompt Facilitator about the meeting after it ends, make sure to turn on transcription before or during the meeting. If Copilot is set to start without transcription, Facilitator will start without transcription as well."

Who can switch it on mid-meeting. "Only meeting participants who are organizers or presenters and are using Teams for web or desktop can turn Facilitator on or off during a meeting."

The language. "When you turn on Facilitator, you'll be asked to select a language if a language for the meeting hasn't already been selected." The selection is a property of the meeting, not of the person asking.

Microsoft also documents two cases where the agent cannot read what it was pointed at: when "only the organizer has joined," because "Facilitator can't read the organizer's copy of the meeting invite due to privacy requirements," and when the invite or notes carry a sensitivity label — "if the meeting invite or notes have a sensitivity label (such as Confidential or another label that requires encryption), Facilitator can't read or extract the agenda."

Two more documented facts from the same product family, because a shared file in a multilingual room meets them: the Interpreter agent page lists ten supported languages — "English, Spanish, Portuguese, Japanese, Simplified Chinese (Mandarin), Italian, German, French, Korean and Taiwanese" — with "20 hours of interpretation … included per person per month with a Microsoft Copilot license"; and the live-captions page states that "Teams doesn't save captions. If you'd like a transcript of the meeting, turn on transcription."

Put together, that is the documented picture as of September 2026: the file is shared with everyone; the AI that reads it needs a Copilot license, works in scheduled meetings only, is switched on by organizers or presenters, and answers in the one language selected for the meeting; external participants do not see its real-time updates in Chat and Notes.

How this works in InterMIND

Everything below is how the product works today, and each item is a mechanic rather than a claim about quality.

A file dropped into the meeting chat is read on your machine. When a document is attached in a meeting chat or a channel, its text is extracted in your browser — a Web Worker converts the file locally, up to 50 MB. Covered: DOC, DOCX, DOCM, ODT, RTF; PDF with a text layer; PPT, PPTX, PPSX, PPTM, ODP; XLS, XLSX, XLSM, ODS, CSV; TXT, MD, Markdown; EPUB. The file's text is not mailed to a third party to be parsed.

The summary is automatic — there is no button and no license. A moment after the file lands, the card's status strip flips from Preparing summary… to AI summary, with Preview next to it for the document itself. Nobody presses anything, nobody has to be the person who "runs the AI on it", and summaries carry no plan quota.

A question about the file gets an answer in the meeting, in each participant's language. Status, 19 September 2026: Mia in meetings is in preview — it is being tested inside InterMIND; any account can switch her on under Settings → Advanced after accepting the alpha terms (the Preview features page describes each one). What follows describes how she works in the preview. Mia is the organization's AI participant. Say «Mia, what delivery date is in the contract?» aloud, or switch the meeting chat to its private mode — the lock next to the message field — and write the question there, and she answers from the material of this session: the transcript so far, the chat, the summaries of the documents shared in it, and the recaps of the room's previous sessions. If the material does not contain the answer, she says so in one sentence rather than inventing a number. She answers licensed participants of paid plans — Pro, Business and Enterprise: a participant on a paid plan has her in every meeting they join, whoever hosts it. Guests and participants on the free plan hear her spoken answers to others, but she does not answer them. There is no AI add-on on top of the plan, no meeting type she cannot join, and nobody has to switch her on during the call — she runs whenever AI features are on for the host's organization.

The answer follows the question. Asked aloud, Mia answers aloud to the whole room: the answer is written natively in the language of the question and in every other language present in the room, and it is voiced on each participant's device in that participant's language; nothing is written to the chat. Asked in the private mode of the chat, she answers there only, in text, and nobody else in the room sees the exchange. Mia is not a participant of the call itself: she is not in the recording or the transcript, and her voice never crosses another participant's microphone. Start talking and she stops; Stop Mia cuts an answer short.

The answer runs on the gateway the host's organization chose. She uses the AI gateway the organization chose for all of its AI features — the default EU gateway or the organization's own endpoint — and the voice comes from that gateway's vendor. On an organization's own endpoint there is no voice, so a spoken question is answered as text in the meeting chat.

Every point in the summary is anchored to the document. The summary bullets are written against paragraph markers injected into the extracted text, so each bullet ends with a ¶ link that jumps to the exact source paragraph in the Extracted text tab. A claim in the summary is one click from the author's wording, and the extracted text is deliberately never translated, so the anchor always lands on the author's own words.

Each member reads the summary in their own language. The summary is written in the document's own language first, then served to each reader in that reader's meeting language and cached per language.

A document opened during the call arrives on every stage. A Google Docs or OneDrive document linked in the meeting chat can be opened for the whole conference — it appears on every participant's stage, labeled with who shared it, each viewer scrolls and zooms independently, and each viewer's client requests it in their own interface language. Rich-text notes go on the stage the same way, with Translated, Original and side-by-side views per reader.

The file's substance lands in the record with the same weight as speech. Documents shared during a session contribute their summaries to the meeting recap alongside what was said, and the recap prompt treats a figure or a decision stated in a document exactly like a spoken one. A session where nobody spoke but documents were shared still produces a recap.

Reading it requires being a member. The extracted text and the summary live only in our database, never in public file storage, and the route that serves them requires membership of that meeting or channel.

Translating the whole file is a separate, metered feature. Reading a shared PDF or Office file in your language — the document, not its summary — is document translation, covering 30 document languages, counted in distinct files over a rolling 30-day window: 10 on Pro, 30 on Business, 100 on Enterprise, and not available on Basic.

The per-pipeline numbers, because there is no single answer: 23 languages for voice and chat, 30 for documents, 17 interface locales.

Five limits worth stating plainly. An unauthenticated guest can be in the meeting, see the document on the stage and hear Mia's spoken answers about it, but Mia does not answer a guest's own questions, and the summary card belongs to a signed-in member — there is no account for it to belong to otherwise. A Google Drive or OneDrive link shares a pointer rather than the file, so there is no text on our side to extract, summarize or ask Mia about; the content stays with its provider. A scanned PDF has no text layer and is labeled as such rather than silently summarized — OCR is not performed. Files arriving from the mobile app or from the Telegram bridge aren't extracted yet. And Mia answers from a document's summary, not from its full text, so a detail the summary did not keep is a detail she will tell you she does not have.

Side by side

Documented facts from Microsoft's own pages, checked September 2026. Where a page doesn't state something, the cell says so.

Both columns tie the in-meeting AI to a paid entitlement of the person using it. The rows where the two sets of documentation differ are the meeting types, the in-call switch, who hears the answer, and the language of the answer.

If you're staying on Teams

Four things worth doing, all from the documentation above:

1. Check who in the meeting holds a Copilot license. The agent that reads shared files needs one to be added or switched on, and only organizers or presenters on Teams web or desktop can turn it on mid-meeting.
2. Schedule the meeting. Facilitator can't be added to channel meetings, instant meetings, or calls — if the file-grounded AI matters, the calendar invite is the entry point.
3. Turn transcription on before or during the call if anyone will want to ask about the meeting afterwards; Microsoft documents that as the condition.
4. Pick the meeting language deliberately. Facilitator answers in the one language selected for the meeting; participants outside the tenant don't see its real-time updates in Chat and Notes.

If most of the people the file was shared with can't ask about it — wrong meeting type, wrong tenant, wrong language — the file was distributed rather than shared.

FAQ

What is Microsoft Teams Meeting Shared Files? A Teams feature on the Microsoft 365 roadmap as feature 570427, created 8 September 2026. Microsoft's entry states it "allows users to add relevant files and links to their meeting for easy access and to automatically share that content with all meeting participants," and that "AI in the meeting, like the Facilitator agent, uses these files for targeted grounding to answer questions and enhance skill functionality." The row is tagged to both Microsoft Teams and Microsoft Copilot (Microsoft 365) (checked September 2026).

When is Meeting Shared Files available? The roadmap entry lists status "In development", release phase "General Availability", and availability "October CY2026", for the "Worldwide (Standard Multi-Tenant)" cloud instance, with platform tags for Android, Desktop, iOS, Linux and Mac (checked September 2026). Roadmap dates are Microsoft's own and can move.

Do I need a Microsoft Copilot license to use the AI that reads meeting files? For Facilitator, yes: "A Microsoft Copilot license is required to add Facilitator to a meeting or turn it on during a meeting." Microsoft adds that "any meeting participant (excluding external participants) can see all real-time updates in Chat and Notes," so the license gates turning it on rather than watching its output inside the tenant (checked September 2026).

Can external or anonymous participants use the file-grounded AI in a Teams meeting? Microsoft's Facilitator page states that real-time updates in Chat and Notes are visible to "any meeting participant (excluding external participants)". The roadmap entry for Meeting Shared Files does not state an access rule for participants outside the tenant (checked September 2026).

Can I ask the meeting AI a question about a shared file? In InterMIND, yes: address Mia by name aloud, or write to her in the private mode of the meeting chat (the lock next to the message field), and she answers from the summaries of the documents shared in this session, together with the transcript, the chat and the recaps of the room's previous sessions. She answers licensed participants of paid plans in every meeting they join; guests and free-plan participants hear her spoken answers to others; no in-call switch is involved. For Teams, the roadmap entry states that "AI in the meeting, like the Facilitator agent, uses these files for targeted grounding to answer questions," and the Facilitator page documents the Copilot license and the scheduled-meeting condition (checked September 2026).

In which language does the meeting AI answer? In InterMIND, in every language present in the room: Mia's spoken answer is written natively per language and voiced on each participant's device in that participant's language. A question written in the private mode of the chat is answered there, in text, to the person who wrote it. For Facilitator, Microsoft states that "you'll be asked to select a language if a language for the meeting hasn't already been selected" — one language per meeting (checked September 2026).

Can everyone in a meeting read a shared file in their own language? In InterMIND, the file's summary is served to each member in that member's own language and cached per language, a linked document opened on the stage is requested by each viewer's client in that viewer's own interface language, and reading the document itself in your language is document translation, covering 30 languages and metered per plan. For Teams, the roadmap entry states the file is shared with all participants and does not state per-participant language behaviour (checked September 2026).

Can I check an AI summary against the document it came from? In InterMIND, yes: each summary bullet ends with a ¶ link that jumps to the exact paragraph of the extracted text it was written from, and the extracted text is never translated so the anchor always lands on the author's own wording. The Extracted text tab holds the document's full text as it was read from the file.

Are document summaries limited by plan? In InterMIND the summary of a shared document is included on every plan with no quota. Mia in meetings is in preview and is not part of any plan yet; in the preview she answers participants of the Pro, Business and Enterprise plans, with no AI add-on on top. Translating the whole document is the metered feature: distinct files over a rolling 30-day window, 10 on Pro, 30 on Business, 100 on Enterprise, and not available on Basic.

What happens to a shared file after the meeting? Its summary feeds the meeting recap alongside what was said, with the same weight as spoken content — a session where nothing was said but documents were shared still produces a recap. The file's card stays in the chat with its AI summary and Extracted text, readable by members of that meeting or channel and by nobody else, and Mia in the room's next session answers from that recap.

Try it

• Open the live demo — a meeting in your language, no signup.
• See what document summaries look like — the ¶ anchors, the status strip, the language rule.
• Read the document-summaries docs — formats, card statuses, privacy and quotas.
• Read how sharing works in-call — documents, notes and recaps on the stage.
• Check the translation quality before you pay for it — per-pair scores on real traffic.

If what bothers you is not the file but the record it becomes, that argument is laid out separately in how to keep a meeting's transcript, summary and action items after the call.

Sources: Microsoft 365 Roadmap — feature 570427, "Microsoft Teams: Meeting Shared Files" (fields quoted from Microsoft's roadmap API); Microsoft Support — Facilitator in Microsoft Teams meetings, Interpreter in Microsoft Teams meetings and calls and Use live captions in Microsoft Teams meetings, checked September 2026.