Microsoft Copilot help and reporting
Consumer Copilot, Microsoft 365 Copilot and GitHub Copilot are distinct support products.
Live Domain Check
Run a live reachability check for copilot.microsoft.com. Compare the regional responses with the problem you see in Microsoft Copilot.
Find Microsoft Copilot help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Consumer Microsoft Copilot, work Copilot and GitHub Copilot are different products and support routes.
The checker above requests copilot.microsoft.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Microsoft Copilot action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse AI service checks.
Consumer Copilot, Microsoft 365 Copilot and GitHub Copilot are distinct support products.
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
We have not linked a separate status page for this service. Check the official help page for current notices.
Open Microsoft Copilot help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Copilot product, personal/work account, feature, device/browser and error/correlation ID.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Microsoft Copilot.
These are troubleshooting comparisons, not claims that Microsoft Copilot is currently experiencing a particular incident.
Identify the product and account type, then compare a new small request with the failing conversation/action.
Use the correct product support area; a work administrator may need to check tenant access or service health.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Microsoft Copilot seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open copilot.microsoft.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Microsoft Copilot issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Microsoft Copilot support.
Run the copilot.microsoft.com check and compare its original timestamps and responses with your actual error. Consumer Microsoft Copilot, work Copilot and GitHub Copilot are different products and support routes.
Use the official help/reporting resource linked above. Consumer Copilot, Microsoft 365 Copilot and GitHub Copilot are distinct support products.
Identify the product and account type, then compare a new small request with the failing conversation/action. Use the correct product support area; a work administrator may need to check tenant access or service health.
Copilot product, personal/work account, feature, device/browser and error/correlation ID.