Microsoft Loop Licensing: What’s Included in M365, How Workspaces Work, and the Enterprise Cost Reality

Microsoft Loop is included in most M365 commercial plans at no additional charge — but that statement hides several nuances that matter once you start deploying it at enterprise scale. Workspace storage sits on SharePoint, which means it counts against your SharePoint quota. Loop components embedded in Teams, Outlook, and Word are broadly available, but governance controls, compliance integration, and premium features require E5 Compliance or additional Purview licences. And for most organisations, the biggest cost is not licensing — it is the governance overhead you did not plan for.

This guide covers Loop's licensing model in full: what is included in which M365 plans, how workspace and component storage works, what requires additional licences, and how to evaluate Loop's commercial position when making M365 renewal decisions.

What Microsoft Loop Actually Is

Loop is Microsoft's collaborative workspace product. It operates on three levels: Loop components (portable, real-time blocks of content — tables, task lists, paragraphs — that sync everywhere they are embedded), Loop pages (collections of components), and Loop workspaces (shared project spaces that hold pages and files).

The key commercial insight about Loop is that it is not a standalone application like Teams or SharePoint. It is a layer that sits on top of M365's existing infrastructure. Loop components are stored as .fluid files in OneDrive and SharePoint. Loop workspaces are backed by SharePoint. This means Loop's licensing is inseparable from your M365 storage and compliance posture.

Loop competes directly with Notion, Confluence, and Coda in the enterprise collaboration space. Microsoft's positioning is that because Loop is bundled with M365, the total cost of ownership is lower than standalone alternatives. That calculation is correct in licence-cost terms — but it ignores the governance, storage, and compliance complexity that Loop introduces into an M365 environment.

Which M365 Plans Include Loop

The key takeaway: Loop is broadly available across commercial M365 plans. Microsoft does not charge separately for the core Loop experience. If your users have M365 E3 or better, they can create workspaces, build pages, and embed components in Teams and Outlook with no incremental licence cost.

How Loop Storage Works — And Why It Matters Commercially

Every Loop workspace is backed by a SharePoint site. Every Loop component created outside a workspace is stored as a .fluid file in the creator's OneDrive. This is not a technical footnote — it has direct commercial implications for large-scale Loop deployments.

OneDrive Storage for Loop Components

When a user creates a Loop component in Teams, Outlook, or a standalone page, it is stored in a hidden OneDrive folder called "Microsoft Loop." M365 E3 users have 1 TB of OneDrive storage included. For most enterprise users, Loop component storage will be negligible — a typical .fluid file is small, and collaborative documents do not approach the storage sizes of video files or large datasets. However, organisations with heavy Loop adoption across tens of thousands of users should monitor OneDrive storage consumption as part of their M365 storage governance.

SharePoint Storage for Loop Workspaces

Loop workspaces are backed by SharePoint sites. Each workspace provisioned creates a SharePoint site in your tenant that consumes storage from your tenant's pooled SharePoint allocation. M365 E3 includes 1 TB of SharePoint storage plus 10 GB per licensed user. A 5,000-user E3 organisation has 51 TB of pooled SharePoint storage, which sounds like a lot — until large-scale Loop adoption, Teams channel files, SharePoint Online content, and Power Platform Dataverse storage all compete for the same pool.

The commercial risk: if your organisation deploys Loop widely and simultaneously has heavy SharePoint usage, OneDrive sync of large files, and Teams file sharing, you may find yourself approaching SharePoint storage limits faster than expected. Microsoft SharePoint storage licensing allows you to purchase additional storage at £0.20/GB/month, but proactive monitoring is cheaper than reactive purchases.

What Requires Additional Licences

The core Loop experience is included in M365 commercial plans, but several important enterprise features require either M365 E5 or specific Purview add-ons.

Compliance and eDiscovery for Loop Content

This is the most significant licensing gap for regulated industries. Loop content stored in OneDrive and SharePoint can be subject to eDiscovery, Data Loss Prevention (DLP), retention policies, and sensitivity labels — but only if you have the appropriate Purview licences.

With M365 E3: Basic retention policies apply to SharePoint-backed Loop workspaces. Loop .fluid files in OneDrive inherit standard OneDrive retention. However, applying sensitivity labels directly to Loop content, running eDiscovery searches that capture Loop components in transit (embedded in Teams messages), or applying granular DLP to Loop workspaces requires E5 Compliance capabilities.

With M365 E5 or E5 Compliance add-on: Full Purview capabilities apply — sensitivity labels on Loop pages, comprehensive eDiscovery coverage including .fluid files, granular DLP policies, and audit logging of Loop activity at the Premium level.

If your organisation operates in financial services, healthcare, legal, or any sector with document retention obligations, deploying Loop at scale without E5 Compliance creates a compliance gap. Loop content that lives in components embedded in Teams messages may not be captured by E3-level retention policies in the same way as SharePoint documents. This is a known limitation that Microsoft has been progressively addressing — but as of 2026, E5 Compliance is the only way to ensure comprehensive Purview coverage for Loop content.

Guest and External Collaboration in Loop

External users (B2B guests) can be invited to Loop workspaces. The licensing rules follow the same model as SharePoint: the hosting organisation's M365 plan governs access rights. Guest access to Loop workspaces does not require the external user to hold an M365 licence — but it does require that the sharing settings in your tenant allow guest access to SharePoint sites (since Loop workspaces are SharePoint-backed).

If you use Entra ID P1 for guest user conditional access and access reviews, those requirements apply to Loop workspace guests just as they apply to any SharePoint guest. If your organisation has restricted guest access to SharePoint, Loop workspace sharing with externals will similarly be restricted.

Microsoft 365 Copilot in Loop

Copilot capabilities within Loop — AI-assisted content generation, summarisation of Loop pages, suggested action items — require the Microsoft 365 Copilot licence at £24.70/user/month (as of 2026). The Copilot in Loop experience is one of the more compelling Copilot use cases for knowledge workers who use Loop as their primary collaboration surface. However, it requires the full M365 Copilot licence — there is no Loop-specific AI add-on at a lower price point. See our guide to Microsoft 365 Copilot licensing for the full picture.

Loop vs Competing Collaboration Tools: The Commercial Comparison

Microsoft's primary commercial argument for Loop is that it replaces third-party tools (Notion, Confluence, Coda) at no incremental cost because it is bundled with M365. This argument is most compelling when:

Loop's commercial case is strongest when: your organisation already has M365 E3 or E5 and is evaluating a Notion or Confluence contract renewal; your use cases align with Loop's core strengths (meeting notes, project tracking, cross-app content embedding); and you have governance capacity to manage a new collaboration surface within your M365 tenant.

The case weakens when: you have deep Confluence customisation, Jira integration, or developer documentation workflows (Loop does not currently support code blocks, versioning, or developer-centric use cases at Confluence's depth); your teams require robust templating, advanced database views, or complex permission hierarchies (Notion's database and relation features are more mature); or you have compliance requirements that require E5 Compliance, which increases the per-user cost of Loop beyond the headline "free with M365."

The financially correct approach is to use Loop's availability as a negotiating lever in Notion or Confluence renewal conversations — even if you intend to keep the third-party tool. If you can credibly demonstrate that Loop meets 70% of your requirements at zero incremental cost, you have leverage to reduce renewal prices by 15–25%.

Governance: The Hidden Cost of Loop at Scale

The most underestimated cost of deploying Loop at enterprise scale is not the licence fee — it is governance. When Loop is enabled without a formal governance policy, the following problems typically emerge within 12–18 months:

Workspace sprawl: Every user can create Loop workspaces, and each workspace creates a SharePoint site. A 5,000-user organisation that enables Loop without provisioning controls can accumulate thousands of SharePoint sites within months, complicating storage management, security reviews, and the eventual migration to a future platform.

Orphaned content: Loop components embedded in Teams messages persist in OneDrive even after the Teams conversation is deleted. Without a retention policy that covers .fluid files, this content accumulates indefinitely. For organisations under eDiscovery obligations, this is a compliance risk.

Access control complexity: Loop workspaces inherit SharePoint permissions, but components embedded in Teams messages can be shared more broadly than the workspace itself. Tracking who has access to what requires the same tools and processes used for SharePoint governance, extended to a new content type.

Loop Governance Requirements by Compliance Level

Loop in EA Renewal Negotiations

Loop should be part of your M365 licensing strategy at renewal, but not in the way Microsoft would like. Here is how to use Loop commercially:

As a replacement lever: If you are renewing a Notion or Confluence contract at the same time as your Microsoft EA, use Loop's availability to create pricing pressure. Even if you prefer the third-party tool, demonstrating that your IT team has evaluated Loop as a replacement shifts the negotiation. Third-party vendors reduce renewal pricing by 20–30% in competitive situations with M365.

As a reason to avoid E5 upsell: Microsoft's account teams frequently pitch E5 Compliance upgrades by pointing to Loop compliance gaps in E3. The correct counter is to ask Microsoft to enumerate specifically which Purview capabilities you need, price the E5 Compliance add-on at £12.60/user/month, and compare it against the actual compliance requirements your legal and risk teams have articulated — not Microsoft's worst-case scenario framing. In many M365 E3 organisations, a targeted Purview add-on for the 10–20% of users who genuinely need advanced compliance is more cost-effective than upgrading the entire estate to E5.

As a storage governance trigger: If Loop adoption is driving SharePoint storage growth, use that data before renewal to negotiate additional SharePoint storage bundles as part of the EA rather than purchasing at standard consumption rates. Bundled storage in an EA typically costs 30–40% less than post-renewal add-on purchases.

Practical Loop Deployment Checklist

Before enabling Loop organisation-wide, complete these steps to avoid the governance and cost problems that consistently catch enterprises off guard:

1. Verify admin settings are correct. In M365 Admin Center under Settings → Org Settings, confirm Loop is enabled for the user groups you intend. Consider a phased rollout (pilot group first) rather than tenant-wide enablement.

2. Establish workspace creation controls. By default, any licensed user can create a Loop workspace. Use SharePoint site creation controls to limit workspace creation to specific groups or require IT approval for workspace provisioning. This prevents site sprawl.

3. Apply retention policies to .fluid files. In Microsoft Purview, create a retention policy that covers OneDrive and SharePoint with a rule for .fluid file types. This ensures Loop components are subject to the same retention schedule as your SharePoint documents.

4. Assess DLP coverage gaps. If your organisation has DLP policies for SharePoint, confirm that Loop workspaces and OneDrive .fluid files are within the policy scope. E3-level DLP can cover SharePoint-backed Loop content; eDiscovery coverage for Loop components in Teams messages requires E5 Compliance.

5. Monitor SharePoint storage. Add Loop workspace storage to your monthly SharePoint storage governance review. Set an alert threshold at 80% of tenant pooled storage allocation. Review our SharePoint licensing guide for storage optimisation strategies.

6. Evaluate Copilot separately. Do not conflate Loop adoption with Copilot adoption. Loop is included in M365; Copilot in Loop is not. If your pilot teams are using Loop and want Copilot AI features, that is a separate M365 Copilot licence decision. See our Copilot ROI calculation guide before committing to Copilot seats.

Frequently Asked Questions

Does Microsoft Loop cost extra on top of M365?

No. Loop is included in commercial M365 plans including Business Basic, Business Standard, Business Premium, E1, E3, and E5. The core Loop experience — workspaces, pages, and components — has no additional licence fee. Copilot features within Loop require a separate M365 Copilot licence.

Can external guests access Loop workspaces?

Yes, if your tenant allows SharePoint guest access. Loop workspaces are SharePoint-backed, so SharePoint sharing policies govern external access. B2B guests invited to Loop workspaces do not need their own M365 licences, but all guest governance controls (Entra P1 Conditional Access, Access Reviews) apply.

Does Loop replace SharePoint?

No — Loop relies on SharePoint as its storage layer. It is better understood as a collaboration interface that sits on top of SharePoint and OneDrive. You cannot deploy Loop without SharePoint being active in your tenant.

Is Loop available in Microsoft 365 GCC?

Loop availability in GCC environments lags commercial cloud. As of early 2026, some Loop features are available in GCC but not GCC High or DoD. Verify current feature availability in the M365 GCC feature roadmap before planning a Loop deployment in a government environment.

Does enabling Loop affect my SharePoint storage quota?

Yes. Loop workspaces create SharePoint sites that consume your tenant's pooled SharePoint storage. Loop components (.fluid files) in OneDrive consume individual OneDrive storage. For most organisations this is not a problem, but high-volume Loop adoption in tenants already approaching SharePoint storage limits should be monitored.