v3.4.1

Fabric Data Agent (Microsoft Fabric) knowledge source support.

What ships

• The Foundry IQ retrieve client now includes a fabricDataAgent knowledge source alongside existing azureBlob / searchIndex / workIQ / fabricOntology sources.
• Gated by FABRIC_DATA_AGENT_ENABLED + FABRIC_DATA_AGENT_KNOWLEDGE_SOURCE_NAME. When both are set and an on-behalf-of user token is available, a kind="fabricDataAgent" entry is appended to knowledgeSourceParams.
• ACL is enforced natively by Fabric via the forwarded per-user token (same x-ms-query-source-authorization header used by Work IQ and Fabric ontology), so no filterAddOn is emitted.
• Managed-identity fallback is never used for remote knowledge source kinds: when the OBO token is missing the Fabric Data Agent source is skipped (with a warning) and local sources still serve the request.

Why this release

The FDA feature landed on develop in commit a2c7e58 (PR #265) but was cut a few minutes before the v3.4.0 release commit e1122248 (PR #266), so it never actually shipped in v3.4.0. The paired platform release GPT-RAG v3.4.2 pinned the manifest at orchestrator v3.4.0 and advertised the feature, but the deployed container had no FDA code path. v3.4.1 publishes the FDA code so GPT-RAG v3.4.3 can pin to a real orchestrator tag that carries the feature.

Validation caveat

Live end-to-end validation against a real Fabric Data Agent was deferred at ship time because no test agent was available. The code path is covered by unit tests in tests/test_foundry_iq_fabric_data_agent.py and the platform-side registration path was validated against Foundry IQ 2026-05-01-preview with stub GUIDs (PUT knowledgesources/fabric-data-agent-ks-stub returned 201).

Files

• VERSION: 3.4.0 -> 3.4.1
• CHANGELOG.md: FDA entry relabeled from [v3.4.0] to [v3.4.1]

No source or test changes vs develop HEAD as of the v3.4.0 release cut.