Check Microsoft’s service-health page first; if no active Copilot incident is listed, refresh or restart Copilot and isolate whether the failure follows your account, browser, or device. ^1^
1. Check whether the outage is ongoing
Open Microsoft service health status and look for an active Copilot incident.
- Incident shown: Wait for Microsoft to mark it resolved, then fully close and reopen Copilot.
- No incident shown: Continue below. A previous outage may explain when the problem began, but it does not confirm the current cause.
2. Reset the current Copilot session
- On the web, refresh the page; in the app, quit it completely and reopen it.
- Sign out, then sign in using the same account and sign-in method previously used:
- Select Continue with Google or Continue with Apple when that was the original method.
- Use the account switcher to distinguish personal accounts from work or school accounts.
- Follow any migration or content-moving message displayed inside Copilot.
Microsoft notes that previous chats may temporarily be unavailable while content moves to the updated Copilot app. That could explain old chats not loading, but it does not by itself explain why new chats also fail. ^2^
3. Test account migration and browser state
If this is a personal account—particularly if you use multiple accounts:
- Open a private or incognito browser window.
- Go to copilot.microsoft.com.
- Sign in with the affected personal account.
- Check the result:
- If the browser remains at
copilot.microsoft.com, continue using Copilot there for now.
- If it redirects to
copilot.com, the account has moved or is completing its move to the updated experience.
Also test another browser or device. If Copilot works there, the problem is isolated to the original client rather than the account or service.
4. Run the connectivity check on Windows
If using Windows:
- Open the Get Help app.
- Search for Copilot connectivity troubleshooter.
- Run it and apply any recommended remedy.
This checks for firewall rules or other connection blockers. ^3^
For macOS, iOS, Android, or another platform, use the private-browser and alternate-device tests above instead.
5. Report the persistent failure
If both new and previous chats still fail while no incident is listed:
- In Copilot, select … in the upper-right corner.
- Select Send feedback.
- Select Report a problem.
- Include:
- When the failure started
- Device and operating system
- Whether both new and previous chats fail
- Whether private browsing or another device works
- A screenshot of the loading error
This provides Microsoft with the account-side details needed to investigate the issue. ^2^
References
- Microsoft service health status
- Troubleshoot your content in the updated Copilot app
- Copilot troubleshooters | Microsoft Support