What it does

A shared AI participant in the meeting. It keeps live collaborative notes, tracks the agenda and time, answers questions, and drafts documents — and everything said to it and by it is visible to the whole meeting. That's the opposite of personal Copilot, where prompts stay private.

Key facts

• Generally available (per Learn, October 2026): collaborative real-time notes on the Notes tab, Q&A from meeting and web content, timeline markers with midway and wrap-up reminders, Word document creation in or after the meeting, the Teams Rooms experience, mobile capture of ad hoc discussions, and @mentioning Facilitator in the meeting chat.
• Public preview: task tracking integration with Planner.
• Loop file generation was retired by 31 July 2026 as part of a back-end migration; Word generation is the replacement. Live notes weren't affected.
• Licensing: eligible Microsoft 365 base licence, a Teams licence, and a Copilot licence. Included with Copilot "subject to available capacity".
• Only licensed users can start Facilitator or prompt it. Unlicensed attendees can see the prompts, responses and notes.
• Admin control is an app, not a meeting-policy parameter: Teams apps > Manage apps, search "Facilitator", Allow or Block. Allowed by default unless all apps are blocked. Scope it with app permission policies or app-centric management.
• Loop experiences in Teams must be on for Facilitator in meetings. AI-generated meeting notes are controlled by the tenant-wide SharePoint property Set-SPOTenant -IsCollabMeetingNotesFluidEnabled — there's no per-user switch.
• Notes are stored as a .loop file in the Meetings folder of the initiating user's OneDrive and treated as meeting transcript data.
• Not supported in 1:1 chats, group chats, or external chats and meetings.
• Single-language only: the user picks the spoken language when starting it. Notes are only taken for the parts of the meeting in that language.

When to use / skip

Facilitator earns its place in working meetings where the group needs one agreed set of notes and actions — project stand-ups, design sessions, workshops. It removes the "who's taking notes?" question and leaves a shared artefact everyone edited. Personal Copilot can't do that, because everyone's view is private.

Skip it for anything external, multilingual, or compliance-heavy. It doesn't run in external meetings at all, gets confused if the meeting switches language, and the notes don't currently show up as cloud attachments in Purview eDiscovery. Meeting protections such as watermarking and "prevent copy and paste" don't apply to its output either. For sensitive internal meetings, those gaps matter more than the convenience.

Also skip it where the client hasn't settled Loop governance. Facilitator depends on Loop experiences being on, and turning Loop on just for Facilitator drags in every other Loop experience in Teams.

Configuration decisions

• Leave Facilitator allowed for everyone, or block it and allow it for a pilot group through an app permission policy.
• Loop experiences in Teams: on or off at tenant level, and whether the organisation accepts the Loop compliance position.
• IsCollabMeetingNotesFluidEnabled: keep AI-generated notes on, or turn them off for the whole tenant (it's all or nothing).
• Sensitivity labelling for notes — they don't inherit the meeting label, so decide whether users must label them manually.
• Records approach: since notes live in the initiator's OneDrive, what happens when that person leaves.
• Whether to join the Teams Public preview to get Planner task tracking.

Gotchas

• Notes don't inherit the meeting's sensitivity label. And if someone labels the notes outside Teams, the file can't then be opened in Teams.
• Retention labels aren't supported for cloud attachments in AI-generated notes, and eDiscovery won't collect them as cloud attachments.
• Watermark and "prevent copy and paste" meeting options don't touch Facilitator's responses or notes. Premium protections stop at the edge of the agent.
• Pick the wrong meeting language and you get no notes.
• The notes file belongs to whoever started Facilitator. Run it from a shared account or a stable owner if the output matters long term.
• Blocking all apps at tenant level also blocks Facilitator — a common surprise in locked-down tenants that have bought Copilot.
• Anything you prompt is public to the room. Users used to private Copilot will over-share once.

Consultant notes

• Demo Facilitator next to personal Copilot in the same meeting. Showing "public versus private" makes the difference land in thirty seconds.
• Check Loop settings before the pilot — Get-SPOTenant for IsLoopEnabled and IsCollabMeetingNotesFluidEnabled, plus the Loop Cloud Policy settings. Learn is explicit that Cloud Policy alone doesn't control the Teams experiences. Facilitator not appearing is usually Loop, not licensing.
• Get the records manager to sign off the OneDrive-of-initiator storage model before rolling out widely.
• Teams Rooms has its own Facilitator page and behaviour; check it before promising in-room capability.
• Update any user guidance that still mentions "Facilitator creates a Loop page" — that path ended in July 2026.

---

Recheck when Planner task tracking reaches GA, or if Microsoft fixes the eDiscovery and sensitivity label gaps on Facilitator notes