The Case of the Massive Loop Container
Why would a seemingly simple Loop workspace develop into a monster SharePoint Embedded container? That’s the question to answer when a Loop container grew to fill nearly 88 GB of SharePoint Embedded storage. The workspace had been through many hundreds of edits, but that’s an unlikely reason to spread and occupy so much storage. Loop and SharePoint Embedded are black boxes when it comes to administration, so we must wait for Microsoft to explain.