Concept card

Databricks Mosaic AI Agent Framework

As of 2026-07-24T14:00:00Z

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Databricks Mosaic AI Agent Framework?

Mosaic AI Agent Framework is the natural home for an agent only if it needs to read Delta tables, call ML models, or query Vector Search in the same reasoning loop — otherwise a direct LangChain chain is cheaper.

Databricks Mosaic AI Agent Framework is the agent-building runtime native to the Databricks Intelligence Platform: scaffolding for constructing, evaluating, deploying, and governing multi-step AI agents that chain together tool calls, retrieval, language-model reasoning, and direct data queries, all inside a workspace where the platform's own catalog governs lineage, access control, and audit trails on every table, model, and function the agent touches. The framework's value proposition is narrow and specific: it is the right home for an agent whose reasoning loop needs to read Delta Lake tables, call machine learning models already registered in the workspace, or query a vector index, without copying that data or those models anywhere else first.

The three pillars that make it a platform rather than a library

The first pillar is deep integration with the workspace's experiment-tracking layer: every agent is registered with a typed input and output signature, the same way any other model artefact is, which makes it possible to run reproducible evaluation passes, compare versions side by side, and trace a production decision all the way back to the training or configuration data that shaped it. This is not a cosmetic detail — it is what turns "the agent behaved oddly on this request" from an unanswerable question into a traceable one.

Why it matters

Unity Catalog functions govern tool access the same way they govern notebooks and Delta tables, so agent permissions inherit existing data governance automatically.
The Mosaic AI Gateway makes agent endpoints look like plain REST APIs, letting BDC Connect or SAP AI Core call them without knowing the internal topology.
For SAP process-aware reasoning, the correct architecture is Joule Agent as orchestrator calling a Mosaic agent as a specialist tool — not replacing Joule.

Key points

Databricks Mosaic AI Agent Framework is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.
Use current SAP, analyst, study, KG, and news signals as evidence, not decoration.
Separate verified facts from directional trends and modeled assumptions.
Define owner, metric, threshold, support path, and rollback before scaling.
For AI use cases, measure reliability, cost, latency, safety, and human validation.
Leave a reusable operating asset: memo, checklist, control table, and exception log.
A premium answer is short, trade-off explicit, and defensible in a steering committee.

Terms used on this page

Decision owner: The accountable person who accepts the trade-off and funds the next action.
Semantic contract: The shared definition of business terms, metrics, entities, and access rules used by tools and teams.
Control plane: The layer that applies policy, access, lineage, monitoring, and escalation across the operating model.
Evidence grade: A label that separates verified fact, directional signal, modeled assumption, and field observation.
Adoption metric: The measurable behavior proving that the concept changed actual work after go-live.
Agent reliability: The consistency, cost, safety, and policy compliance of an agent across repeated runs.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →