OneDrive account returning "accessDenied / serviceReadOnly - Database Is Read Only" on all metadata/drive API calls (personal account, Linux clients)

Question

I'm getting a persistent accessDenied error with inner error code serviceReadOnly and message "Database Is Read Only" whenever any third-party client tries to query drive metadata or mount my OneDrive account via the Microsoft Graph API.

Account details:

• Personal Microsoft account (OneDrive Personal, not Business/M365 org account)
• Storage: 243.2 GB used of 1 TB (23%) — well within quota
• No warnings shown in the OneDrive web interface (onedrive.live.com) regarding license, storage, or account status

Error details (from rclone):

Failed to query available drives: HTTP error 403 (403 Forbidden) returned body: "{\"error\":{\"code\":\"accessDenied\",\"message\":\"Database Is Read Only\",\"innerError\":{\"code\":\"serviceReadOnly\",\"date\":\"2026-08-22T01:25:48\",\"request-id\":\"[PII removido]\",\"client-request-id\":\" [PII removido] \"}}}" 

What I've tried:

• Reproduced with multiple independent clients using different OAuth app registrations: rclone (default client ID), GNOME Online Accounts / gvfsd-onedrive (GNOME's client ID)
• Fully removed and re-added the account in GNOME Online Accounts (fresh OAuth token) — error persists
• Verified the account works normally through the OneDrive web interface (browsing, uploading files manually)
• Verified the abraunegg/onedrive Linux client (a separate open-source sync client, different OAuth app registration) is able to authenticate and successfully perform incremental uploads without hitting this error

Observations:

• The error appears specific to drive listing/metadata query operations (/me/drives or similar), not all API operations, since upload-only sync via abraunegg still works
• This affects the account itself, not a specific client, since it's reproducible across completely unrelated OAuth applications
• I've seen other users reporting the same "Database Is Read Only / serviceReadOnly" error recently, which suggests this may be a server-side issue affecting multiple accounts, not something specific to my account configuration

Questions:

1. Is this a known, ongoing server-side issue?
2. Is there a way to check if my account has been placed into a read-only/restricted state, and if so, why (given there's no license or storage warning)?
3. What steps can I take to restore full read/write metadata access?

Any guidance would be appreciated. Thanks!

Answer 1

(Please note that this is Brazilian Q&A Forum, any threads should be posted in Portuguese. However, I will still provide an answer in English based on your initial response.) 

Hi, Cleiton Moya de Almeida

This does not look like a storage, license, Linux, or OAuth-token problem. The evidence points to a Microsoft Graph service issue affecting the plural /me/drives endpoint for some personal accounts, while /me/drive and normal web access continue working. The same behavior has been reproduced in Graph Explorer. rclone issue #9794

Here are some suggestions you can try:

Test both endpoints in Microsoft Graph Explorer: GET /v1.0/me/drive GET /v1.0/me/drives

If only the plural endpoint fails, use /me/drive where the client permits it. For rclone, update to the latest beta and monitor the linked issue for a fix or workaround.

Reauthorizing repeatedly is unlikely to help because unrelated applications return the same service-side response.

If it continues, contact https://support.microsoft.com/home/contact while signed into the affected personal account. Include the exact UTC timestamp, request ID, client-request ID, failing endpoint, and confirmation that /me/drive works but /me/drives fails. Those details are needed for backend investigation.

Please be advised that this is a user-to-user support forum. Moderators and contributors, including external Microsoft employees, are not allowed to directly interfere with Microsoft product features or access back-end systems. Our role is limited solely to providing technical guidance on reported incidents, requests, or ideas.   

Thank you for your patience in reading, I hope this information has been helpful to you. 

---

If the answer is helpful, please click "Yes" and kindly upvote it. If you have extra questions about this answer, please click "Comment."    

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Olá, primeiramente desculpe por não me atentar que que o fórum era somente de perguntas em PT-BR, e obrigado por responder mesmo assim. As respostas foram muito úteis para isolar o problema!

Fiz o teste sugerido no Graph Explorer, logado com minha conta pessoal e o resultado confirma exatamente a hipótese da primeira resposta:

• GET /v1.0/me/drive (singular) → 200 OK, retorna os dados corretamente
• GET /v1.0/me/drives (plural) → 403 Forbidden

Dados do erro 403:

• Request ID: [PII removido]
• Client-request-id: [PII removido]
• Data/hora do teste: 2026-08-23

Ou seja, no meu caso específico, o problema parece estar isolado ao endpoint plural /me/drives — o singular funciona normalmente, mesmo com um app de consentimento recente (Graph Explorer). Isso confirma também o que estou vendo na prática: o onedrive, de abraunegg- que usa apenas o endpoint singular, continua funcionando normalmente. Vou verificar agora se consigo ajustar o rclone e o gvfsd-onedrive para evitar depender do endpoint plural até que a Microsoft resolva isso.

Fico no aguardo caso haja alguma atualização sobre esse bug específico do /me/drives. Obrigado novamente pela ajuda em isolar a causa!