MC1483514: Dynamics 365 and Power Platform Add Staged Storage Validation for Dataverse-Only Tenants

---

📢 Official Microsoft Message Center Announcement

---

Dynamics 365 and Power Platform– Information about storage validation for Dataverse-only tenants
Message ID: MC1483514 (Updated)
Beginning November 9, 2026, we are introducing staged storage validation for supported Dynamics 365 applications. The change gives administrators clearer visibility into storage use, advance notice of potential restrictions, and several ways to remain within capacity, including removing unneeded data, adding capacity, or enabling pay-as-you-go for sandbox environments.

If no corrective action is initiated after repeated notifications, when a tenant exceeds its entitled Database, File, or Log capacity, environment creation, copy, restore, and recover operations will be restricted immediately. If the overage remains unresolved, sandbox environments that do not have pay-as-you-go billing enabled will enter Administration mode after 30 days of remaining over capacity, allowing access only to administrators. After 90 days from the date the tenant exceeds capacity, affected sandbox environments will be disabled and will no longer be accessible to users. During this phase customers can contact Microsoft Support for the sole purpose of directing data export options, if needed.

Production environments are not subject to administration mode and disabled stage restrictions and will remain accessible. However, environment creation, copy, restore, and recover operations for sandbox or production type environments will remain blocked while the tenant is over capacity.

Deployment Timeline:

• Rollout begins: November 9, 2026
• Rollout completion: December 14, 2026

How does this affect me?
The Dataverse storage validation applies only to Dataverse-only tenants without Dynamics 365 Finance and Operations environment(s) or consumption. The following products are included in the storage validation rollout:

• Microsoft Dynamics 365 Sales
• Microsoft Dynamics 365 Customer Service
• Microsoft Dynamics 365 Field Service
• Microsoft Dynamics 365 Customer Insights
• Microsoft Dynamics 365 Customer Voice
• Microsoft Dynamics 365 Contact Center
• Microsoft Dynamics 365 Project Operations (Dataverse deployments)

If your tenant exceeds its entitled storage capacity, the following lifecycle applies:

table, td, tr, th {border: 1px solid #243a5e; border-collapse: collapse;} th {text-align: center; background-color: #243a5e; color: #fff;}

Stage	Timing	Impact
1. Restricted	When the tenant first exceeds its entitled storage capacity, known as time zero (T0)	Environment creation, copy, restore, and recover operations for sandbox and production type environments are blocked immediately when the tenant exceeds its entitled capacity.
2. Administration mode	After 30 unresolved days from T0	Only administrators can sign in to *affected sandbox environments. All other users are blocked from accessing the environment.
3. Disabled	After 90 unresolved days from T0	All users, including administrators, are blocked from accessing *affected sandbox environments; the environment data is retained and remains available for recovery after remediation. During this phase, customers can contact Microsoft Support for the sole purpose of directing data export options, if needed. All other mechanisms designed to resolve overage are also available to customers at this phase.

Sandbox environments with active pay-as-you-go billing do not progress through the storage overage lifecycle even if the tenant remains over storage capacity. Other *affected sandbox environments in the tenant may still be affected with restrictions.

We will provide notifications that include the tenant’s current storage status, the date it first exceeded capacity, its current lifecycle stage, future restrictions, and recommended remediation actions.

Admins can exit Administration Mode at any time; however, the overage lifecycle continues as long as the tenant remains over its entitled storage capacity. Once the tenant returns below 100%, no further restrictions are applied. Environments do not automatically return to their previous state; admins must manually exit Administration Mode or re-enable them, as applicable. Processing time may vary depending on the remediation method used.

Sandbox environments with active pay-as-you-go billing are excluded from the overage lifecycle even if the tenant remains over storage capacity.

What action do I need to take?
Review your environment(s) and perform the following actions before November 9, 2026:

• Review Database, File, and Log capacity in the Power Platform admin center.
• Remove or archive data that is no longer needed.
• Establish data governance policies in your environment to help prevent future storage overages.
• Purchase additional capacity or configure pay-as-you-go.
• Invite makers and users to become aware of these potential restrictions and to notify administrators about possible areas of adjustment.
• Review your release activities that depend on sandbox availability, and plan accordingly.

For additional information, please visit the following articles:

• What happens when my organization exceeds storage capacity?
• Dataverse capacity-based storage details
• Manage data with Dataverse governance policies
• Free up storage space
• Add more Dataverse capacity
• Configure pay-as-you-go in your environment
• What environments consume tenant capacity
• Power Platform licensing guidance

*Affected environments: Sandbox environments that do not have pay-as-you-go enabled. Any references to affected environments in this message apply exclusively to those sandbox environments

Source: Microsoft Message Center • Analysed by MWPro

<<< [MC1483514] Archive
Tooltip: View earlier revisions of this post