This chapter covers Microsoft Loop, a new collaborative workspace in Microsoft 365 that enables real-time co-authoring and sharing of portable content components across apps. For the MS-900 exam, understanding Loop's components, workspaces, and integration points is essential, as it represents a key innovation in Microsoft's productivity suite. Approximately 5-8% of exam questions touch on modern collaboration tools, including Loop, Viva, and Teams. This chapter will equip you with the precise technical details needed to answer questions about Loop's architecture, licensing, and use cases.
Jump to a section
Imagine a team working in a large physical room with a giant whiteboard that covers an entire wall. Each team member has a set of colored markers. When someone writes on the whiteboard, everyone in the room sees the change instantly. But what if the team is scattered across different cities? Microsoft Loop is like a digital version of that whiteboard, but with superpowers. Each component on the Loop whiteboard is like a sticky note that can be a task list, a paragraph, a table, or even a live data feed. When a team member updates a sticky note in their local copy, the change is synced in real time to all other copies, no matter where they are – in a Teams chat, an Outlook email, or a Word document. The whiteboard is not a single file; it's a live, interconnected canvas. Each sticky note is a 'Loop component' that can be shared independently. Think of it as a shared clipboard that updates itself. If I paste a task list into a Teams chat, and you paste the same component into an email, we both see the same live data. When you check off a task, I see it checked off instantly. The underlying technology uses Microsoft Fluid Framework to synchronize data via Microsoft Graph, ensuring low-latency updates across all Microsoft 365 apps. Just as a physical whiteboard allows anyone in the room to contribute simultaneously, Loop allows multiple users to edit the same component at the same time, with changes merging seamlessly. It's like having a real-time collaborative document, but broken into reusable, portable pieces that live anywhere in Microsoft 365.
What is Microsoft Loop?
Microsoft Loop is a transformative collaboration platform introduced by Microsoft as part of Microsoft 365. It is designed to break down the silos between traditional documents, chats, and emails by enabling real-time, fluid collaboration on portable pieces of content called 'Loop components'. Loop is built on the Microsoft Fluid Framework, an open-source technology that decouples content from the application, allowing the same component to be embedded and edited across multiple surfaces simultaneously.
Why Loop Exists
Traditional collaboration often involves sending files back and forth, creating multiple versions, and struggling to keep everyone on the same page. Loop addresses these pain points by providing:
Real-time co-authoring: Multiple users can edit a component simultaneously, with changes reflected instantly.
Portability: Components can be shared across Teams, Outlook, Word, Whiteboard, and other Microsoft 365 apps without losing interactivity.
Granularity: Instead of sharing an entire document, users can share a specific table, list, or paragraph.
Workspaces: A shared canvas where teams can organize components, ideas, and projects in a flexible, persistent space.
How Loop Works Internally
Loop components are built using the Microsoft Fluid Framework, which uses a data structure called a 'Fluid container'. This container holds the state of the component and is stored in the cloud. When a user makes a change, the framework uses Operational Transformation (OT) to merge concurrent edits from multiple users. The framework communicates via WebSockets to Microsoft Graph, ensuring low-latency synchronization (typically under 200ms). Each component has a unique identifier (GUID) that allows it to be embedded in multiple hosts (Teams, Outlook, etc.). The host application renders the component using an iframe or a native rendering engine, but the actual data lives in the Fluid container.
Key Components and Values
- Loop components: Portable, live content units such as: - Voting table: A table with rows for options and columns for votes, allowing team members to vote in real time. - Task list: A to-do list with assignees, due dates, and status. - Paragraph: A rich text block that supports formatting and inline images. - Numbered list: For ordered steps or priorities. - Checklist: A simple list with checkboxes. - Progress tracker: A visual indicator of task completion. - Person: A contact card that can be expanded. - Image: An inline image. - Date: A date picker. - Status: A status indicator (e.g., In Progress, Done). - Loop workspaces: A dedicated canvas (similar to a wiki or Notion page) where teams can create, organize, and iterate on components. Workspaces are stored in the user's OneDrive for Business and are shareable with specific people or groups. - Loop pages: Within a workspace, pages are used to structure content. Pages can contain multiple components and can be nested. - Fluid Framework: The underlying technology that enables real-time sync. It uses a client-server model where the server (Azure Fluid Relay) coordinates changes.
Configuration and Licensing
Loop is included in the following Microsoft 365 plans:
Microsoft 365 Business Basic, Standard, Premium
Microsoft 365 Enterprise E3, E5
Microsoft 365 Education A3, A5
Microsoft 365 Frontline F1, F3
Note: Loop components are available in Teams and Outlook with these licenses. Loop workspaces require an additional license? Actually, as of 2024, Loop workspaces are available to users with these licenses, but some advanced features (like sensitivity labels) may require E5. There is no separate Loop license.
To enable Loop in an organization, an admin can configure policies in the Microsoft 365 admin center under Settings > Org settings > Microsoft Loop. The admin can control:
Whether users can create and share Loop components.
Whether Loop workspaces are enabled.
Data residency settings (where Fluid containers are stored).
Integration with Microsoft 365
Loop components can be inserted in:
Microsoft Teams: In chat messages, channel conversations, and meeting notes.
Microsoft Outlook: In email messages (compose new email or reply).
Microsoft Word: In documents (via Insert > Loop component).
Microsoft Whiteboard: As sticky notes.
Microsoft OneNote: In notebooks.
Microsoft SharePoint: In pages and news posts (via web part).
When a component is shared, all recipients with appropriate permissions can edit it. Changes are synced across all instances in real time.
Security and Compliance
Loop components inherit the security and compliance policies of the host application. For example, a component shared in a Teams chat is subject to the same data loss prevention (DLP) policies, retention policies, and eDiscovery as the chat. However, because components are stored in Azure Fluid Relay, admins should be aware of where data is stored. Microsoft provides data residency options to keep data within a specific geographic region.
Exam-Relevant Details
Loop components are not files; they are live data containers.
They are stored in Azure Fluid Relay (not in Exchange or SharePoint).
Components can be shared with external users if the organization allows external collaboration.
Loop workspaces are stored in the creator's OneDrive for Business (each workspace is a folder with a special structure).
The Fluid Framework is open-source and available on GitHub.
Loop is not available in Microsoft 365 Government Community Cloud (GCC) or GCC High as of 2024 (check current status).
Loop components have a size limit of approximately 250 KB of JSON data.
The maximum number of concurrent editors is 50 (per component).
Loop uses Operational Transformation (OT) for conflict resolution, not CRDT (Conflict-free Replicated Data Types) though the Fluid Framework supports both.
Common Misconfigurations
Blocking Loop via policy: Some admins disable Loop components globally, which can frustrate users. Instead, admins can allow components but disable workspaces.
Data residency: If an organization has strict data residency requirements, the admin must configure the Azure Fluid Relay location in the admin center.
External sharing: If external sharing is disabled in Teams or Outlook, Loop components cannot be shared with external users.
Verification Commands (PowerShell)
Administrators can use PowerShell to check Loop settings:
Get-CsTeamsClientConfiguration | Select-Object -ExpandProperty DisableLoopComponents
Get-CsTeamsMessagingPolicy | Select-Object -ExpandProperty AllowLoopComponentsTo enable Loop components globally:
Set-CsTeamsClientConfiguration -DisableLoopComponents $falseFor Outlook:
Get-OrganizationConfig | Select-Object -ExpandProperty LoopComponentsEnabled
Set-OrganizationConfig -LoopComponentsEnabled $trueSummary of Key Numbers
Concurrent editors: Up to 50.
Component size limit: ~250 KB.
Sync latency: Typically <200 ms.
Storage: Azure Fluid Relay for components; OneDrive for workspaces.
Availability: Not in GCC/GCC High (as of 2024).
This comprehensive understanding will help you answer MS-900 questions on Loop with confidence.
Insert a Loop component
A user opens a Teams chat and clicks the Loop icon (or types '/' and selects 'Loop component'). A menu appears showing available component types (task list, voting table, etc.). The user selects one, and the component is created as a Fluid container in Azure Fluid Relay. The component is rendered in the chat as an interactive card. The user can then add content (e.g., tasks) and share it with others in the chat.
Share and collaborate
Other members of the chat see the component in real time. When they click on it, they can edit it directly. Changes are sent via WebSocket to the Azure Fluid Relay, which broadcasts the changes to all other instances. If two users edit the same field simultaneously, the Operational Transformation algorithm merges the changes without conflict. Each user sees the update within milliseconds.
Copy component to another app
A user wants to share the same component in an Outlook email. They click the 'Copy component' button in Teams, which copies a link to the component (a deep link with the component's GUID). In Outlook, they paste the link into the email body. Outlook recognizes the link and renders the component inline. The recipient can edit the component directly in the email, and changes sync back to the original component in the Teams chat.
Use Loop workspace
A user navigates to loop.microsoft.com and creates a new workspace. The workspace is stored as a special folder in their OneDrive. They add pages and components. They can invite team members via email or link. Invited members get access to the workspace and can co-author in real time. The workspace supports commenting, @mentions, and version history.
Admin configuration
An admin wants to disable Loop components for security reasons. They go to Microsoft 365 admin center > Org settings > Microsoft Loop and toggle off 'Allow Loop components'. They also use PowerShell to disable Loop in Teams and Outlook. The changes take effect within a few hours. Users will no longer see the Loop option in chat or email. Existing components remain but become read-only.
Enterprise Scenario 1: Real-Time Project Tracking
A large consulting firm uses Microsoft Teams for client projects. Previously, project managers would create a task list in Excel, share it via email, and then manually update statuses based on email replies. This led to version conflicts and stale data. They adopted Loop task lists embedded in Teams channels. Now, team members update their tasks directly in the chat. The project manager can see real-time progress. The same task list is also embedded in a SharePoint site for stakeholders. Changes sync instantly. This reduced status meeting time by 30%. The firm configured Loop to be enabled for all users, but disabled workspaces to avoid content sprawl. They also set a data residency policy to keep Fluid containers in the US region.
Enterprise Scenario 2: Collaborative Brainstorming with Voting
A marketing agency uses Loop voting tables to gather feedback on campaign ideas. They create a voting table in Teams with campaign names as rows and criteria (e.g., 'Creative', 'ROI') as columns. Team members vote by clicking cells. The table tallies votes in real time. The agency also shares the same component in an Outlook email to include remote clients. Clients can vote directly in the email. The agency found that this increased participation by 50% compared to email polls. One challenge: external clients needed guest access in Teams to see the component in email, which required enabling external sharing. They configured Azure AD B2B collaboration to allow secure guest access.
Performance and Scale
At scale, Loop components are lightweight. A single component can handle up to 50 concurrent editors. For larger teams, multiple components can be used. The Azure Fluid Relay automatically scales based on demand. Organizations with thousands of users should monitor network latency; WebSocket connections require stable internet. Misconfiguration: if an admin blocks WebSocket traffic (port 443), Loop components will fail to sync. Also, if the Azure Fluid Relay region is far from users, latency may exceed 500ms. The solution is to choose the nearest region during setup.
Common Pitfalls
Data loss: If a user deletes a component from a chat, it is permanently deleted unless it is also embedded elsewhere. There is no recycle bin for components.
Compliance: Loop components are not indexed by eDiscovery in all cases. As of 2024, components in Teams chats are discoverable, but components in Outlook emails may not be fully indexed. Organizations should test eDiscovery with Loop components.
External sharing: If a Loop component is shared with an external user who does not have a Microsoft 365 license, they can view but not edit. Editing requires a licensed user or guest account.
What MS-900 Tests on Loop
MS-900 objective 2.1 covers 'Describe the productivity solutions of Microsoft 365', which includes Loop. Specifically, the exam expects you to:
Identify the purpose of Microsoft Loop (real-time collaboration, portable components).
Know which Microsoft 365 apps support Loop components (Teams, Outlook, Word, Whiteboard, OneNote, SharePoint).
Understand the difference between Loop components and Loop workspaces.
Recognize that Loop is built on the Fluid Framework.
Know that Loop is available in most Microsoft 365 plans (Business, Enterprise, Education, Frontline) except GCC/GCC High.
Understand that Loop components are not files and are stored in Azure Fluid Relay.
Common Wrong Answers and Why Candidates Choose Them
'Loop components are stored in SharePoint.' This is wrong because Loop components are stored in Azure Fluid Relay, not SharePoint. Candidates confuse Loop with SharePoint document libraries. Remember: Fluid containers are separate.
'Loop workspaces are stored in Teams.' Wrong. Workspaces are stored in the creator's OneDrive for Business. Candidates think of Teams as the host, but storage is in OneDrive.
'Loop requires a separate license.' Wrong. Loop is included with most Microsoft 365 subscriptions. There is no add-on license. Candidates may think of premium features like Microsoft Viva.
'Loop components can only be edited by one person at a time.' Wrong. Loop supports up to 50 concurrent editors. Candidates think of traditional documents with check-out locking.
Specific Numbers and Terms That Appear on the Exam
Fluid Framework: The underlying technology.
Azure Fluid Relay: Where component data is stored.
50: Maximum concurrent editors per component.
Real-time: Sync latency under 200ms.
Portable: Components can be embedded in multiple apps.
Workspace: A persistent, shared canvas.
Edge Cases the Exam Loves
External sharing: Can you share a Loop component with an external user? Yes, if the organization allows external collaboration. The external user needs a Microsoft account or guest access.
Data residency: Admins can configure where Fluid data is stored. The exam may ask about compliance.
Loop in GCC: Not available (as of 2024). This is a common trick question.
How to Eliminate Wrong Answers
If an answer says 'stored in SharePoint' or 'stored in Exchange', eliminate it.
If an answer says 'requires additional license', eliminate it (unless it's about a premium feature like Viva).
If an answer says 'only one user can edit at a time', eliminate it.
If an answer says 'Loop is available in GCC', eliminate it (unless the question specifies a future date).
By focusing on these patterns, you can quickly eliminate distractors and select the correct answer.
Microsoft Loop enables real-time collaboration with portable components that sync across Microsoft 365 apps.
Loop components are stored in Azure Fluid Relay, not in SharePoint or Exchange.
Loop workspaces are stored in the creator's OneDrive for Business.
Loop is built on the Fluid Framework, an open-source technology.
Up to 50 users can edit a single Loop component concurrently.
Loop is included with most Microsoft 365 subscriptions (Business, Enterprise, Education, Frontline) with no extra license.
Loop is not available in Microsoft 365 GCC/GCC High as of 2024.
Admins can enable/disable Loop via admin center or PowerShell.
Loop components can be shared with external users if policies allow.
Common exam traps: confusing storage location (Azure Fluid Relay vs SharePoint) and licensing requirements.
These come up on the exam all the time. Here's how to tell them apart.
Microsoft Loop Components
Real-time co-authoring with up to 50 users
Portable across multiple apps (Teams, Outlook, Word)
No version conflicts; always current
Stored in Azure Fluid Relay (not a file)
Requires internet connection for live sync
Traditional File Attachments
Requires manual version control; conflicts common
Tied to a single file; must be re-attached
Stale copies if not updated
Stored as .docx, .xlsx, etc. in SharePoint/OneDrive
Can be edited offline; sync later
Mistake
Loop components are just fancy links to a file.
Correct
Loop components are not links; they are live, interactive data containers. When you share a component, you are sharing a reference to a Fluid container that stores the actual data. Editing the component updates the container, and all instances reflect the change. It is not a link to a static file.
Mistake
Loop workspaces are stored in Teams.
Correct
Loop workspaces are stored in the creator's OneDrive for Business, not in Teams. Teams is just one of many surfaces where workspaces can be accessed. The workspace data is stored as a special folder structure in OneDrive.
Mistake
You need a Microsoft 365 E5 license to use Loop.
Correct
Loop is available in Microsoft 365 Business Basic, Standard, Premium, Enterprise E3, E5, Education, and Frontline plans. No additional license is required. However, some advanced security features (like sensitivity labels) may require E5.
Mistake
Loop components cannot be used with external users.
Correct
Loop components can be shared with external users if the organization's external sharing policies allow it. External users need a Microsoft account or Azure AD guest access to edit. View-only access is possible without an account.
Mistake
Loop replaces Microsoft Teams.
Correct
Loop is not a replacement for Teams. It is a collaboration tool that works alongside Teams, Outlook, Word, and other apps. Teams remains the hub for chat, meetings, and calling. Loop enhances those experiences with portable, real-time components.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
A Loop component is a portable, live content unit (like a task list or voting table) that can be embedded in Teams, Outlook, Word, etc. A Loop workspace is a persistent, shared canvas where multiple components and pages are organized. Components are stored in Azure Fluid Relay; workspaces are stored in OneDrive for Business. On the exam, remember that components are for quick sharing, workspaces are for ongoing project collaboration.
Yes, you can insert Loop components into Word documents. Go to Insert > Loop component and choose from the available types. The component appears as an interactive card. Other users who open the document can edit the component in real time. This is a key integration point tested on MS-900.
Yes, Loop components can be shared with external users if your organization allows external collaboration. The external user must have a Microsoft account or be added as a guest in Azure AD. They can edit the component in real time if they have a license or guest access. View-only access is possible without an account.
Admins can manage Loop in the Microsoft 365 admin center under Settings > Org settings > Microsoft Loop. Toggle 'Allow Loop components' on or off. You can also use PowerShell: Set-CsTeamsClientConfiguration -DisableLoopComponents $true to disable in Teams, and Set-OrganizationConfig -LoopComponentsEnabled $false to disable in Outlook. Changes take effect within a few hours.
As of 2024, Microsoft Loop is not available in Microsoft 365 Government Community Cloud (GCC), GCC High, or DoD environments. Microsoft has announced plans to bring Loop to these clouds, but no specific timeline. For the exam, assume Loop is not available in GCC unless stated otherwise.
Up to 50 users can edit a single Loop component simultaneously. This is a specific number you should remember for the exam. If more than 50 users need to collaborate, consider using multiple components or a Loop workspace.
Loop components are stored in Azure Fluid Relay, a cloud service that handles real-time synchronization. They are not stored as files in SharePoint or OneDrive. However, Loop workspaces (which contain multiple components) are stored in the creator's OneDrive for Business. This distinction is important for compliance and data residency.
You've just covered Microsoft Loop and Collaborative Workspaces — now see how well it sticks with free MS-900 practice questions. Full explanations included, no account needed.
Done with this chapter?