Microsoft Loop

Microsoft Loop is the portable-content layer of Microsoft 365: pages, workspaces and components, where a component is a list, table or task board that stays synchronized wherever it is pasted - into Teams, Outlook, Word or Whiteboard. Pages and workspaces live in the Loop app at loop.microsoft.com, and everything is stored in OneDrive, SharePoint or SharePoint Embedded, so tenant permissions, retention and quota apply from the first workspace. The AI story has shifted: Microsoft's own comparison page rates Loop's AI integration 'Medium - supports Copilot in some contexts, but not deeply integrated', reserving High for Copilot Pages and Very high for Copilot Notebooks.

Treat Loop as infrastructure you already own, not a Notion substitute. Cost is the trap: Loop rides on the Microsoft 365 subscription you pay for, but the surfaces that make it feel current need more - Copilot Pages require a OneDrive license and a provisioned OneDrive site, Notebooks require Microsoft Copilot or Copilot Chat, and @mentions require an Exchange Online mailbox, so on-premises-only tenants get the degraded copy. Real-time editing also needs WebSocket traffic to *.svc.ms and *.office.com allowed, and admins can disable Loop components. What it is bad at: big structured databases, offline work, and being a destination - once Teams is your workspace, the Loop app has little reason to open. Keep the wiki where it is and use Loop for the live artifact inside the thread you already have.