Repository navigation
v7.0.0
Changed
- Deploy Agent App MCP Server independently and select its toolsets with
MCP_TOOLSETS, default[]. Enable its NL2SQL tools explicitly with
["nl2sql"]. - Compose shared authentication and transport separately from selected
toolsets' configuration, resources and provider lifetimes. - Move SQL tools from the native orchestrator to the MCP Server and retire
the former direct SQL/Fabric/DAX configuration. - Keep reference and custom application composition above the reusable
Bicep/Terraform foundation, with application-owned resources and permissions. - Bind the coordinated runtime sources while intentionally retaining
ingestionv3.1.3.
Component versions
| Component | Version |
|---|---|
| agent-app-mcp | v2.0.0 |
| agent-app-ui | v3.5.0 |
| agent-app-orchestrator | v7.0.0 |
| agent-app-ingestion | v3.1.3 |
| infra / AI Landing Zone | v2.7.3 |
Validation
- Focused application-composition and exact-pin contracts passed against the
real bundled application definition. - Platform CI covers Python deployment/hook contracts, Bicep build/lint and
offline contracts, and Terraform checks on Ubuntu and Windows. - Infrastructure provider lock, module pins and provenance are preserved.
- Validation is local and CI-based. Azure deployment, live model calls,
live SQL connectivity, private networking and deployed provider parity
were not exercised.
Migration and rollback
Upgrade the complete pinned component and configuration combination.
Select DEPLOY_AGENT_APP_MCP=true for the reference application's server and
set MCP_TOOLSETS=["nl2sql"] to enable its SQL tools. Deploy the server before
its consumers and retain the approved catalog, identity bindings and read-only
SQL permissions. Toolset changes take effect after restart or redeployment.
Rollback restores the previous complete component/configuration combination
and deployment state while retaining catalog data. Review retained grants
deliberately when disabling a toolset.