Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 08:27 UTC Customize Public modeDiscuss ChangeIntel on Discord

Dynamics 365 and Power Platform– Information about storage validation for Dataverse-only tenants

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 12 Oct 2026 December 4, 2026 → December 14, 2026

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
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: 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.Restrictions are removed after the tenant has returned below 100% of its entitled storage capacity. Processing time may vary depending on the remediation method used. 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. Inform administrators, makers, and users about the potential restrictions. 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.

What changed

Between archive captures, newest first
    • Tags Admin impact → Updated message, Admin impact

    … capacity, including removing unneeded data, adding capacity, or enabling pay-as-you-go for sandbox environments. Whenenvironments.If no corrective action is initiated after repeated notifications, when a tenant exceeds its entitled Database, File, or Log capacity, environment creation, … 30 days of remaining over capacity, allowing access only to administrators. After 60 days, those90 days from the date the tenant exceeds capacity, affected sandbox environments will be disabled, preventing accessdisabled and will no longer be accessible to users. During this phase customers can contact Microsoft Support for all users. Productionthe sole purpose of directing data export options, if needed.Production environments are not subject to theseadministration mode and disabled stage restrictions and will remain accessible. However, environment creation, copy, restore, and recover operations for sandbox or production type environments will still be remain blocked while the tenant remainsis over capacity. Deployment Timeline:Rollout begins: November 9, 2026 Rollout completion: December 4,14, 2026 How does this affect me? The Dataverse storage validation applies only … Dataverse-only tenants without Dynamics 365 Finance and Operations environment(s) or consumption. The following products in-scope ofare included in the storage validation include:Microsoftrollout:Microsoft Dynamics 365 Sales Microsoft Dynamics 365 Customer Service Microsoft Dynamics 365 Field … known as time zero (T0) Environment creation, copy, restore, and recover operations for sandbox and production type environments are blocked 2. Administration mode 30 days after the tenant first exceeds capacity -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 6090. 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 remediationremediation. 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.lifecycle even if the tenant remains over storage capacity. Other *affected sandbox environments in the tenant may still be affected with restrictions. We restrictions.We will provide notifications that include the tenant'stenant’s current storage status, the date it first exceeded capacity, its current lifecycle stage, upcomingfuture restrictions, and recommended remediation actions. Restrictions actions.Restrictions are removed after the tenant has returned below 100% of its entitled storage capacity. Sandbox environments with active pay-as-you-go billing are excluded from the lifecycle even if the tenant remains over storage capacity. Processing time may vary depending on the remediation method used. …

  1. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 08:27 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current