The error message indicates a transient Copilot failure rather than a problem with the prompt itself. Recommended actions depend on where Copilot is being used, but the general pattern is:
- Retry after some time
- Several Copilot experiences return generic errors when backend capacity or service issues occur. For example, Copilot in Power Automate and Security Copilot both surface generic error messages when the underlying service is unavailable or throttled.
- Wait several minutes and try again, especially if many attempts were made in a short period.
- Check for capacity or throttling issues
- In Security Copilot, a
Throttlederror indicates capacity limits or high load. The guidance is to review provisioned capacity and usage, and then retry later. Similar capacity or throttling conditions can cause generic “something went wrong” messages in other Copilot surfaces. - If using a managed/enterprise Copilot, ask the administrator to verify capacity and service health, and to open a support case if the issue persists.
- In Security Copilot, a
- Verify account, license, and connectivity
- For Copilot in Microsoft 365 Apps or Edge, generic “Something went wrong”/blank-pane errors can be caused by:
- License propagation delays or license/account conflicts.
- Network or endpoint connectivity issues to the Copilot service.
- Ensure:
- The account has an appropriate Copilot license and only one primary signed-in identity in the app.
- The device has a working internet connection and required Copilot endpoints are reachable.
- Organizational policies or privacy settings are not blocking Copilot.
- For Copilot in Microsoft 365 Apps or Edge, generic “Something went wrong”/blank-pane errors can be caused by:
- If the problem is persistent and localized to one account or tenant
- Similar issues with Copilot portals and Microsoft 365 Copilot APIs have been resolved only after backend fixes by Microsoft, sometimes after license or configuration changes had already been ruled out.
- If the issue continues over hours and across browsers/devices, escalate through official support channels for the specific Copilot product so the service team can investigate tenant- or account-level faults.
Because the exact Copilot surface (Edge, Microsoft 365 Apps, Dynamics 365, Security Copilot, etc.) is not specified, the next step is to identify which product is in use and then follow that product’s troubleshooting path: verify requirements (license, region, platform), check connectivity to its Copilot endpoint, and, if all checks pass and errors persist, open a support ticket with full details (time of failures, tenant, and screenshots of the error).
References:
- Use Copilot to analyze automation activity and ask product questions
- Security Copilot agent error messages
- Copilot is missing, disabled, or doesn't work correctly
- Troubleshoot Copilot Chat loading problems in the Microsoft Edge sidebar
- Microsoft 365 Copilot Retrieval API errors with Authorization Failed - User does not have valid license - Microsoft Q&A
- Unable to log into m365.cloud.microsoft, something went wrong - Microsoft Q&A