I know this has been asked a couple of times before but there is never really a definitive answer. We've got some permanent demo orgs set up in our O365 tenant. As you can imagine, they have minimal records in (either the sample data set or just a few records we've added to be able to show functionality). I've also gone through all the usual space saving exercises like deleting audit logs and old system jobs using recurring bulk deletes but they're still 5GB+ each.
The thing is, what is taking up all the space is actually tables which it would seem D365 requires to run. WebResourceBase (1.5GB), SystemFormBase (1GB), RuntimeDependancyBase (400MB), RibbonClientMetadaBase (390MB).
There doesn't seem to be a way to find out what is taking up all the web resource space. If it was a certain managed solution maybe we could evaluate whether it was necessary to keep or not.
Why are these tables coming out of our storage allowance if we can't do anything about how big they are? Why are they so massive? 1GB+ for some system forms? nearly 400MB for some ribbon metadata? It seems bit harsh that we must pay for this stuff as storage.
Has anyone got anywhere raising this as a support case and getting Microsoft to dig into the back end and find out?