Microsoft Fabric Updates Blog

Microsoft JDBC Driver for Microsoft Fabric Data Engineering (Preview)

JDBC (Java Database Connectivity) is a widely adopted standard that enables client applications to connect to and work with data from databases and big data platforms.

The Microsoft JDBC Driver for Microsoft Fabric Data Engineering (Preview) – an enterprise-grade connector that brings powerful, secure, and flexible Spark SQL connectivity to your Java applications and BI tools, all through Microsoft Fabric’s Livy APIs.

Why this Matters

As organizations increasingly rely on Apache Spark for scalable data engineering and analytics, seamless integration with enterprise platforms is critical. The new Microsoft JDBC Driver for Microsoft Fabric Data Engineering empowers developers, data engineers, and administrators to connect, query, and manage Spark workloads in Microsoft Fabric with the reliability and simplicity of the JDBC standard. The following is an example of using this driver in DbVisualizer.

A screenshot of a computer

AI-generated content may be incorrect.

Since this driver has been specifically designed and developed for Fabric Data Engineering, it has deep integration with lakehouse for data access in OneLake, allows using an environment item during execution of your jobs as well as allows different Spark configurations based on your unique needs.

Key Features

  • JDBC 4.2 Compliance: Works out-of-the-box with Java 11, 17, and 21, and supports popular BI tools like Tableau, Power BI (via JDBC connector), DBeaver, DbVisualizer etc.
  • Enterprise Authentication: Multiple Azure Entra ID (formerly Azure Active Directory) flows – including interactive browser, client credentials, certificate-based, and access token authentication – ensure secure access for every scenario.
  • Robust Connection Pooling: Built-in pooling with health monitoring, automatic recovery, and HikariCP integration for high-throughput production workloads.
  • Native Spark SQL Support: Execute Spark SQL statements directly, with comprehensive support for all Spark SQL data types – including complex types (ARRAY, MAP, STRUCT).
  • Performance & Resilience: Asynchronous result set prefetching, circuit breaker pattern, auto-reconnection, and advanced retry logic keep your applications running smoothly.
  • Proxy & Logging: Full support for HTTP/SOCKS proxies and customizable logging for enterprise environments.

The Microsoft JDBC Driver for Microsoft Fabric Data Engineering is designed to accelerate your Spark-powered data engineering projects with enterprise-grade security, reliability, and performance. We invite you to try it out, share your feedback, and unlock new possibilities for analytics and integration in Microsoft Fabric.

To download and learn more about the Microsoft JDBC Driver for Microsoft Fabric Data Engineering, refer to the Microsoft JDBC driver for Microsoft Fabric Data Engineering documentation.

Related blog posts

Microsoft JDBC Driver for Microsoft Fabric Data Engineering (Preview)

January 20, 2026 by Xu Jiang

The exchange of real-time data across different data platforms is becoming increasingly popular. The Cribl source (preview) is now available in Real-Time Intelligence, allowing real-time data to flow into Fabric RTI Eventstream through our collaboration with Cribl, enabling you to take full advantage of Fabric Real-Time Intelligence’s robust analytics tools for their real-time needs. Collaborating to broaden … Continue reading “Expanding Real-Time Intelligence data sources with Cribl source (Preview)”

January 20, 2026 by Ye Xu

Copy job is the go-to solution in Microsoft Fabric Data Factory for simplified data movement, whether you’re moving data across clouds, from on-premises systems, or between services. With native support for multiple delivery styles, including bulk copy, incremental copy, and change data capture (CDC) replication, Copy job offers the flexibility to handle a wide range … Continue reading “Simplifying data movement across multiple clouds with Copy job – Enhancements on incremental copy and change data capture”