Copilot keeps telling me, "I couldn't read your document. Please wait a bit and try again."

Because the same Copilot document-reading error affects multiple people in both Excel and PowerPoint, have a Microsoft 365 administrator check tenant Service health before changing or reinstalling individual Office clients.

1. Check for a tenant incident

1. Sign in to the Microsoft 365 admin center with a Service Support admin, Helpdesk admin, or another role permitted to view service health.
2. Go to Health > Service health.
3. Review:
   • Active issues Microsoft is working on
   • Issues for your organization to act on
   • The Issue history tab for a recently resolved Copilot or Microsoft 365 Apps incident
4. If a relevant incident appears, open it and follow its status updates rather than troubleshooting every affected computer separately. Microsoft documents this as the authoritative tenant-specific location for active incidents and advisories.^1^

The public status page does not currently establish a broad incident matching this exact Excel/PowerPoint message, so the tenant dashboard is the important check.^2^

2. Isolate desktop client versus service/network

If Service health shows no matching issue:

1. Open one affected workbook or presentation in Excel or PowerPoint for the web.
2. Run the same Copilot operation.
3. Interpret the result:
   • Web works, desktop fails: concentrate on the Office build, update channel, license refresh, or desktop network path.
   • Web and desktop both fail for several users: concentrate on tenant configuration, licensing, connected-experience policies, or the organization’s network perimeter.
   • Only one document fails: create a new .xlsx or .pptx file in OneDrive and test Copilot there. If that works, preserve both files and escalate the document-specific failure rather than reinstalling Office.

3. Check shared Office configuration

On one affected Windows device:

1. Open Excel or PowerPoint and select File > Account.
2. Under Product Information, install available updates.
3. Check the update channel. Copilot features are not available in Semi-Annual Enterprise Channel; business devices must use Current Channel or Monthly Enterprise Channel. The web apps can be used while IT changes the managed channel.
4. Select Update License, then close and restart every Microsoft 365 application.
5. Under Account Privacy, select Manage Settings and verify that:
   • Experiences that analyze your content is enabled.
   • All connected experiences is enabled.

For organization-managed devices, these privacy and update-channel settings may be controlled centrally and must be reviewed by IT.^3^

4. Test the organization’s network path

If failures correlate with the corporate network, VPN, proxy, or security stack, test one affected user from an approved alternate network. If that succeeds, the network administrator should verify that:

• Microsoft 365 and Copilot endpoints are allowed.
• *.cloud.microsoft and copilot.cloud.microsoft are not blocked.
• Secure WebSocket connectivity works to:
  • *.office.com
  • *.cloud.microsoft
  • copilot.cloud.microsoft
• TLS inspection or aggressive proxy timeouts are not interfering with those connections.

Microsoft specifically notes that blocked WSS, interfering TLS inspection, and proxy timeouts can cause Copilot integrations to fail.^4^

5. Validate entitlement and escalate with logs

If the problem persists without a service incident:

1. An AI administrator can go to Support > Help and support in the Microsoft 365 admin center.
2. Enter copilot missing.
3. Run the Copilot Service Plan Diagnostic for one affected user and confirm that the expected Copilot service plans are assigned.^5^
4. If entitlement is correct, collect logs through Copilot > Settings > Other settings > Copilot diagnostics logs and submit them to Microsoft. Review the submission first because it can include prompts, responses, relevant content samples, and log files.^6^
5. Include the affected users, timestamps with time zones, app/build numbers, desktop-versus-web results, network test result, and sample files that are safe to share.

Avoid an Office reinstall as the initial response: a simultaneous Excel/PowerPoint problem affecting multiple team members should first be separated into tenant service, shared policy/network, and desktop-only branches.

References

1. How to check Microsoft 365 service health
2. Microsoft service health status
3. How to find and enable missing Copilot button in Microsoft 365 apps | Microsoft Support
4. Microsoft Copilot requirements
5. Microsoft Copilot service plan diagnostic tool and service plans for IT admins
6. Configure Microsoft Copilot settings in the Microsoft 365 admin center