… 8 unchanged lines …
  - Overflow works in one direction only: spare database capacity can cover a log or file deficit, and spare log can cover file. Spare **file** capacity covers nothing.
  - Notifications fire weekly at under 15% remaining, again at under 5%, and again once you're in overage. Tenant, Power Platform and Dynamics 365 admins all get them and nobody can opt out.
  - In overage, these operations stop: create an environment, copy an environment, restore an environment, convert a trial to paid, recover an environment, add a Dataverse database. Several of those need at least 1 GB free.
+ - Borrowing counts towards notifications: for the warning calculation, spare capacity from another bucket is added to the short bucket's entitlement. If Log is at 130 GB against 100 GB and Database has 40 GB spare, Log's effective entitlement is 140 GB, it's at about 93% used, and you still get the under-15%-remaining banner even though you're not over capacity and nothing is restricted.
+ - The 85% threshold drives that arithmetic: a bucket needs an effective entitlement of its consumption divided by 0.85 to avoid a notification, and borrowing only helps if enough spare exists.
+ - Overage runs on a clock from the day the tenant first exceeds 100% effective consumption (T0). Stage 1 (Restricted) blocks create, copy, restore and recover. At 30 days from T0 affected sandboxes go to Administration mode, and at 90 days from T0 sign-in to them is blocked for everyone, admins included, though the environment and data are kept.
+ - Admins can lift a sandbox out of Administration mode to do remediation, but the timer keeps running. Sandboxes with pay-as-you-go enabled don't progress through the lifecycle.
  - Admins can preallocate capacity to a specific environment. Overage against a preallocated amount is currently soft enforcement only — email at 85% of allocation — but it reduces what's left in the tenant pool for everyone else.
  - Default, production and sandbox environments count towards consumption. Trial, preview, support, developer and Teams environments don't.
  - Microsoft states there's no technical limit on the size of a Dataverse environment. The numbers in the admin centre are entitlement limits, not engineering ones.
    … 13 unchanged lines …
  - File capacity excess can't rescue a database or log deficit. Clients with piles of spare file capacity still get blocked.
  - The default environment's list view shows only consumption *above* its included quota, so it reads as 0 GB until it isn't. Open the Details pane to see actual usage.
  - Team Member licences give no per-user database, file or log entitlement, so they don't appear in the entitlement breakdown. Expect that question.
+ - The Disabled stage isn't a cliff you can ignore. If sandboxes are locked, return the tenant to compliance and then re-enable them; Microsoft says you can contact support about data export options in the meantime.
  - Environments without a Dataverse database still consume 1 GB each. Tenants with dozens of empty environments lose real capacity to them.
  
  ## Consultant notes
  - Run the per-table breakdown at the start of any storage conversation. It converts an abstract argument about buying capacity into a specific argument about a specific table.
  - Warn clients that audit is the most common cause of a log capacity crisis, and that it grows in proportion to transaction volume, not data volume. Nobody expects this.
  - Never quote add-on pricing. Point at the Power Platform and Dynamics 365 licensing guides and let procurement do procurement.
+ - Put the overage clock in the client's runbook. Stage 2 starts at 30 days, the lock at 90, and "we were waiting on procurement" isn't a recovery plan.
  - Downloadable capacity reports expire after 30 days. If you're building a trend, capture the export on a schedule rather than trusting the portal to remember.
  
  ---