Why do some (not all) edits to OneNote pages via MS graph return error 20280

Andy Harker 0 Reputation points
2026-10-24T18:13:29.3666667+00:00

Microsoft Graph allows some OneNote pages to be edited (e.g. the title renamed), but not all.

Some pages edits fail with error 20280, but what does this error code actually mean?

Why are pages in some sections successfully editable with no error and others are not?

I can't find a difference between the pages or the sections that work vs. those which do not.

Detail:
PATCH /me/onenote/pages/{id}/content returns HTTP 500 with {"code":"20280","message":"Transient error occured while processing request. {0}"} for pages in almost every section of one notebook (82 sections, ~2,500 pages). It has persisted for over a day and isn't transient. Error 20280 isn't in the OneNote error code documentation.

Microsoft 365 and Office | OneNote | For business | Other
0 comments No comments

1 answer

Sort by: Most helpful
  1. Kristen Tran 2,785 Reputation points Independent Advisor
    2026-11-02T04:01:04.9966667+00:00

    Hi Andy,

    Thank you for sharing the detailed information.

    Error 20280 is not currently documented in the official OneNote API error code reference. Based on previously reported cases, it appears to be an internal OneNote service-processing error returned through as HTTP 500. Similar errors have previously affected other OneNote operations and were treated as service-side issues.

    A successful page update should return 204 No Content. Since the same request works for some pages but fails consistently for others, the issue is more likely related to the internal state of those pages or sections than to authentication, permissions, or the overall request format.

    Please try the recommended tests:

    1/ Test a minimal title update

    PATCH https://graph.microsoft.com/v1.0/me/onenote/pages/{page-id}/content
    Content-Type: application/json
     
    [
     {
     "target": "title",
     "action": "replace",
     "content": "Test title"
     }
    ]
    

    Run the same request against one working page and one failing page.

    For your reference:

    2/ Retrieve the affected page with generated IDs

    GET https://graph.microsoft.com/v1.0/me/onenote/pages/{page-id}/content?includeIDs=true
    

    This will help determine whether the affected page can be read correctly and whether its generated element IDs are available for PATCH operations.

    3/ Copy a failing page

    Copy an affected page to a new section, retrieve the new page ID, and test the PATCH request again. If the copied page works, the original page or section may have an inconsistent backend state.

    4/ Create a new page in an affected section

    If a new page can be updated, the problem is likely limited to existing pages. If the new page also fails, the section itself may be affected.

    Since the error has persisted for more than a day, limited retries with exponential backoff are reasonable, but continuously retrying the same pages is unlikely to resolve an object-specific issue.

    If the problem continues, please contact your IT admin to open a support request and provide the UTC timestamp, request-id, client-request-id, one working page ID, one failing page ID, and the results of the tests above. These details will help the support team investigate the notebook’s backend state.

    They can follow the steps outlined in this article to contact Microsoft Support: Get support – Microsoft 365 admin | Microsoft Learn.

    If you’re unsure who your administrator is, this guide may help: How do I find my Microsoft 365 admin? - Microsoft Support. 

    I hope this information helps. Should you have any further questions, please feel free to let me know.

    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.