Sites.selected Require Sites.read.all

Sites.selected Require Sites.read.all can stop normal Microsoft 365 or Office work until you isolate the account, device, and exact error. Use the steps below in order and stay with official Microsoft recovery paths from the source guidance.

When Sites selected Require Sites read all Gets in the Way

Sites.selected Require Sites.read.all is the core issue affecting SharePoint. All is the core issue affecting SharePoint. A Global admin granted registered app explicit write access to specific sharepoint site using graph explorer.

Do This First for Sites selected Require Sites read all

You should also read the subsequent blog article from earlier this year about it.

What Usually Causes Sites selected Require Sites read all

• The Microsoft account in use may not match the purchase, mailbox, or license owner.

• Cached credentials, device policy, or a stalled service check may block the expected action.

• A subscription, permission, or temporary service issue may interrupt the workflow.

Practical Fix Sequence for Sites selected Require Sites read all

When to use this: Follow these steps when the symptoms match and you can access the relevant Microsoft account or escalate through Microsoft Support.

1. You should also read the subsequent blog article from earlier this year about it.

2. Confirm the site, library, file path, and signed-in account are correct.

3. Review permissions, checkout status, required metadata, versioning, retention, and library limits.

4. Test the action in the browser before troubleshooting the sync client or Office desktop app.

5. If the issue affects multiple users, have a SharePoint administrator review service health and audit logs.

Why this helps: The sequence separates identity, permission, and local-client issues before broader reinstall work.

If it still fails: Save the exact error text, account email, and screenshots for Microsoft Support.

Edit Day-to-Day Files in WPS Despite Sites selected Require Sites read all

WPS Office cannot fix Microsoft account sign-in, Authenticator, billing, activation entitlement, OneDrive ownership, or admin locks. Those stay on the Microsoft side.

While that recovery continues, WPS Office can keep local editing moving:

1. Download and install WPS Office.

2. Open Word, Excel, PowerPoint, or PDF files in the matching WPS app.

3. Save a local working copy until Microsoft access returns.

4. Move or sync files back through your normal workflow afterward.

If you need a practical local workspace in the meantime, try WPS Office.

Stay Ahead of Sites selected Require Sites read all Next Time

• Keep a backup verification method on important Microsoft accounts.

• Record which account owns each purchase, mailbox, and device license.

• Sign out of unused Microsoft profiles on shared PCs and update Office regularly.

• Back up critical files before repair, reset, or reinstall actions.

Answers to Frequent Sites selected Require Sites read all Questions

Can WPS Office solve the Microsoft-side failure? No. It helps you keep editing compatible files locally while Microsoft account or service issues are handled in Microsoft tools.

Should I reinstall Office immediately? Usually not. Confirm the account, subscription, and exact error first unless Microsoft guidance for your case requires a reinstall.

What should I send to Microsoft Support? The affected account email, device type, exact error text, and screenshots of the failure.