Download Dataverse JDBC Driver

Download the Dataverse JDBC driver, copy the JDBC URL into DbSchema, and start designing schemas with ER diagrams — free Community Edition.

About the Dataverse JDBC driver

A JDBC driver is a Java .jar library that lets applications connect to Dataverse. DbSchema uses JDBC to reverse engineer schemas, run SQL, and generate documentation. Driver files are usually published by the database vendor or an open-source project.

JDBC URL format

Host, port, database name, and SSL options are passed in a URL starting with jdbc:. Each Dataverse driver uses its own syntax — see the connection details below.

The Dataverse JDBC driver

Microsoft Dataverse is a cloud-based data platform that underlies Microsoft Power Apps, Power Automate, and Dynamics 365, providing a secure and scalable data storage service for business applications. It exposes a TDS (Tabular Data Stream) endpoint allowing read-only T-SQL queries against Dataverse tables using standard SQL tooling. Dataverse supports complex data models including relationships, business rules, and role-based access control.

The Microsoft Dataverse JDBC URL

• Required File(s): mssql-jdbc-xxx.jar
• Java Driver Class: com.microsoft.sqlserver.jdbc.SQLServerDriver
• JDBC URL: jdbc:sqlserver://{HOST}:5558;database={DB}
• Website: Microsoft Dataverse Developer Documentation

Set Up the Dataverse Connection

Dataverse differs from every other database here in one way: the SQL endpoint is switched off until an administrator turns it on, and it can be withheld from individual users even then. Both are settings an administrator makes, not something the client can work around.

1. Enable the TDS endpoint for the environment. In the Power Platform admin center open Manage → Environments, pick the environment, and under Settings → Product → Features switch on Enable TDS endpoint. Until this is on, the environment does not listen for SQL traffic at all.
2. Give the user the endpoint privilege. Where access is controlled per user, the user's security role needs the Allow user to access TDS endpoint privilege. Without it a correctly formed connection is still refused.
3. Use the organization host and the right port. The host is the environment's organization URL, as in myorgname.crm.dynamics.com. The endpoint answers on 1433 and on 5558; where only 5558 was opened, the port has to be stated explicitly.
4. Authenticate with Microsoft Entra ID. Nothing else is accepted — there are no SQL logins. Pick the interactive Entra entry in the Connection Mode combo, which opens a browser window and handles multifactor authentication.
5. Enter it in DbSchema. Fill in the host, the port and the environment as the database, or set Connection Mode to Edit the JDBC URL Manually to write the whole string yourself. There is no connection string to copy from a portal here — the URL is built from the organization host.

The endpoint is read-only, so DbSchema reverse engineers Dataverse tables, relationships and columns and runs T-SQL queries against them, but schema changes stay in Power Apps.

DbSchema and Microsoft Dataverse

DbSchema connects to Microsoft Dataverse via the TDS endpoint using the SQL Server JDBC driver, enabling visualization of Dataverse table schemas, running read-only T-SQL queries against Dataverse data, and documenting Power Platform data structures for enterprise governance.