Loop storage can outgrow what admins can explain
Reviewed by Helen Jones
Microsoft Loop creates a separate SharePoint Embedded container for each workspace. In a 27 August practitioner report, one lightly used workspace reached about 88 GB while the available admin view did not explain the growth. This is one observed case, not confirmation of a tenant-wide Loop defect.
Small admin teams can see a large container, but may not have the ownership, usage or cost detail needed to decide whether it is normal business activity or a problem. That turns sudden growth into another opaque source of storage pressure and support work. The report does not establish why this workspace grew, so it is a monitoring signal rather than evidence of a product-wide fault. It does show the operational gap: an admin can identify a large SharePoint Embedded container but still need better evidence before choosing to clean up, escalate or simply watch it.
Analysis
Add Loop and SharePoint Embedded containers to your monthly storage review. Flag abrupt growth, record the workspace owner and business purpose, and raise an evidence-backed Microsoft support case before assuming normal user content explains it.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Loop storage can outgrow what admins can explain", Collab365 Spaces.