microsoft/azure-ai-search-foundry-iq-live-knowledge-sources

microsoft/azure-ai-search-foundry-iq-live-knowledge-sources

Description: Reusable accelerator for Foundry IQ live grounding with Fabric Ontology and MCP Server Knowledge Sources.

Language: Python

License: MIT

Stars: 16

Forks: 5

Open issues: 2

Created: 2026-06-10T08:49:32Z

Pushed: 2026-09-14T09:20:33Z

Default branch: main

Fork: no

Archived: no

README:

Foundry IQ Live Knowledge Sources Accelerator

> Go from clone to a proved stable Search Index Knowledge Source, compose it with a preview MCP Server source, then extend the same guarded lifecycle to governed Fabric Ontology sources.



Execution manual | [First live in Codespaces](docs/15-codespaces-first-live.md) | Offline trace demo | KO/EN walkthrough

This accelerator is for six successive jobs:

| You are here | Finish this | Path | | --- | --- | --- | | Evaluator | Inspect the answer, activity, references, and source identities without cloud access. | ./liveks try | | Search implementer | Wrap and prove an existing agentic-ready Search index without transferring ownership. | search-index | | Knowledge composer | Add Microsoft Learn MCP to an existing Search index without provisioning a new service. | mcp-search-index | | Three-source composer | Add a native existing Fabric ontology to the reused Search + MCP path. | three-source | | Azure implementer | Deploy and prove one preview MCP Server KS without Fabric. | mcp-only | | Fabric implementer | Add an existing or greenfield ontology and prove both source paths. | byo-fabric or full |

The repository is a reusable accelerator, not a production reference architecture. Coding-agent behavior is specified separately in [AGENTS.md](AGENTS.md); human onboarding stays focused on the outcomes above.

30-Second Replay

From a fresh clone, inspect the complete answer-and-evidence contract before installing packages or configuring Azure:

git clone --depth 1 https://github.com/microsoft/azure-ai-search-foundry-iq-live-knowledge-sources.git
cd azure-ai-search-foundry-iq-live-knowledge-sources
./liveks try --evidence-out .deployment/first-run-evidence.json

Python 3.11 or newer is the only requirement. Require Contract: PASS (4/4 assertions): the known synthetic fact, both required activity types, both required reference types, and both Knowledge Source names must be present.

> REPLAY - NO AZURE CALL: this command proves the checked-in response contract only. It does not prove that Azure AI Search, MCP Server KS, or Fabric ran live.

The ignored capsule records repository revision, runtime, fixture digest, source counts, and assertion status without query, answer, raw response, or credentials. Pull-request validation runs the same command and retains the capsule as a short-lived workflow artifact.

Lowest-Risk Live: Existing Search Index

When an agentic-ready Azure AI Search index already exists, use the generally available 2026-04-01 lane before preview-only sources:

./liveks bootstrap
./liveks init --profile search-index --env liveks-index
# Fill endpoint, index_name, semantic_configuration_name, and optional field lists.
./liveks doctor --env liveks-index
./liveks plan --env liveks-index
./liveks up \
--env liveks-index \
--query "" \
--expect-term ""

doctor reads the index definition with a transient Microsoft Entra token. plan checks stable payloads and name collisions without writes. up creates only a Search Index KS and minimal extractive Knowledge Base, then applies the supplied content assertion; the Search service and index remain BYO assets.

Prove a real call with a known non-sensitive term, then clean up:

./liveks verify \
--env liveks-index \
--query "" \
--expect-term ""
./liveks down --env liveks-index

Require search-index-retrieve=pass, grounding-content=pass, and search-index-preserved=pass. Read the [stable Search Index execution contract](docs/23-search-index-ks.md).

Compose Existing Search With MCP

When the same Search service can use an existing Azure OpenAI deployment, add a preview MCP Server KS and one combined KB without provisioning infrastructure:

./liveks init --profile mcp-search-index --env liveks-combined
# Fill the existing Search endpoint/index/semantic configuration and Azure OpenAI endpoint/deployment/model.
./liveks doctor --env liveks-combined
./liveks plan --env liveks-combined
./liveks up \
--env liveks-combined \
--query "" \
--expect-term "" \
--combined-query ""

This profile creates only a GA 2026-04-01 Search Index KS, a 2026-05-01-preview MCP Server KS, and a preview combined KB. plan names every object, API version, ownership boundary, cost, and cleanup action using GET requests only.

verify first forces the existing index, then forces MCP, then offers both sources to the combined planner. Require search-index-retrieve=pass, mcp-retrieve=pass, and combined-retrieve=pass. The combined check reports only source evidence found in activity, references, or sourceData; answer text never proves routing.

Cleanup deletes the lock-owned combined KB, MCP KS, and Search Index KS in dependency order, then requires search-index-preserved=pass. It never deletes the Search service, index, Azure OpenAI deployment, resource group, or Fabric. Read the [MCP + Search Index execution contract](docs/24-mcp-search-index-kb.md).

Compose Search, MCP, And Native Fabric

When the same tenant also has an existing Fabric workspace and ontology, extend the data-plane-only path without provisioning infrastructure:

./liveks init --profile three-source --env liveks-three
# Fill existing Search, Azure OpenAI, Fabric workspace, and ontology values.
./liveks doctor --env liveks-three
./liveks plan --env liveks-three...