microsoft_docs_search returns a stale chunk for a page that microsoft_docs_fetch serves current

Open
#228 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
backend, search

Research direction

The payload names no source files. Start by finding where microsoft_docs_search results are indexed and how contentUrl is attached to chunks, then compare that with the path microsoft_docs_fetch uses to read the same URL. Reproduce by running both tools on the Entra Agent ID page and checking whether search returns a chunk older than the live page. Done means search chunks for changed or redirected URLs are refreshed or removed, which needs a maintainer decision on re-index versus drop.

Written by the indexing model from the issue text.

Description

microsoft_docs_search returns a chunk attributed to a Learn URL whose live content has changed. microsoft_docs_fetch on the same URL returns the current page.

Page

https://learn.microsoft.com/entra/agent-id/identity-professional/microsoft-entra-agent-identities-for-ai-agents

Steps to reproduce

  1. Call microsoft_docs_search with the query Microsoft Entra Agent ID is currently in PREVIEW.
  2. Look at the first result. Its contentUrl is the page above, and its title is "What is Microsoft Entra Agent ID?". The chunk has an "Important" notice saying Microsoft Entra Agent ID "is currently in PREVIEW".
  3. Call microsoft_docs_fetch on the same URL.

Expected

The search chunk matches what fetch returns for that URL.

Actual

  • Fetch returns the current "What is Microsoft Entra Agent ID?" overview. It has no preview notice and says Agent ID "is available for all Microsoft Entra customers".
  • With another query, the search also returned a "How to get started" chunk under the same URL. That chunk says Agent ID is available through the Frontier program and needs a Microsoft 365 Copilot license.
  • The same search response contradicts the stale chunk. It includes the Entra "What's new" April 2026 entry announcing general availability, and "What's new in Microsoft Entra Agent ID", which says the product "is now generally available".

Why it matters

Clients often use search results without fetching the full page. A stale chunk that still says "PREVIEW" and gives retired licensing guidance leads readers to the wrong product status and the wrong licensing.

Suggestion

  • Re-index, or drop, search chunks for URLs whose content has changed or that now redirect. In this case, refresh the chunks under the identity-professional/microsoft-entra-agent-identities-for-ai-agents URL.
  • More generally, a last-indexed date on each search result would let callers spot stale entries.

I reproduced this on October 31, 2026, with two different queries.

Dominant language
TypeScript
Stars
2k
Forks
288
Avg merge
4m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MicrosoftDocs/mcp

All issues in MicrosoftDocs/mcp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.