Copilot Studio agent not display hyperlinks with initial query

Question

Copilot Studio agent not display hyperlinks with initial query

Katie Forsyth 40

RESOLUTION: Switched from GPT AI model to Claude Sonnet to resolve the issue.

My studio agent doesn't display hyperlinks to documents when I ask an initial query but when I ask the same question repeated, hyperlinks show up.
How do I fix this so that hyperlinks display right away with when the initial query is made.
Follow up clarification: Initial response does not provide any links at all when responding to initial query but asking the same question in the same window without refreshing the page or closing and reopening the agent, links show up in the responses.
here's an example from initial response
User's image

example after asking the same question a second time where hyperlinks show up
User's image

Ashlesha Pawar (Tata Consultancy Services Limited) 395 Reputation points Microsoft External Staff

2026-07-01T06:34:36.9833333+00:00
Hi Katie Forsyth, thanks for the clear repro details.

What you’re seeing is usually a retrieval/citation behavior issue, not a hyperlink rendering bug by itself. On the first turn, the agent may return an answer before strong source matches are ranked; on the repeated query (same session), context is improved and citations/links are then included.

Recommended fixes:

In your instruction/prompt, explicitly require sources on first response (example: “Always include source links when answering from knowledge.”).

Verify citations/knowledge-link behavior is enabled in your agent response settings.

Improve retrieval quality for the first turn:

Use clearer document titles and section headers.

Add key synonyms/keywords users ask with.

Remove duplicate/near-duplicate content.

Add a topic/tool path for high-value queries so first-turn routing is deterministic.

Re-publish after changes and retest in a fresh session (new chat window) to avoid warm-context effects.

If this still reproduces consistently, collect conversation ID, environment, and timestamp and open a Microsoft support ticket as a potential product issue.

1 answer

Your answer

Ashlesha Pawar (Tata Consultancy Services Limited) 395 Reputation points Microsoft External Staff

2026-07-01T06:34:36.9833333+00:00

Hi Katie Forsyth, thanks for the clear repro details.

What you’re seeing is usually a retrieval/citation behavior issue, not a hyperlink rendering bug by itself. On the first turn, the agent may return an answer before strong source matches are ranked; on the repeated query (same session), context is improved and citations/links are then included.

Recommended fixes:

In your instruction/prompt, explicitly require sources on first response (example: “Always include source links when answering from knowledge.”).

Verify citations/knowledge-link behavior is enabled in your agent response settings.

Improve retrieval quality for the first turn:

Use clearer document titles and section headers.

Add key synonyms/keywords users ask with.

Remove duplicate/near-duplicate content.

Add a topic/tool path for high-value queries so first-turn routing is deterministic.

Re-publish after changes and retest in a fresh session (new chat window) to avoid warm-context effects.

If this still reproduces consistently, collect conversation ID, environment, and timestamp and open a Microsoft support ticket as a potential product issue.

Answer 1

URLs can be suppressed or altered in Copilot responses depending on how the agent and channel render the output.

From similar behavior with declarative agents and API plugins in Microsoft 365 Copilot, the main mitigation is to ensure that links are formatted explicitly as hyperlinks in the agent’s response content, rather than relying on implicit URL detection.

To improve initial responses so hyperlinks appear consistently:

Format links explicitly as clickable hyperlinks
Ensure the agent (or plugin) returns URLs using a clear hyperlink format, such as Markdown-style links (for example, [Document title](https://contoso.com/doc)), instead of plain text URLs. This reduces the chance that the channel’s rendering or post-processing will hide or strip the URL in the first turn.
Verify the agent is correctly published and used in the intended channel
If the agent is being invoked via Microsoft 365 Copilot (for example, with @mention), confirm that the latest version of the agent is published and that the same configuration is used in both the “initial query” scenario and the “follow‑up query” scenario. Inconsistent publishing or channel assignment can lead to different formatting behavior between turns.
Use developer diagnostics to confirm URLs are present in the raw response
Enable the available developer or diagnostic view for the agent/channel and check whether the URLs are present in the raw agent output for the initial query. If the URLs are present in the raw output but missing in the rendered chat, the issue is with the channel’s rendering/formatting, and explicit hyperlink formatting (step 1) is the primary fix.

If, after ensuring explicit hyperlink formatting and correct publishing, URLs still appear only on repeated queries, review any custom logic or post-processing that might alter or filter the first response differently from subsequent turns.

References:

URLs sometimes disappear in Copilot responses when using a declarative agent with API plugin - Microsoft Q&A