Copilot Links

Question

Jeff Turner 0

I am encountering a problem in which Copilot does not respond to questions or anything I try to click/open.

0 comments

1 answer

Answer 1

When Copilot doesn’t respond to clicks or questions, use these targeted checks based on common causes in Microsoft environments:

Check for known “problematic prompt” responses
If Copilot shows messages like:

“Sorry, something went wrong. Please try again.” → An unexpected error occurred. Rephrase the question and try again.
“Sorry, Copilot is at capacity and temporarily unavailable — please try again in a little while.” → Backend capacity issue; wait and retry.
“Sorry, your message contains potentially harmful content…” → Remove any potentially harmful wording and retry.
“Sorry, I couldn’t understand your question…” or “I was not able to generate a valid answer…” → The question could not be translated into a valid FetchXML query or the query failed. Rephrase the question and try again, focusing only on the data visible in the current page/view.
“Sorry, your search includes too many results…” → Narrow the query (for example, limit to yesterday’s or last month’s data) so it stays within FetchXML aggregation limits.

These behaviors are expected when Copilot cannot interpret the prompt or execute the underlying query.

If Copilot in Dynamics 365 Sales doesn’t respond at all
If the Copilot pane opens but never responds or shows a message that it can’t connect:

Ensure the Copilot agent in Microsoft Copilot Studio is successfully published. If initial publishing might have failed, republish the agent once.
Check Power Platform data loss prevention (DLP) policies:
1. Go to Power Platform admin center → Data policies → Data loss prevention.
2. Edit or create a policy and in Prebuilt connectors, locate:
  - Microsoft Dataverse
  - Direct Line channels in Copilot Studio
3. Unblock these connectors and group them together in the same policy group (business or non-business).
4. Save and close the policy.

Blocked connectors or an unpublished agent will prevent Copilot from responding.

If Copilot is missing, disabled, or partially working in Microsoft 365 Apps
If the Copilot button is missing, grayed out, or errors like “Something went wrong. Let’s try again.” appear:

Follow the steps in How to find and enable missing Copilot button in Microsoft 365 apps (linked in the references) to verify the button is enabled.
If the issue persists, an admin should verify:
- A valid Microsoft 365 Copilot–supported license is assigned.
- Copilot is not blocked by organizational policies.
Also consider common causes:
- Newly assigned license not yet fully propagated.
- Conflicting sign-in (for example, signed in with both personal and work/school accounts).
- Network requirements for Copilot not met.
- Shared Computer Activation or device-based licensing in use (Copilot not supported in those scenarios).

Run built-in Copilot troubleshooters (Windows / Microsoft 365)
If Copilot still does not respond:

Open the Get Help app on the device.
For license issues (Copilot icon missing where it should be): search for “Copilot License Troubleshooter” and follow the steps.
For connectivity issues (Copilot opens but cannot connect or respond): search for “Copilot connectivity troubleshooter” and follow the steps.
Review the findings and apply any suggested fixes (for example, firewall or network configuration changes).

Home users: after running the troubleshooters and verifying the basics, contact Support from the Copilot licensing article.
Business users: work with the Microsoft 365 admin to confirm Copilot licensing and policy configuration; the admin can then contact Microsoft support for deeper investigation.

References: