This topic describes the enhancements and modifications included in the July 2026 releases of Data Integrity Suite.
| Service | Feature | Availability status |
|---|---|---|
| Catalog | Create custom semantic with Gio™ AI Assistant You can now use Gio™ AI Assistant in the Catalog to create custom semantic types from natural language descriptions. Gio™ generates a semantic type configuration, checks for similar existing semantic types, and lets you refine the result through chat before creation. For more information, see Create custom semantic type with Gio™ AI Assistant . | Preview |
| Catalog |
Time-bound catalog metrics tracking
You can now monitor catalog program health by tracking contribution activity, identifying active contributors, and understanding where stewardship efforts are focused. Adoption metrics highlight key performance indicators (KPIs) such as contribution volume and contributor participation, with breakdowns by asset type and contributor. These insights enable Data Stewards to assess program health at a glance, identify engagement gaps, and track adoption trends over time. For more information, see View catalog dashboard. |
Preview |
| Configuration |
AKS Cluster access setup
With AKS cluster access setup, you can easily monitor and catalog data assets across your containerized environments. You'll also need a valid Microsoft Azure account, access to your target AKS cluster, and kubectl installed locally. From there, the setup is straightforward, authenticate with Azure, set your target subscription, connect to your cluster, and update your kubeconfig to establish access. You can then verify connectivity using standard kubectl commands. For more information, see EKS, GKE, and AKS cluster access setup. |
Public |
| Configuration | Beta connectors: Early access to new RDBMS datasources Data Integrity Suite now offers new RDBMS datasources in beta, giving you early access to cataloging and lineage capabilities across a broad range of databases and platforms. Beta connectors support data cataloging and data lineage, with ongoing improvements delivered based on your feedback ahead of general availability. For more information, see Beta connectors . | Preview |
| Configuration | Service principal authentication for SQL datasources. You can now authenticate Microsoft SQL Server, Azure SQL, and Azure Synapse datasources with a service principal in addition to username and password authentication. You can enter the tenant ID, client ID, and client secret directly, or retrieve the client secret from a configured key vault. For more information, see the authentication methods for Microsoft SQL server , Azure SQL , and Azure Synapse . | Preview |
| Configuration |
AI Catalog connector Introduced the AI Catalog connector to discover and catalog AI assets from cloud AI providers (Anthropic Claude, OpenAI, GitHub Copilot, Microsoft Copilot Studio) and self-hosted MCP servers and AI agents. The connector enables unified inventory and governance of your organization's AI landscape. For more information, see AI Catalog. |
Preview |
| Governance | Live metrics in the Governance dashboard You can now monitor live governance health metrics from Overview page in Governance , including KPI trend indicators and ownership and coverage views. The dashboard updates as you apply time range, domain, and CDE Only filters so you can quickly assess governance status without building manual reports. For more information, see View governance dashboard . | Preview |
| Quality |
Pipeline Realtime Service – Agent Deployment
You can now deploy Realtime pipeline services directly on an Agent, as well as in the cloud. This flexibility lets you process data in your own environment when needed. The Agent-based option lets you deploy pipeline services to a specific agent and filter the services deployed on that agent. It also keeps data processing within your infrastructure, helping you meet data residency and compliance requirements, while enabling low-latency local processing without routing through the cloud. For more information, see Configure run configuration. To see this feature in action, select here. |
Public |
| Quality |
Databricks Runtime (DBR) 16 and 17 through Volumes
When you are ready to upgrade to Databricks Runtime (DBR) 16 or 17, you'll need to configure a volume and provide its path in your run configuration. You can update your existing run configuration to point to a volume instead of DBFS. Make sure you have the appropriate permissions on the volume before making this change. For more information, see Setup a pipeline engine on Databricks. To see this feature in action, select here. |
Public |