What is Microsoft Loop? A Practical Guide to Collaborative Workspaces in M365 E3/E5

About this article
This article was created using an automated generation workflow leveraging generative AI. It reviews Loop requirements, storage locations, and management/compliance information from Microsoft Learn, summarizing key points for users and administrators when using Loop in Microsoft 365 E3/E5.

Verification Status: 📘 Microsoft Official Information Verified / Tenant Settings & Cloud Environment Need Verification / Not Verified on Actual Devices

Microsoft Loop is a tool for multiple people to co-create and develop information that is not yet finalized in real time.

Word is suitable for finalized documents, Planner for tasks with assigned owners and deadlines, and SharePoint for storing organizational records. Loop, on the other hand, is designed for "pre-decision" collaboration, such as pre-meeting discussion points, early-stage project notes, and tables or checklists that evolve over time.

Four Key Terms to Learn First

In Microsoft Learn, current Loop files are described as .loop files. Even if you see the name .fluid used in earlier releases, this article will refer to .loop as the standard.

Where Loop Data is Saved Matters

An important point in understanding Loop is that not all Loop data is saved in the same location just because it is "Loop." Depending on where it is created, data is stored in SharePoint Embedded, SharePoint sites, or OneDrive.

flowchart LR
    U[利用者]
    LA[Loopアプリ]
    TC[Teamsチャネル]
    TP[Teamsプライベートチャット]
    O[Outlook]
    SPE[(SharePoint Embedded)]
    SP[(SharePointサイト)]
    OD[(OneDrive)]

    U --> LA
    U --> TC
    U --> TP
    U --> O
    LA --> SPE
    TC --> SPE
    TC -. 会議・チャネル内の一部 .-> SP
    TP --> OD
    O --> OD

Typical examples are as follows:

This distinction is not just for IT departments. When considering offboarding, retention, eDiscovery, sharing, storage capacity, and access control, the starting point is always: "Where is this Loop data stored?"

How to Approach This in M365 E3/E5?

Under current Microsoft requirements, Loop components require a OneDrive or SharePoint license. Loop workspaces require an eligible license that includes the Loop with workspaces service plan.

While Microsoft 365 E3/E5 are eligible plans, upgrading to E5 does not mean Loop itself suddenly gains significantly more advanced features. First, verify your contracted SKU, the service plans assigned to users, and your management policies.

In particular, it is crucial not to treat Office 365 E3/E5 and Microsoft 365 E3/E5 as the same. Administrators should verify the actual SKUs and service plans in the Microsoft 365 admin center.

What Network Administrators Need to Know

Loop's real-time co-authoring relies on WebSocket communication. In addition to the standard Office 365 URL and IP requirements, Microsoft Learn advises allowing WebSocket traffic to *.svc.ms and *.office.com.

sequenceDiagram
    participant A as 利用者A
    participant M as Microsoft 365 / Loop
    participant B as 利用者B
    A->>M: 表のセルを更新
    M-->>B: WebSocket等で変更を反映
    B->>M: チェック項目を完了
    M-->>A: 変更をリアルタイム反映

If you encounter an issue where "only Loop edits are not reflecting in real time," troubleshooting should isolate not only the app itself but also proxies, firewalls, and WebSocket controls.

Try This First: A 3-Item Collaborative Note

If you have an environment where you can create a test workspace or page, place just the following three items:

目的
確認したいこと
次のアクション

Add three checklist items under "Things to Verify" and share it with one test partner.

What to Look For

• The other person's changes are reflected on your screen in real time.

• The list of shared users contains only the intended people.

• The content remains intact even after closing and reopening the page.

• Keep track of where you created the Loop from.

Try Changing One Thing

Convert one checklist item into a table and add an "Owner" column. A key feature of Loop is how easily you can change the structure of information on the fly.

Practical Example: Organizing Discussion Points for M365 Migration

For example, when preparing to migrate to a new Microsoft 365 environment, writing a formal specification document from the start can make unresolved issues look like they have already been finalized.

In Loop, you can categorize them as follows:

Once the content is finalized, you can move formal specifications to Word, tracking tables to Lists, and action items to Planner. Positioning Loop not as the "final deliverable" but as a "workspace for thinking" makes it much easier to adopt.

Different Perspectives for End Users, Business Staff, and IT Admins

Do Not Assume Purview Applies Uniformly Across the Board

While Loop supports Microsoft Purview features like retention, eDiscovery, sensitivity labels, and DLP, the scope of support for some features varies depending on where the data is stored.。

For example, Microsoft Learn notes that Information Barriers (a mechanism that restricts searching, communication, and collaboration between specific groups) apply to Loop data stored in OneDrive/SharePoint, but are not supported in SharePoint Embedded containers.

Sensitivity labels can be applied to Loop components and pages, and container-level labels can be used for Loop workspaces. However, note that files uploaded to a workspace—whose actual files are stored in the user's OneDrive—are not protected by the workspace's container label alone.

In other words, administrators should not simply look at "Loop supported/unsupported," but should verify in the following order:

flowchart TD
    A[対象のLoopデータを特定] --> B{どこで作成した?}
    B --> C[SharePoint Embedded]
    B --> D[SharePointサイト]
    B --> E[OneDrive]
    C --> F[対象Purview機能の対応表を確認]
    D --> F
    E --> F
    F --> G[必要ライセンスとポリシーを確認]

Read-Only Focus: Checking Connection Permissions with Microsoft Graph PowerShell

Rather than making sudden changes to Loop itself, validation using Graph should start by checking the current connection context.

Connect-MgGraph -Scopes "User.Read"
Get-MgContext | Select-Object Account, TenantId, Scopes

What to Look For?

Account、TenantId、Scopes to verify "which tenant you are connected to and with what permissions."

Success Criteria

The expected account and tenant are displayed, and User.Read is included in Scopes, then this verification is successful. No operations to modify Loop data will be performed.

The Value of Changing One Thing

Connecting and comparing with a different test account allows you to verify whether you have mistaken the target tenant before troubleshooting "why the app is visible or not." Instead of adding permissions indiscriminately, start with the minimum privileges required for your objective.

Prompt for Creating a Draft Loop Page with Generative AI

新しいプロジェクトのLoopページを作ります。
次のメモを「目的 / 決まっていること / 未決事項 / 次に確認すること」の4つに分類してください。
元のメモにない決定事項は追加せず、推測は「推測」と明示してください。
各項目に、正式文書へ移すべきタイミングも1行で提案してください。

[メモ]

Since Loop often handles work-in-progress information, explicitly instruct the AI not to present assumptions as finalized facts.

Checklist for Administrators

• Actually assigned Microsoft 365 SKUs and Loop service plans

• OneDrive / SharePoint licenses

• Presence of Exchange Online mailboxes

• Loop creation policies via Cloud Policy and SharePoint PowerShell

• Settings on the host side where Loop is embedded (Teams, Outlook, etc.)

• Office 365 URLs/IPs and WebSocket communication

• Where data is stored (SharePoint Embedded, SharePoint, or OneDrive)

• Support scope for retention, eDiscovery, sensitivity labels, DLP, and Information Barriers

• Lifecycle of Loop data owned by offboarded or transferred employees

• Additional requirements when using Copilot Pages / Copilot Notebooks

Official Information / Primary Sources

• Requirements for Loop components and Loop workspaces – Microsoft Learn

• Overview of Loop storage – Microsoft Learn

• Summary of governance, lifecycle, and compliance capabilities for Loop experiences – Microsoft Learn

• Use sensitivity labels with Microsoft Loop – Microsoft Learn

• Manage Loop in your organization – Microsoft Learn

Loop is a continuously updated service. This article is based on official Microsoft information as of September 17, 2026. Since admin portals, cloud environments, rollout status, and Purview feature support scopes are subject to change, please re-verify the primary sources above and your own tenant during actual deployment.