Share via

How to resolve a "FraudThrottle.htm#2057" error

Adrian Anastas 5 Reputation points
2026-04-22T08:29:08.2666667+00:00

I have a Developer environment that I use for building and testing API integrations to M365 products.

On Monday at 4:30 AM one of my integrations reported an access error, and then when investigating I now get this error trying to access the Sharepoint site:

Access Denied

This page has been blocked as it violates the Acceptable Use Policy located in the Terms of Use. If you believe this is a mistake, please contact our Support team using M365 Admin Center for further assistance.

How can I get this resolved? Any advice would be appreciated.

Microsoft 365 and Office | Development | Microsoft 365 Developer Program

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Gabriel-N 17,785 Reputation points Microsoft External Staff Moderator
    2026-04-22T09:38:20.8666667+00:00

    Hello Adrian Anastas

    Recently, the forum has received quite a number of reports related to Acceptable Use Policy (AUP) enforcement, and in this week, we’re also starting to see more cases related to FraudThrottle errors.

    To be honest with you, and I hope you can understand, this is a user-based community forum. As a forum moderator, I do not have access to Microsoft’s internal systems required to investigate individual account‑level issues due to privacy and security constraints. Because of this, I’m unable to manually reset, override, or influence Developer Program eligibility or tenant status.

    Based on my research, the best approach is:

    • Open a support ticket and request escalation to the relevant backend team
    • Continue following up with Microsoft for clarification on what triggered the block
    • Back up all critical data as a precaution (if access is still partially available)

    For the specific case of FraudThrottle.htm#2057, I would also recommend checking whether you’re able to create a support ticket directly from the affected tenant. There have been reports from some users that the support option may be greyed out in this situation. If you encounter the same issue, you may consider the following alternatives:

    User's image

    Additionally, you might consider taking a look at this active thread, the original poster and other users have shared their experience on how to raise a support ticket to the right team when encountering AUP enforcement, and even provided scripts that may help in some cases: Acceptable Use Policy violation notice on Microsoft 365 Developer E5 sandbox - SharePoint read-only at farm level

    I hope these suggestions can help you move forward, at least partially. If you have any updates, feel free to share them here, the community would really appreciate it.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

  2. AI answer

    2026-04-22T08:29:38.04+00:00

    "FraudThrottle" and the Acceptable Use Policy (AUP) message indicate that the tenant or specific activity has been flagged and blocked at the service level by Microsoft, not by any SharePoint configuration in the site, library, or code.

    Resolution requires Microsoft support intervention; it cannot be fixed from SharePoint admin settings, site settings, or by changing code.

    Recommended steps:

    1. Stop or reduce the offending traffic
      Because the error is tied to throttling/abuse protection, immediately pause any custom integrations, scanners, or automation that are calling SharePoint/OneDrive at high volume or high frequency. This aligns with the throttling and blocking behavior described for SharePoint Online:
      • Excessive or long‑term high traffic can cause throttling (HTTP 429/503) and, in more extreme cases, a block at app or user level.
      • Blocks are applied to protect the overall health of the service and remain until the offending pattern is changed. See the throttling behavior and limits in Avoid getting throttled or blocked in SharePoint Online.
    2. Check for a block notification in the tenant
      When SharePoint Online blocks a subscription, a message is posted in the Microsoft 365 Message Center:
      • The message explains what caused the block, gives guidance on how to fix the offending process, and who to contact to remove the block.
      • Review that Message Center post carefully and adjust the integration accordingly (for example, reduce call rate, add backoff/retry honoring Retry-After, avoid bulk scanning patterns, etc.). This is described under "What should you do if you get blocked in SharePoint Online?".
    3. Open a support ticket from the M365 Admin Center
      The AUP message explicitly instructs contacting Support via the Microsoft 365 Admin Center. That is required for:
      • Confirming that the issue is indeed an AUP/block action and not a transient throttling spike.
      • Having the case escalated to the appropriate backend team to review and, if appropriate, remove or adjust the block.
      Practical guidance based on similar AUP/block cases:
      • Prepare screenshots of the exact error (including any FraudThrottle.htm#2057 reference) and affected SharePoint URLs.
      • Be ready to describe:
        • The nature of the integration (what APIs, what operations).
        • When the issue started (exact time, as in your 4:30 AM event).
        • Any recent changes to scripts, tools, or load patterns.
      • During the support session, support may collect logs and escalate to an internal backend team; resolution typically requires that escalation.
    4. Adjust the integration to avoid future throttling/blocks
      After support confirms or removes the block, adjust the integration to comply with SharePoint Online throttling guidance:
      • Implement exponential backoff and always honor the Retry-After header when receiving HTTP 429 or 503.
      • Avoid high‑frequency or bulk operations that scan or modify large volumes of content without optimization.
      • Ensure the integration does not resemble unsupported patterns (for example, using SharePoint/OneDrive as a generic intermediary for another repository) and does not run load tests against SharePoint Online.
    5. Monitor for service‑level issues
      If multiple users or apps see intermittent 503/"Server is busy" errors (separate from the AUP message), check the Service Health Dashboard in the Admin Center to rule out broader service incidents.

    Because an AUP/FraudThrottle block is enforced at the service level, only Microsoft support can confirm the reason and remove or relax it after the integration has been corrected.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.