Microsoft Loop supported features and where they work

Microsoft Loop is a set of collaborative building blocks — live components, flexible pages, and shared workspaces — that let teams edit the same small pieces of content across multiple Microsoft apps. Components (tables, lists, notes, task lists, voting, and more) are single, live objects that stay synchronized where they’re supported: Teams, Outlook on the web, Word on the web, OneNote, and SharePoint. This article lists the Loop components and core features, where you can host them today, tenant and licensing prerequisites that enable or block features, known limitations and workarounds, and how support differs by client and subscription.

What exactly are the Loop features you’ll see

Loop is built from three core concepts: components, pages, and workspaces.

Loop components are small, portable, live blocks you can embed in messages and documents. Typical components include Table, Paragraph, Task list, Voting table, Checklist, and Progress tracker. These components remain a single source of truth — edits you make appear for everyone who has access in real time. People can react to components, mention colleagues, or follow a component to get notified of changes.

Loop pages are flexible canvases that combine components with free-form text and files. A page collects multiple components, adds context and attachments, and is a place for a small team to organize a piece of work without creating a full document.

Workspaces are shared collections that list pages and components for a project or team, showing who’s active and what items exist.

Core features and short examples:

• Live collaborative components: multiple people edit a Table embedded in a Teams chat and each row appears immediately for everyone. For example, a shared planning table in a chat updates as colleagues add rows.
• @mentions: you can mention a colleague inside a Paragraph component to notify them across supported hosts.
• Reactions and presence: participants can react to a component and see who is currently editing it.
• Sync and real-time updates: changes to a component embedded in Outlook on the web appear in the same component embedded in a Teams channel for people with access.
• Version history: Loop content has basic versioning you can use to view recent edits and restore prior states; the depth and UI depend on the host app.
• Embedding and portability: a Loop component copied into a Teams message, an Outlook draft, or a OneNote page stays linked to that single source-of-truth component.

Example: create a Task list component on a Loop page and paste it into a Teams message; teammates can tick tasks off directly in that chat and the Loop page shows the updated status immediately.

Which Microsoft apps and clients actually support Loop components today

Support varies by host and by client type (web, desktop, mobile). Hosts that can contain Loop components today include Teams, Outlook (web and some desktop clients), Word for the web, OneNote, and SharePoint. Each host treats components a bit differently.

Teams (chat and channels)

• Teams is one of the most complete hosts for Loop. Components inserted into a chat message or a channel post are interactive: collaborators can edit, @mention, react, and see presence without leaving Teams.

For example: embedding a Table in a Teams chat lets participants edit rows inline while continuing the chat thread.

Outlook (web and desktop)

• Outlook for the web supports editing Loop components inline in message drafts and when viewing messages that contain components. Some Outlook desktop clients show the component but restrict interactivity or open a web editor.

For example: inserting a Paragraph component into an Outlook web draft lets recipients edit the same content if their clients support Loop, but recipients using certain desktop clients may see a read-only snapshot or be prompted to edit in the browser.

Word for the web

• Word for the web can host Loop components inside documents. Editing generally happens inline and keeps the component synced across hosts.

OneNote

• OneNote (web and some clients) can embed Loop components; editing may route to the web editor, with presence and live updates for collaborators.

SharePoint

• SharePoint pages can include Loop components, often through the Loop web experience. Components embedded in a SharePoint page update for viewers who have edit access, but the editing UI may open in a separate pane.

Behavioral differences and client breakdown

• Web clients (Teams web, Outlook web, Word for the web) generally provide the fullest and most consistent interactivity. Desktop clients often provide similar functionality but can fallback to a web view or a reduced experience depending on app version.
• Mobile clients (iOS, Android) and some lighter desktop clients commonly offer reduced functionality: components may render as a snapshot or open the web editor for full edits. Presence and inline editing can be limited on mobile.
• Operating systems (Windows, macOS) are not directly the gating factor — the difference is the app version and whether the native client integrates the Loop runtime or relies on a web fallback.

Subscription types and effect on availability

• Loop capabilities are available to Microsoft 365 commercial tenants. Consumer M365 accounts and some legacy subscription types may not have the same feature set or may have limited access.
• Tenant settings, admin controls and feature rollouts can also change what individual users see, regardless of OS or client.

Practical test you can run

1. Create a simple Checklist component in a Teams web chat.
2. Paste the same component into an Outlook web draft.
3. Verify editing behavior from each client your team uses (Teams desktop, Teams web, Outlook desktop, Outlook web, iOS/Android).

This reveals hosting and client differences for your environment.

Where Loop features are limited or behave differently (boundaries to expect)

Expect gaps and different behavior in several areas. Here are common limits and practical workarounds.

Offline and intermittent connectivity

• Limitation: Offline editing parity is not guaranteed. Some clients provide limited cached reads but full live editing requires an online connection.
• Workaround: Edit locally in a document you control (for example, Word) and paste updates back into the Loop component when online. For critical offline work, use document co-authoring in Word or OneNote which have more robust offline syncing.

Reduced interactivity in some hosts

• Limitation: Hosts that don’t fully support Loop may render components as read-only snapshots or open the web editor for edits.
• Workaround: Add a brief note in the message like “Edit via Teams web” and include the component link. Encourage users to use the Teams or Outlook web client when they need full interactivity.

Search and indexing gaps

• Limitation: Not all Loop content is indexed the same way as files or classic SharePoint pages. Tenant search can miss some components depending on host and index timing.
• Workaround: Place an anchor on a SharePoint page or document that is searchable, or maintain a summary page that includes key items from Loop pages for discoverability.

Complex objects and large tables

• Limitation: Very large tables, embedded files inside a component, or heavy formatting can degrade performance or limit editing capabilities.
• Workaround: Store large datasets in Excel or SharePoint lists and link to them from a Loop page instead of mirroring them inside a single component.

Versioning and audit gaps

• Limitation: Loop has version history but it may not provide the same enterprise audit trails or retention behavior as SharePoint-managed documents by default.
• Workaround: If you need strict retention, export important content into SharePoint or Office files that are covered by your tenant retention and eDiscovery policies.

Cross-tenant and external sharing

• Limitation: Sharing Loop content across tenants can be restricted by tenant settings; external users may get read-only or no access.
• Workaround: Use SharePoint or Teams guest access configured by your admin for cross-tenant collaboration, or export a snapshot when needed.

Copy/paste and portability limits

• Limitation: Copying a component into unsupported clients can create a snapshot rather than a live, linked component. Rich content may not survive round-trips.
• Workaround: Share the component link and instruct users to open and edit it in a supported host, or embed the component into a SharePoint page that all collaborators can access.

Pattern summary: prefer web clients for full interactivity, keep heavy data in native file types, and use SharePoint/Teams guest features for cross-tenant scenarios.

Licensing, tenant settings and admin controls that affect feature availability

Loop features depend on Microsoft 365 licensing, tenant feature rollouts, and admin controls. If Loop isn’t available for a user, check these points.

Licensing basics

• Loop capabilities are available to Microsoft 365 commercial tenants. Consumer M365 accounts and some legacy subscription types may not have the same feature set.

Tenant and admin controls to check

• External sharing and guest access: If your tenant blocks external sharing or guest invitations, cross-tenant Loop sharing will fail.
• Services required: Loop relies on underlying services that are controlled in the admin center (SharePoint and OneDrive for storage behaviors, and Exchange for Outlook integration). If those services are disabled or restricted, Loop behavior can be limited.
• Feature rollout and update rings: Microsoft sometimes ships Loop features gradually. Admins who restrict preview features or control update policies may delay availability.

Quick checklist an admin should run when a user reports “Loop not available”

1. Verify the user’s SKU is a supported commercial Microsoft 365 plan.
2. Confirm SharePoint and OneDrive services are enabled for the tenant.
3. Confirm Exchange Online is active (Outlook integration depends on it).
4. Check external sharing and guest settings if the issue involves cross-tenant users.
5. Confirm the tenant isn’t blocking Loop or Fluid Framework features via feature flags or security policies.

Admin center UIs and specific setting names may change; if you don’t see an obvious control, review recent Microsoft admin documentation for current paths.

Microsoft 365 admin center > Settings > Org settings > Services

If those checks don’t resolve the problem, capture a screenshot of the behavior, the affected user’s SKU, and the client type (Teams desktop, Teams web, Outlook desktop/web) before filing a support ticket or feedback.

Common misconceptions people have about Loop support

Loop is not a replacement for SharePoint, OneNote, or Word as a primary content repository. It’s designed for lightweight, live collaboration on small content pieces and collections of those pieces.

Misconception: Loop replaces SharePoint

• Reality: SharePoint remains the enterprise content store with comprehensive metadata, search indexing, retention and compliance controls. Use Loop for flexible, collaborative fragments that teams edit in context, and SharePoint when you need formal document management.

Misconception: All Loop components work offline

• Reality: Offline support is inconsistent. Some hosts provide cached views, but full two-way editing usually requires an online connection. If offline work is essential, rely on Word/OneNote co-authoring which has stronger offline sync.

Misconception: Everything embedded is a separate copy

• Reality: When a host supports Loop correctly, embedding a component references a single live instance. Editing any embedded copy updates every other location that references the same component, assuming all viewers have access.

Small example comparison to co-authoring in Word

• Co-authoring in Word is document-centric: the entire file lives in SharePoint/OneDrive, with full fidelity, offline syncing, and enterprise controls. Loop is component-centric: small, portable blocks can be used across apps with lighter governance and potentially less robust offline and retention behavior.

Conclusion

Next steps: confirm your users are on supported Microsoft 365 commercial plans, test a simple Loop component in Teams web and Outlook web to observe differences, and ask your IT admin to run the checklist in the Licensing section if features are missing. For functional gaps — search, offline edit, or cross-tenant sharing — use the suggested workarounds (export to SharePoint for retention, use Excel/SharePoint lists for large tables, prefer web clients for live edits) and file feedback with Microsoft including the client type and tenant details so they can investigate.

Frequently Asked Questions

How do I enable Loop for my organization?

Start by confirming users have supported Microsoft 365 commercial subscriptions and that SharePoint, OneDrive and Exchange services are enabled. Ask your admin to check tenant external sharing and feature flag settings in the Microsoft 365 admin center. If Loop still doesn’t appear, capture the user SKU and client type (Teams web/desktop, Outlook web/desktop) and file a support request.

Can I export Loop content for archiving or compliance?

Loop content can be copied into documents or SharePoint pages for retention, but Loop’s native versioning and retention behavior may not substitute for SharePoint-managed records. If you require firm retention or eDiscovery coverage, export key content into files stored in SharePoint or OneDrive that your compliance policies cover.

Is Loop secure enough for confidential data?

Loop uses tenant services (SharePoint/OneDrive/Exchange) for storage and follows the tenant’s security and compliance settings. For highly confidential data, follow your organization’s data classification rules: if policy requires SharePoint document controls or additional DLP, use those systems rather than relying solely on Loop components.