Long-standing Microsoft 365 E5 Developer tenant suddenly blocked by PolicyViolationThrottle — 1.6+ TB of existing OneDrive data now inaccessible and eDiscovery export failing

Question

Long-standing Microsoft 365 E5 Developer tenant suddenly blocked by PolicyViolationThrottle — 1.6+ TB of existing OneDrive data now inaccessible and eDiscovery export failing

Prateek Bhatia 0

The situation

I’m the Global Administrator of a long-standing Microsoft 365 E5 Developer Program tenant that has been active for several years.

Recently, OneDrive/SharePoint access was restricted with:

PolicyViolationThrottle | PolicyViolationThrottle.htm#1033

My primary concern is data recovery, not restoring the previous storage entitlement.

What makes this unusual

The tenant had historically operated with a much larger OneDrive storage allocation.
I did not receive or notice an actionable warning explaining that my existing data would become subject to a significantly lower storage limit before the restriction occurred.
Microsoft Support has already investigated the issue, including Tier 2 escalation and consultation with Microsoft engineering.
I was directed to Microsoft Purview eDiscovery as the recovery method.

The important part is that Purview can still see the data:

~1.6+ TB of content is discoverable in the affected OneDrive sites.

However, when I attempted an eDiscovery export, the export completed, but the available package was only ~5 KB, appearing to contain reports/metadata rather than the actual files.

So I currently have this situation:

Microsoft's systems can discover hundreds of GB of my existing OneDrive data, but I have no working way to retrieve it.

What I need clarification on

What exact storage entitlement was applied to this tenant when the restriction was triggered?
Was there a backend policy/entitlement transition for existing Developer tenants?
What notification/warning was generated before enforcement, and through which channel?
Why can Purview discover ~1.6+ TB, but the eDiscovery export is not producing the actual files?
Is there a SharePoint/OneDrive, Developer Program, storage, policy-enforcement, or data-recovery engineering team that can assist with recovering the existing content?

I understand the current Microsoft 365 Developer Program documentation describes a 300 GB pooled tenant limit. My question is specifically about the transition/enforcement on existing tenants and recovery of data that was already stored before the restriction.

I am not asking Microsoft to restore unlimited storage. I am asking for a supported way to recover my existing data.

I can provide screenshots, eDiscovery results, export reports, and my existing Microsoft Support case details privately if needed.

Any guidance from a Microsoft engineer familiar with Developer Program storage enforcement, PolicyViolationThrottle, SharePoint/OneDrive, or eDiscovery recovery would be greatly appreciated.

Prateek Bhatia 0 Reputation points

2026-09-09T21:39:04.8866667+00:00

Important: I am not primarily asking for the storage limit or tenant restoration. My immediate priority is recovering the existing data. Purview can still discover approximately 1.6+ TB in the affected OneDrive, but the eDiscovery export is currently producing only a ~5 KB report package instead of the actual files. I would greatly appreciate help from a Microsoft engineer/team who can advise on the supported backend recovery path.
Prateek Bhatia 0 Reputation points

2026-09-10T20:48:01.67+00:00

Update: Microsoft Support has now confirmed that the case was escalated to Microsoft engineering/Tier 3, but engineering declined both temporary tenant reactivation and any alternative Microsoft-side data-recovery method. The data remains discoverable through Purview (~1.6+ TB), but I still cannot retrieve it.

1 answer

Your answer

Prateek Bhatia 0 Reputation points

2026-09-09T21:39:04.8866667+00:00

Important: I am not primarily asking for the storage limit or tenant restoration. My immediate priority is recovering the existing data. Purview can still discover approximately 1.6+ TB in the affected OneDrive, but the eDiscovery export is currently producing only a ~5 KB report package instead of the actual files. I would greatly appreciate help from a Microsoft engineer/team who can advise on the supported backend recovery path.
Prateek Bhatia 0 Reputation points

2026-09-10T20:48:01.67+00:00

Update: Microsoft Support has now confirmed that the case was escalated to Microsoft engineering/Tier 3, but engineering declined both temporary tenant reactivation and any alternative Microsoft-side data-recovery method. The data remains discoverable through Purview (~1.6+ TB), but I still cannot retrieve it.

Answer 1

Hendrix 990 Independent Advisor

Hi Prateek,

Thank you for your detailed sharing.

Since you mentioned that "Microsoft Support has already investigated the issue, including Tier 2 escalation and consultation with Microsoft engineering.", does that mean you have created a support ticket and contacted a support agent?

If that's the case, please actively keep in touch with the support agent, as he/she can initiate a remote session, review backend settings, and have the expertise to perform in-depth troubleshooting and provide appropriate solutions.

If you haven't submitted a support ticket, please refer to: Get support - Microsoft 365 admin | Microsoft Learn for detailed guidance on how to open a support ticket with Microsoft Support.

Please understand that this is a user-to-user community forum. As a sole user here, I don't have access to your environment or Microsoft's backend systems, so I can only provide guidance based on public documentation and community experience. In this case, the best next step is to create a Support Ticket directly with Microsoft Support and request advanced assistance from the support agent.

Hope you're able to get this resolved soon.

Prateek Bhatia 0 Reputation points

2026-09-10T20:46:14.58+00:00
Hi Hendrix,

Thank you for the response. I have now followed the exact route you suggested.

I have an active Microsoft Support case and have already worked with multiple support engineers. The case was escalated to Tier 2 and subsequently consulted with Microsoft engineering (Tier 3).

Unfortunately, I have now been informed that Microsoft engineering has declined both options I requested:

Temporarily reactivating/unblocking the tenant so I can download my existing data

Providing any Microsoft-side mechanism to recover/export the existing OneDrive data

The reason provided was that the tenant was determined to have violated the applicable policies, and therefore Microsoft considers the restriction final. I specifically asked the support engineer to raise the fact that I did not receive or notice any warning/notification before the restriction, but I was told that engineering's position was that agreeing to the Developer Program terms means the policy applies regardless.

This leaves me in a particularly difficult situation because Microsoft Purview was able to discover approximately 1.6+ TB of existing OneDrive content, yet the eDiscovery export produced only an approximately 5 KB report package rather than the actual files.

At this point, Microsoft Support has told me that they have exhausted all available resolution options from their side.

So my question is no longer simply "how can I troubleshoot this?"

Is there any Microsoft team, escalation channel, or data-recovery process outside the standard Microsoft 365 Support workflow that can review a case where the data remains discoverable in Microsoft's systems but the tenant owner has no supported way to retrieve it?

I fully understand that this is a user-to-user community and that you don't have access to my tenant. I'm posting this update because the situation has now progressed beyond normal troubleshooting, and I would appreciate any direction toward the appropriate Microsoft team or escalation path.
Hendrix 990 Reputation points Independent Advisor

2026-09-10T22:51:23.0266667+00:00

Hi Prateek,

Thank you for the update, and I'm truly sorry about your situation.

As this is a community forum, I generally do not have access to Microsoft's internal systems, backend tenant information, engineering notes, or investigation results. As such, only Microsoft Support and Engineering can definitively determine what recovery options are or are not available in your specific case.

I may be able to offer suggestions based on similar experiences, but I cannot validate or overturn an engineering decision. Any further review, exception request, or escalation would ultimately need to come from Microsoft. If the engineering team said that they have exhausted all available resolution options from their side, unfortunately, I'm sorry to say that there isn't anything I can do to help you in this situation.