Microsoft enforces Dataverse storage limits for Dynamics 365 from 9 November 2026: over-capacity sandboxes can be disabled

Microsoft enforces Dataverse storage limits for Dynamics 365 from 9 November 2026: over-capacity sandboxes can be disabled

1 October 2026 — Microsoft is starting to enforce Dataverse storage capacity for Dynamics 365 customers. A Message Center post published on 30 September 2026 (MC1483519) says staged storage validation rolls out from 9 November 2026 and completes by 4 December 2026. A tenant that goes over its entitled Database, File or Log capacity loses some administrative operations at once, and its sandbox environments can end up disabled.

Not yet independently verified. This rests only on Microsoft’s own Message Center post, read through a public archive because the admin centre requires sign-in. No Microsoft Learn page or independent report of the change was found. We will update this when it can be confirmed, and remove this note.

Who is in scope

The validation applies only to Dataverse-only tenants, meaning tenants with no Dynamics 365 Finance and Operations environment or consumption. The products named are Dynamics 365 Sales, Customer Service, Field Service, Customer Insights, Customer Voice, Contact Center and Project Operations (Dataverse deployments).

What happens when a tenant is over capacity

Microsoft describes three stages, counted from the moment the tenant first exceeds capacity:

Stage	When	Effect
Restricted	Immediately	Environment creation, copy, restore and recover are blocked
Administration mode	After 30 days	Only administrators can sign in to affected sandbox environments
Disabled	After 60 days	Nobody, administrators included, can use affected sandbox environments; the data is kept and can be recovered after remediation

Production environments stay accessible, but the create, copy, restore and recover block applies to them as well while the tenant is over capacity. Sandboxes with active pay-as-you-go billing do not go through the lifecycle. Restrictions lift once the tenant is back below 100% of its entitled capacity. Microsoft says it will send notifications giving the tenant's storage status, the date it first went over, its current stage and upcoming restrictions.

Why it matters

Many organisations have run over their Dataverse entitlement for months with little consequence beyond a warning in the admin centre. From November, the first effect is operational: you cannot copy production into a sandbox or restore a backup while over capacity, which is exactly when a recovery is needed. Partners who build and test in customer sandboxes can find those environments locked to admins and then disabled.

What to do

• Check capacity now in the Power Platform admin centre for Database, File and Log, against the tenant's entitlement.
• Clean up first: audit logs, old system jobs, attachments and unused environments are the usual large consumers.
• Decide which sandboxes matter, and either buy capacity or enable pay-as-you-go billing for them before the 30-day clock can start.
• Tell implementation partners who use your sandboxes about the dates.
• Watch the Message Center for the tenant-specific notices Microsoft says it will send.

Sources

• Microsoft 365 Message Center MC1483519: Dynamics 365 and Power Platform – Information about storage validation for Dataverse-only tenants (public archive copy) — 30 September 2026