Is Loop a Paid Add-On
No. Microsoft Loop — the collaborative canvas of components, pages and workspaces — is included in the business and enterprise Microsoft 365 plans most organisations already own: Business Standard, Business Premium, Microsoft 365 E3 and E5, plus Office 365 E1, E3 and E5. There is no standalone Loop SKU to buy and no per-user Loop fee. For a buyer mapping the advanced Microsoft estate, Loop is a feature of a licence you hold, not a new line item — which makes it one of the few Microsoft capabilities where the correct answer to a procurement request is simply do not buy anything.
The only users who cannot create Loop content are those on the most basic plans — for example Microsoft 365 Business Basic users could historically view and contribute to Loop pages shared with them but could not create new workspaces themselves.
What You Actually Need
Loop stores its content in SharePoint Embedded, so the real prerequisite is a SharePoint or OneDrive for Business service plan. Any user with that service plan — included in F1, F3, Office 365 E1/E3/E5 and the Microsoft 365 enterprise plans — can create and manage Loop workspaces.
| Plan | Use Loop content | Create workspaces |
|---|---|---|
| Business Basic | Yes (view/contribute) | Historically no |
| Business Standard / Premium | Yes | Yes |
| Microsoft 365 E3 / E5 | Yes | Yes |
| Office 365 E1 / E3 / E5 | Yes | Yes |
The practical point: if your workforce is on E3, E5 or Business Premium, every user already has everything Loop needs. There is nothing to procure and nothing to attach.
The 2025-2026 Licensing Change
Microsoft removed the separate Loop Workspaces service-plan requirement, making Loop Workspaces a core Microsoft 365 service for any user with a SharePoint or OneDrive plan. The rollout completes in February 2026, and Microsoft confirmed in December 2025 that it had cancelled enforcement of the earlier Workspaces licensing restriction indefinitely.
This matters because it ends a period of genuine confusion. Earlier guidance implied that Loop Workspaces might require a specific service plan and that access could be restricted; that enforcement has now been dropped. For buyers, the result is simpler than the noise suggested — Loop Workspaces are a core entitlement of the plans you already hold, and you should not let a reseller package them as a chargeable extra.
Where the Real Cost Is
The only meaningful Loop-related cost is Copilot. The AI features inside the Loop app — drafting, summarising and reasoning over a page — require a Microsoft 365 Copilot licence at $30 per user per month. That is the same Copilot economics that govern the rest of the suite, and it dwarfs anything Loop itself costs because Loop costs nothing. Treat Copilot in Loop as one more workload in your overall Copilot business case rather than a Loop decision, and weigh it alongside the AI commercial terms we cover for Azure OpenAI. The same collaboration-tooling cost discipline applies to your meeting estate, covered in our Teams Rooms licensing guide.
Tenant Controls and Adoption
Even though Loop is free, it does not arrive ungoverned by default, and the administrative reality shapes whether it costs you anything indirectly. Loop content is created and shared as components that live inside emails, Teams chats and Loop pages, and tenant administrators control creation and sharing through the Microsoft 365 admin centre and the cloud-policy service. A common early decision is whether to enable Loop across the whole tenant immediately or pilot it with specific groups — both are valid, but leaving the default on without a plan is how shadow workspaces accumulate.
The adoption pattern matters commercially because Loop competes directly with tools you may already pay for. Organisations running Notion, Confluence or Coda alongside Microsoft 365 are, in effect, paying a third-party subscription for capability that now ships free inside their existing E3 or E5 estate. A deliberate Loop rollout can therefore retire a paid collaboration tool — a saving that dwarfs anything in the Loop licence itself, because the Loop licence is zero. Treat Loop adoption as a consolidation opportunity, not just a new feature to switch on.
There is no per-feature upsell to fear here: components, pages and workspaces are all part of the core entitlement. The only paid line, again, is Copilot. So the administrative work is about control and consolidation, not cost containment. Map which third-party collaboration subscriptions Loop could replace, decide your tenant-wide enablement and sharing posture, and fold the resulting savings into the wider Microsoft 365 value case rather than letting Loop sit as an unmanaged free feature.
This is also why Loop rarely belongs in a procurement conversation at all. There is nothing to negotiate on the Loop line because there is no Loop line. The genuine commercial decisions sit one level up — the Microsoft 365 plan that includes it, the Copilot business case that extends it, and the third-party tools it lets you cancel — and that is where attention and benchmarking should go.
Governance, Not Licensing
Because Loop is free and ungated, the risk shifts from cost to control. Loop workspaces can proliferate across SharePoint Embedded with little visibility, creating data-governance and retention questions long before they create a licensing one. The work for a CIO is therefore lifecycle policy — ownership, retention and discoverability — not procurement. Map Loop governance alongside your wider Microsoft data controls, benchmark your Copilot business case against the Microsoft vendor intelligence hub and the Microsoft Copilot Guide, and resist any quote that tries to charge you for Loop itself. To stress-test a Copilot rollout that includes Loop, request a confidential briefing.