Last updated: 2026-07-15

Browse Azure

Pick Azure-hosted resources straight from your signed-in Azure account instead of hand-typing cluster URLs or server hostnames. Browse Azure… opens a subscription → resource kind → resource tree with live search, and fills the connection form for whatever you pick.

What it does

Finding the right endpoint for an Azure resource usually means a trip to the Azure Portal: copy the ADX cluster URI, work out the ade.applicationinsights.io proxy URL for an App Insights component, or dig the full server name out of a PostgreSQL flexible server's overview blade. Browse Azure removes that trip — Jam SQL Studio enumerates the subscriptions your Azure identity can see and lists the connectable resources in each, with live search across the tree.

Filling in a resource never auto-saves or auto-connects. Use resource populates the server, port, database, authentication, and SSL fields that resource implies; you still review, test, and save the connection yourself.

From Add Connection

On the Azure Data Explorer and SQL Server connection forms, a labeled Browse Azure button sits next to the server field. On the PostgreSQL form the same action is a subtle icon-only button with a “Browse Azure…” tooltip (other engines don’t show it). The picker is filtered to that form’s engine, so an ADX form only offers clusters, App Insights components, and Log Analytics workspaces.

From Import Connections

The Import… menu also lists an Azure (signed-in account) source alongside Azure Data Studio, DBeaver, and the other import sources. Choosing it opens the same picker in multi-select mode, unfiltered by engine, with cascading checkboxes at the subscription and resource-kind level — tick a whole subscription to take everything in it. Resources you already saved show as muted and pre-unchecked, and confirming sends your picks through the normal import review dialog.

Azure identity

A chip at the top of the picker shows which identity discovery is using, switchable between:

• Azure CLI — reuses whatever account you’re logged into via az login; account changes happen in a terminal and are picked up on the picker’s Refresh.
• Microsoft Entra ID — an interactive browser sign-in, with Sign in with a different account… and Sign out available from the identity menu.

Jam SQL Studio detects the Azure CLI first and falls back to Entra sign-in when it isn’t available; whichever you pick explicitly is remembered as the default next time. Enumeration only covers subscriptions visible to your active identity’s home tenant — cross-tenant guest accounts are a known limitation, called out in the picker’s empty state rather than silently omitted.

Supported resource kinds

Security

Browse Azure never reads or writes a database password — PostgreSQL and SQL Server Authentication logins are always entered by you, the same as a hand-typed connection. Azure access itself uses your existing identity (Azure CLI session or Entra sign-in); Jam SQL Studio does not store Azure secrets of its own.

Frequently asked questions