Share via

Microsoft Export API is no longer returning "Code:PaymentRequired" errors for users not licensed and/or DLP

Siddharth Gautam 860 Reputation points
2026-03-03T19:08:18.36+00:00

This week we have noticed that Microsoft Export API is no longer returning 'Code: PaymentRequired' errors for users not licensed and/or DLP (Data Loss Prevention) Off as before. As a result, we are seeing a spike in MS Teams messages being received and archived. While we realize that Microsoft usage fees and Azure Subscriptions are a thing of the past, and that Microsoft may no longer need to enforce proper licensing, we would expect to still get this error for users with DLP Off. Many customers expect that if DLP is off, Export API will not return their messages and thus not be archived. While we not recommend relying on the Microsoft DLP setting, some customers do use this. Are you aware of the issue and does Microsoft have any statement on this?

Microsoft Security | Microsoft Graph
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Francisco Montilla 30,200 Reputation points Independent Advisor
    2026-04-06T12:20:49.45+00:00

    Hello,

    Just a quick heads up since you are asking for an official Microsoft statement this public forum is actually staffed by fellow users and community members not actual Microsoft employees. We do not have inside access to unannounced backend roadmaps or internal billing service decisions.

    That unexpected spike in your archived messages definitely sounds like an undocumented backend shift in how the Teams Export API evaluates licensing conditions when DLP is disabled. Since there are currently no documented public incidents regarding the PaymentRequired error disappearing we need to grab some more details from your environment to diagnose this properly.

    • What is the exact Graph API endpoint you are using for the message extraction and are you submitting your request using the model A or model B billing parameter?
    • Are you seeing this sudden change occurring globally across all of your customer tenants or if it seems completely isolated to a specific subset of environments?
    • Finally were there any recent modifications applied to the enterprise application permissions or the API scopes within Entra ID on any of the impacted tenants right around the time this spike started?

    Send me those details and we can start isolating what changed on the backend.

    0 comments

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.