Entra ID auth & Azure discovery
in progressSign in with Entra (Azure SQL and Azure Redis), find Azure SQL targets, and get a hand with firewall access when it is needed.
Azure SQL should not require a scavenger hunt for credentials and firewall rules. Sign in with Entra ID, discover the servers and databases you can reach, and get help adding a firewall rule when Azure turns you away at the door.
Signing in
- Entra (browser) - the normal interactive flow, including whatever conditional access and MFA your tenant requires.
- Entra (device code) - for a machine where opening a browser is awkward: SQLly shows a code, you complete sign-in elsewhere.
Tokens are acquired and refreshed for you, and more than one Entra account can be registered at a time, which is the normal state of affairs if you work across a customer tenant and your own.
Azure Cache for Redis and Azure Managed Redis
Redis connections can sign in with Entra too. Pick Redis as the engine,
choose Microsoft Entra, enter the cache host (it ends in
.redis.cache.windows.net or .redis.azure.net), set TLS to
Require or stricter, and pick a signed-in account. SQLly asks Entra for a token
for the Redis audience (https://redis.azure.com/.default) from the same
sign-in your Azure SQL connections use, and authenticates as the identity's object id, or as the name in Redis user (optional) when the cache's access policy
names the identity by one. The editor warns when the host is not an Azure Redis endpoint.
Azure closes a Redis connection whose token has expired, so SQLly re-authenticates an
open connection with a fresh token (AUTH on the live connection) before the
old one runs out. This covers Sentinel connections too (the master, the replica that
serves reads, and a new master after a failover, which signs in with the newest token)
and Redis Cluster connections, whose routed connection is rebuilt with the new token so
every node - including one reconnected later - signs in with it. Give the identity a data access policy on the cache first - Entra
sign-in only proves who you are; the cache decides what you may run.
Verified against the token flow with a scripted identity provider and a local Redis standing in for the cache; not yet run against a live Azure Managed Redis instance. The Profiler and Pub/Sub tools hold a connection that cannot re-authenticate mid-capture, so on Entra they end when the token they started with expires - start them again.
Discovery, cached so it is there on launch
SQLly asks Azure Resource Manager which SQL servers and databases your accounts can see, across subscriptions, and shows them in the explorer. Because that is an authenticated network round-trip, a cold launch would otherwise leave the tree empty for the first few seconds - so every successful discovery is saved as a local snapshot and reloaded instantly on the next launch.
Azure is re-contacted only when you ask: refreshing an Azure node, adding or removing an Entra account, or signing in again. A stale or corrupt cache never blocks startup; it simply yields nothing until a refresh.
Firewall assist
Azure SQL rejects an unknown client IP with error 40615, and the message contains the address it blocked. SQLly recognises that specific failure, extracts the IP, matches the server against your discovered ARM servers, and offers to add the firewall rule, rather than leaving you to translate a login error into a portal visit.
In progress. Sign-in, discovery with its cache, and firewall-block detection work today; some of the rule-creation and multi-tenant edges are still being smoothed.