Database Browser 5.3.4.0 is now available. This release adds support for SQL Server Azure and Microsoft Fabric connections, including Windows, SQL Server, and Microsoft Entra authentication options. The connection dialogue has gained a few more keys to the database cupboard. Sensible keys, not the sort you find in a drawer labelled "misc".
What is new in Database Browser 5.3.4.0
- Added: Support for SQL Server Azure and Fabric connections
- Added: Windows Authentication
- Added: SQL Server Authentication
- Added: Microsoft Entra Service Principal
- Added: Microsoft Entra Managed Identity
- Added: Microsoft Entra Default
- Added: Microsoft Entra Password
Azure and Fabric SQL connections are now easier to inspect
Database Browser is built for direct database inspection: connect, browse tables, run SQL, edit records where appropriate, export results, and move on. Version 5.3.4.0 extends that workflow to SQL Server Azure and Fabric connection scenarios.
This is useful when you need a quick look at cloud-hosted SQL data without building an ETL project first. Use it for checking table structures, reviewing records, testing SQL, or confirming that the connection details work before a larger process depends on them.
Microsoft Entra authentication support covers modern SQL setups
The release adds several Microsoft Entra authentication choices, including Service Principal, Managed Identity, Default, and Password. That gives teams more practical options when connecting to environments where simple username and password access is not the preferred method.
To work with Azure or Fabric SQL connections, install the latest Microsoft OLE DB Driver for SQL Server. The download links are listed in our OLE DB drivers download links knowledgebase page.
Although this sounds simple, it was a lot of work under the bonnet. There is a small chance we missed something, so please tell us if you find any issues. SQL connection code has a habit of hiding surprises in the cupboard behind the nice clean dialogue box.
If your database access is managed through Azure identities, this update is worth installing. If you only use local SQLite files or a small on-premises database, there is no panic. Database updates should not behave like a fire alarm in a library.
Upgrade when you work with Azure or Fabric SQL data
Upgrade to Database Browser 5.3.4.0 if you need to inspect SQL Server Azure or Fabric data directly, or if your connection setup uses Microsoft Entra authentication. If your current Database Browser setup is working and you do not use these connection types, you can update when convenient.
See the Database Browser product page, review the Database Browser version history, or use the donation page if the free tool saves you time.