This chapter covers Microsoft Loop components, a key collaborative feature within Microsoft 365 that enables real-time co-authoring of dynamic content across Teams, Outlook, and other apps. For the MS-900 exam, this topic appears in roughly 5-8% of questions under Objective 2.1 (Describe productivity solutions of Microsoft 365). You need to understand what Loop components are, how they differ from traditional static content, their underlying Fluid Framework, and where they can be used. This chapter will provide a thorough explanation of the technology, its mechanics, and exam-critical details.
Jump to a section
Think of a Microsoft Loop component as a shared whiteboard section that multiple people can draw on simultaneously. In a physical office, a team might have a whiteboard with a table of tasks. Each person can walk up, add a note, check a box, or rearrange items. But if two people try to write in the same spot at the same time, there's a conflict. Now imagine that whiteboard is digital, and every change is instantly synced to all viewers' screens. The whiteboard doesn't lock; instead, it uses a technique called Operational Transformation (OT) or Conflict-Free Replicated Data Types (CRDTs). Each person's edits are treated as atomic operations that can be merged without conflict. For example, if Alice types 'A' at position 5 and Bob types 'B' at position 5 at the same time, the system inserts both characters, preserving the intent. This is exactly how Loop components work: they are live, collaborative snippets of content (like tables, lists, or paragraphs) that reside in a Fluid Framework container. When you paste a Loop component into a Teams chat or Outlook email, you're not sending a static copy; you're embedding a reference to a live object. Everyone who can see that component sees the same data, and edits are synchronized in real-time via the Fluid service. Just as the whiteboard allows multiple markers to write at once without waiting, Loop components allow simultaneous editing without version conflicts.
What Are Microsoft Loop Components?
Microsoft Loop components are portable, live, collaborative pieces of content that can be shared across Microsoft 365 apps such as Teams, Outlook, Whiteboard, and the Loop app itself. They are built on the Fluid Framework, a technology that enables real-time synchronization and co-authoring. Unlike traditional shared documents (e.g., a Word file attached to an email), Loop components are lightweight and designed for fast, granular collaboration. Common types include task lists, tables, paragraphs, bulleted lists, checklists, and more.
Why Loop Components Exist
Before Loop, collaboration often involved sending static files back and forth, leading to version conflicts and delays. Even with co-authoring in Word or Excel, the collaboration was confined to that specific app. Loop components break down silos: you can embed a live task list in a Teams chat, and when someone updates it, the change appears everywhere the component is shared—including in Outlook emails or on a Whiteboard. This aligns with Microsoft's vision of 'fluid' collaboration where content flows seamlessly between apps.
How It Works Internally
Loop components are built on the Fluid Framework, which uses a combination of Operational Transformation (OT) and Conflict-Free Replicated Data Types (CRDTs) to handle concurrent edits. Here's a step-by-step of the mechanism:
Creation: A user creates a Loop component in a host app (e.g., Teams). The component is essentially a JSON object containing structured data (e.g., a list of tasks). This object is stored in a Fluid container hosted in the Microsoft cloud.
Sharing: When the user sends the component to another user (e.g., via a chat message), the message contains a link to the Fluid container, not a copy of the data. The recipient's client connects to the same container.
Real-time Sync: Each client maintains a local copy of the component state. Edits are sent as operations (e.g., 'insert character at position 5', 'delete task ID 3'). The Fluid service merges operations using OT/CRDTs and broadcasts the merged state to all clients. This ensures eventual consistency without locks.
Persistence: The Fluid container persists in the cloud as long as at least one user has access. If all users delete the component, it may be garbage-collected after a period (though exact timers are not documented). The component's data is stored in the same region as the user's tenant.
Key Components, Values, and Defaults
Fluid Framework: The underlying real-time sync engine. It is not a separate Azure service; it is integrated into Microsoft 365.
Loop components: The actual content types. Supported types (as of MS-900 exam objectives):
- Task list - Table - Paragraph - Bulleted list - Checklist - Numbered list - Voting table - Progress tracker - Q&A - Host apps: Teams (chat, channels, meetings), Outlook (email), Whiteboard, Loop app (standalone). - Limitations:
Maximum component size: No hard limit documented, but practical limit is a few thousand characters.
Number of simultaneous editors: Fluid supports up to 10 concurrent editors per component (based on documentation).
Data residency: Components are stored in the same geographic region as the Microsoft 365 tenant.
Licensing: Loop components are available with Microsoft 365 Business Basic, Standard, Premium, and Enterprise plans. No additional license is required beyond the base Microsoft 365 subscription.
Configuration and Verification
Loop components are enabled by default in most Microsoft 365 tenants. Admins can disable them via: - Teams admin center: Messaging policies > 'Allow Loop components' toggle. - Outlook on the web: Settings > General > 'Loop components' (user-level). - PowerShell: Set-CsTeamsMessagingPolicy -AllowFluidContent $false.
Verification: Users can test by opening Teams, starting a chat, and clicking the Loop components icon (a square with a loop arrow) below the compose box. If the icon is missing, the feature is disabled.
Interaction with Related Technologies
Loop components are part of the broader Microsoft Loop app, which also includes: - Loop pages: Flexible canvases that can contain multiple Loop components and other elements. - Loop workspaces: Shared spaces for teams to organize pages and components.
Loop components integrate with: - Microsoft Teams: Embedded in chat and channel messages. - Outlook: Embedded in email bodies (sender and recipient must have Loop components enabled). - Microsoft Whiteboard: Components can be pasted onto a whiteboard. - Microsoft Planner: Task lists can be synced to Planner (limited integration).
Exam-Relevant Details
Loop components are NOT the same as Loop pages or workspaces. The exam may ask which one is a portable snippet vs. a canvas.
Loop components require the Fluid Framework, but the exam does not test deep technical details of Fluid.
The key exam point: Loop components allow real-time co-authoring across apps without leaving the conversation context.
Common trap: Candidates confuse Loop components with SharePoint web parts or Power Apps components. Loop components are distinct and focused on lightweight, inline collaboration.
Default state: Enabled in all Microsoft 365 subscriptions that include Teams or Exchange Online.
Security: Loop components respect existing permissions (e.g., if shared externally, the external user must authenticate and have appropriate access).
Create a Loop Component
In a supported app (e.g., Teams chat), click the Loop components icon below the compose box. A menu appears showing available component types (Task list, Table, Paragraph, etc.). Select one. The component is inserted as a live, editable block. Behind the scenes, the Fluid Framework creates a new container in the cloud and assigns a unique ID. The component's initial state is serialized as JSON and stored in the container. The host app displays the component using a Fluid client that renders the JSON as a rich interactive element.
Share the Component
When you send the message containing the Loop component, the message payload includes a deep link to the Fluid container. Recipients who click or view the component are connected to the same container. The link includes authentication tokens to verify access. If the recipient is outside the organization, they may need to authenticate via Azure AD B2B collaboration. The component appears as a live block in the recipient's chat or email, not as a static screenshot.
Collaborate in Real Time
All participants with access to the component can edit it simultaneously. Edits are sent as incremental operations to the Fluid service. The service uses OT/CRDT algorithms to merge concurrent changes. For example, if two users add different items to a task list, both items appear. Each client's local state is updated via the merged operations. Users see cursor positions and edits of others in real time (similar to co-authoring in Word). The component remains live as long as the chat or email is open.
Update Across Locations
If the same Loop component is shared in multiple locations (e.g., a Teams chat and an Outlook email), changes made in one location are reflected in all others. This is because all instances reference the same Fluid container. The Fluid service propagates changes to all connected clients. For example, if a task in a Loop component is marked complete in a Teams chat, the same task appears complete in the Outlook email that contains the component. This cross-app sync is a key differentiator from static content.
Stop Sharing or Delete
When a user deletes a message or email containing a Loop component, the component is removed from that location but still exists in other locations and the Fluid container. The component is fully deleted only when all references are removed and the container is garbage-collected (typically after 30 days of no access). Admins can also delete containers via PowerShell or compliance tools. If a user loses access (e.g., removed from the chat), they can no longer view or edit the component.
Scenario 1: Project Task Tracking in Teams A marketing team is launching a campaign. The project manager creates a Loop component with a task list in the team's Teams channel. The tasks include assignments, due dates, and status. Team members update the list as they complete work. The component is also embedded in an Outlook email sent to stakeholders for visibility. When a team member marks a task complete in Teams, the email automatically shows the updated status. This eliminates the need for separate status reports. In production, the team has a channel with 15 members. Performance is smooth as long as concurrent edits are under 10. One issue: if a member edits the component in Outlook web, there is a slight delay (1-2 seconds) compared to Teams due to different sync mechanisms. The team learned to avoid editing the same cell simultaneously to prevent confusion, though the system handles merges well.
Scenario 2: Collaborative Agenda in Meetings During a weekly sales meeting, the organizer shares a Loop component with a voting table to decide the next quarter's focus. Participants vote in real time via Teams chat. The results update instantly. Later, the organizer copies the component into a Loop page for future reference. The component retains the live data. A common misconfiguration: if the organizer shares the component with external guests, external users cannot edit unless they have a Microsoft 365 account and the tenant allows external collaboration. The team had to switch to a guest account for a partner.
Scenario 3: Troubleshooting Misconfiguration A company disabled Loop components via Teams messaging policy to reduce distractions. However, users still saw the icon and could create components. This happened because the policy was applied only to new chats, not existing ones. The admin had to modify the policy and restart Teams clients. Another issue: a user reported that a Loop component in an email was not updating. The cause was that the recipient had opened the email in a non-supported client (e.g., Apple Mail). Loop components only work in Outlook on the web or the Outlook desktop client with the Fluid feature enabled. The fix was to view the email in Outlook on the web.
Objective 2.1 – Describe productivity solutions of Microsoft 365 The MS-900 exam tests Loop components under the umbrella of 'modern collaboration tools.' You should expect 1-2 questions specifically on Loop components, often disguised as 'real-time co-authoring' or 'fluid content.' Key exam points:
What Loop components are: Portable, live, collaborative content snippets that can be shared across Microsoft 365 apps. They are NOT full documents or pages.
Where they can be used: Teams (chat, channels, meetings), Outlook (email), Whiteboard, Loop app.
Supported types: Task list, table, paragraph, bulleted list, checklist, numbered list, voting table, progress tracker, Q&A.
Underlying technology: Fluid Framework (not SharePoint, not Power Platform).
Licensing: Included in Microsoft 365 Business and Enterprise subscriptions; no extra cost.
Common Wrong Answers: - 'Loop components require a separate license.' (False; they are included in most Microsoft 365 plans.) - 'Loop components are only available in Teams.' (False; they work in Outlook, Whiteboard, and Loop app too.) - 'Loop components create a copy of the data that is not synced.' (False; they are live and synced in real time.) - 'Loop components are the same as Loop pages.' (False; pages are canvases, components are snippets.)
Trap Patterns:
The exam may ask: 'Which Microsoft 365 feature allows real-time co-authoring of a task list in a Teams chat?' The correct answer is 'Loop components.' Distractors might include 'SharePoint list' or 'Planner.'
Another question: 'What technology powers Loop components?' Answer: 'Fluid Framework.' Not 'Azure Functions' or 'Power Automate.'
Edge Cases:
Loop components cannot be used in Yammer or SharePoint news posts (as of exam date).
External sharing requires Azure AD B2B and may not work in all scenarios.
If an admin disables Loop components via policy, users will not see the icon in Teams.
How to Eliminate Wrong Answers: Remember that Loop components are about real-time, cross-app collaboration. If an answer suggests static content or app-specific features, it is likely wrong. Focus on the key phrase 'portable, live, collaborative snippets.'
Loop components are portable, live, collaborative snippets that sync in real time across Teams, Outlook, Whiteboard, and the Loop app.
They are built on the Fluid Framework, which uses OT/CRDTs for conflict-free editing.
Loop components are included in most Microsoft 365 subscriptions without extra cost.
Common types: task list, table, paragraph, bulleted list, checklist, numbered list, voting table, progress tracker, Q&A.
Maximum concurrent editors per component is 10.
Loop components are different from Loop pages (canvases) and Loop workspaces (shared spaces).
Admins can disable Loop components via Teams messaging policies or Outlook settings.
External sharing requires Azure AD B2B authentication; anonymous access is not allowed.
These come up on the exam all the time. Here's how to tell them apart.
Loop Components
Real-time sync across multiple apps (Teams, Outlook, etc.)
Lightweight, inline snippets (task list, table, etc.)
No page context required; embedded in chat/email
Based on Fluid Framework
Limited to 10 concurrent editors
SharePoint Web Parts
Static content within a SharePoint page
Full web parts (document library, calendar, etc.)
Requires a SharePoint site and page
Based on SharePoint Framework
Supports many concurrent users with page-level permissions
Mistake
Loop components require a separate Microsoft 365 license.
Correct
Loop components are included with Microsoft 365 Business Basic, Standard, Premium, and Enterprise subscriptions. No additional license is needed.
Mistake
Loop components are only available in Microsoft Teams.
Correct
Loop components can be used in Teams, Outlook, Whiteboard, and the Loop app. They are designed to be cross-app.
Mistake
Loop components create a static copy when shared.
Correct
Loop components are live and sync in real time. All instances share the same underlying data via the Fluid Framework.
Mistake
Loop components are the same as Loop pages.
Correct
Loop components are portable snippets (e.g., a task list). Loop pages are larger canvases that can contain multiple components and other content.
Mistake
Loop components can be edited by anyone with the link, including anonymous users.
Correct
Loop components require authentication. External users need a Microsoft 365 account and appropriate permissions (Azure AD B2B). Anonymous access is not supported.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Microsoft Loop components are live, collaborative content snippets that can be shared across Microsoft 365 apps. They work by storing data in a Fluid container in the cloud. When you share a component, you share a link to that container, not a copy. All edits are synced in real time using the Fluid Framework's OT/CRDT algorithms. This allows multiple users to edit simultaneously without conflicts.
Loop components are supported in Microsoft Teams (chat, channels, meetings), Outlook (email), Microsoft Whiteboard, and the Microsoft Loop app (standalone). They are not available in Yammer, SharePoint news, or OneNote as of the current exam objectives.
No. Loop components are included with Microsoft 365 Business Basic, Standard, Premium, and Enterprise subscriptions. There is no additional cost. However, some features like external sharing may require Azure AD B2B, which is included in many plans.
Yes, but with limitations. External users must have a Microsoft 365 account and be authenticated via Azure AD B2B collaboration. Anonymous access is not supported. The external user must be invited to the tenant or the chat/email, and the organization must allow external sharing.
Admins can disable Loop components in Teams via the Teams admin center: Messaging policies > 'Allow Loop components' toggle. For Outlook, users can disable it in Outlook on the web settings. There is no global tenant-level switch for all apps; you must configure per app.
Loop components are portable, lightweight snippets (e.g., a task list) that can be embedded in chats or emails. Loop pages are larger, flexible canvases that can contain multiple components and other content, similar to a digital whiteboard. Pages are part of the Loop app and workspaces.
The Fluid Framework supports up to 10 concurrent editors per component. If more than 10 try to edit simultaneously, performance may degrade or some may be unable to edit. Microsoft recommends limiting concurrent edits to 10 for optimal performance.
You've just covered Microsoft Loop Components and Collaboration — now see how well it sticks with free MS-900 practice questions. Full explanations included, no account needed.
Done with this chapter?