What it does

Live, co-editable blocks — tables, lists, task lists, paragraphs — dropped into a Teams message. Everyone in the conversation edits the same content in place, and the same component stays in sync wherever else it's been shared, such as an Outlook email.

Key facts

• Available in Teams on Windows, Mac, iOS, Android and web, in chats and channels. Loop components also work in Outlook (Windows and web), OneNote, Whiteboard and the Office mobile app.
• Each component is a .loop file (older ones are .fluid) saved automatically in the creator's OneDrive. Loop storage counts against SharePoint quota.
• Moving a .loop file from OneDrive into a SharePoint site breaks it everywhere it was shared — chats and emails will fail to load it.
• Teams experiences are controlled tenant-wide by SharePoint Online PowerShell: Set-SPOTenant -IsLoopEnabled for Loop components in Teams chats, channels and private meetings, and Set-SPOTenant -IsCollabMeetingNotesFluidEnabled for collaborative meeting notes. Both default to $true, and neither can be scoped to individual users.
• Cloud Policy (config.office.com) has separate settings for Loop workspaces, Loop files in other Microsoft apps, and Loop in Outlook. Cloud Policy alone doesn't control the Teams experience — you need the SharePoint PowerShell settings too.
• Multi-geo tenants have to set the SharePoint parameters in every regional URL for consistent results.
• Loop components are always shared as editable, regardless of the tenant's default link permission. View-only link defaults don't apply to them.
• Turning creation off doesn't block access to existing Loop files. Microsoft points to information barriers or Conditional Access for that.
• Loop components are disabled in most federated scenarios, and external email recipients can't open them unless sharing with those recipients is allowed.
• Cloud availability varies — check the Loop requirements page before planning for GCC or sovereign clouds.

When to use / skip

Use Loop components for the small, shared, short-lived things that otherwise generate fifteen messages: agreeing an agenda, a quick action list after a call, collecting names for a rota, drafting a paragraph together. They're at their best in group chats and channel threads where everyone is already present, and they stop people sending "latest version attached" at each other.

Skip them for anything that needs to outlive the conversation or be found later by someone who wasn't in it. A Loop component in a chat is a file in one person's OneDrive, shared by link — when that person leaves, ownership becomes a records question. Put long-lived work in a channel file, a Planner plan, a list, or a proper document. And don't use them with external federated contacts; mostly they won't render.

Configuration decisions

• Whether Loop stays on tenant-wide (the default) or is disabled with IsLoopEnabled until the compliance team has signed it off.
• Whether collaborative meeting notes stay enabled — separate switch, same principle.
• How the Cloud Policy settings line up with the SharePoint settings, so Outlook and Teams don't behave differently.
• Retention and eDiscovery coverage for .loop files in OneDrive — agree it with the compliance workstream before broad adoption rather than after.
• External sharing posture, given that Loop components always go out as editable.
• Whether OWA mailbox policy settings support Loop in new Outlook and Outlook on the web, if the client wants components to work across email too.

Gotchas

• Admins switch Loop off in Cloud Policy and are surprised it still works in Teams. The Teams side is the SharePoint tenant setting.
• Disabling creation leaves existing components accessible. If the goal is to stop access, that's a different conversation.
• Editable-by-default catches people who've carefully set view-only links across the tenant.
• A tidy-minded user moving .loop files into a team site to "file them properly" breaks every chat they were in.
• Leavers' OneDrives take their Loop components with them once retention for the account runs out.
• Conditional Access session controls can reduce Loop functionality in browser sessions, which looks like a bug to users.
• Multi-geo tenants that change the setting in one region only end up with inconsistent behaviour that's tricky to diagnose.

Consultant notes

• Show users a Loop task list in a group chat during adoption sessions — it lands faster than any explanation.
• Put a one-liner in user guidance: "Loop for quick shared notes; channel files for anything you'll need next month."
• Check both the SharePoint PowerShell values and the Cloud Policy settings before answering "is Loop on?"
• Keep .loop files in OneDrive where they were created. Tell users to copy content out, not move the file.
• Loop components and Copilot Pages share storage plumbing (the Loop My workspace uses the same SharePoint Embedded container as Copilot Pages) — expect governance questions about one to pull in the other.

---

Revisit if Microsoft adds user-level scoping for Loop in Teams, or changes where chat-created Loop components are stored