Topic starter
22/08/2026 12:01 pm
TL;DR: Databricks Data + AI Summit 2026 signals that enterprise AI is shifting from pilots to production, with OpenSharing, Federated Catalog, and Lakebase aimed at cross-cloud asset sharing, governed data federation, and transactional agent workloads, according to Trust3. The governance gap is now the harder problem: organisations need visibility into agent scope, access, and runtime behaviour, not just more infrastructure.
Editorial analysis by NHI Mgmt Group, based on content published by Trust3: “Unpacking Databricks Summit 2026: The Three Infrastructure Shifts Moving AI from Pilot to Production”.
Key questions
Q: What breaks when agentic AI is governed only as a data platform problem?
A: The control model breaks because data governance does not answer who or what is acting on the data at runtime.
Q: Why do AI agents need distinct machine identities in production?
A: Distinct machine identities let teams bind every agent action to a known runtime actor with a defined scope.
Q: How do security teams know if AI governance is working?
A: Look for evidence that access decisions are reviewable, permissions are revocable, and exceptions are not becoming permanent.
Practitioner guidance
- Define agent identity before production rollout Assign each agent a distinct machine identity, scope its permissions to the minimum required actions, and document the systems it may invoke.
- Classify shared AI assets for governance Inventory models, agent skills, prompts, and unstructured inputs as governed assets with owners, retention rules, and permitted sharing boundaries.
- Verify policy consistency across federated catalogs Test whether access decisions, lineage, and audit records remain stable when the same data is queried through multiple catalogs or clouds.
Bottom line: Databricks Summit 2026 shows that agentic AI is now a production architecture issue, but governance remains the limiting factor.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
22/08/2026 12:02 pm
Agentic AI governance debt is becoming the real integration tax: platforms can now move models, data, and agent skills across clouds, but most organisations still govern those objects as if they were static analytics artifacts. That mismatch creates blind spots around who can invoke an agent, what data it can touch, and how its actions are attributed. The control problem shifts from storage location to runtime authority, which means identity governance must move earlier in the design cycle.
A question worth separating out:
Q: Should organisations separate analytics access from agent write permissions?
A: Yes. Read-heavy analytics and write-capable agent workflows create different risk profiles, so they should not share the same standing permissions. When the same role can both analyse and act, an error or compromise in the agent layer can turn into an operational change.
👉 Read our full editorial: Databricks Summit 2026 shows agentic AI needs governance