Azure SQL Server (Logical Server)
Does ZopNight manage Azure SQL Server (Logical Server)?
An Azure SQL logical server carries no compute charge of its own. The server is the administrative parent holding logins, firewall rules, and auditing settings for SQL databases and elastic pools. ZopNight discovers it via Resource Graph to build parent-child topology, so the spend of every child database rolls up correctly.
Rules that fire on Azure SQL Server (Logical Server)
No active rule family targets Azure SQL Server (Logical Server) today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery and topology only; the logical server carries no direct compute charge. |
An Azure SQL logical server is the administrative parent for SQL databases and elastic pools, holding logins, firewall rules, and auditing settings. The server itself is free, but it anchors the databases and pools where the spend lives.
A free resource that anchors paid ones
The logical server has no meter. Azure charges nothing for the server object itself: no compute, no per-hour rate, no minimum. Every dollar associated with it actually belongs to its children: the SQL databases, elastic pools, and backup storage created underneath it. That makes the logical server the wrong place to look for savings directly, and exactly the right place to organise the search, because a server groups related databases under one set of credentials, one region, and usually one team.
Topology is the point of discovering it
ZopNight discovers logical servers via Azure Resource Graph and uses them to build the parent-child topology for their databases and elastic pools, so cost attribution and recommendations roll up correctly. A rightsizing finding on a database is far more actionable when it arrives grouped under the server it belongs to, and therefore under the application. ML auto-tagging covers this type, extending predicted environment tags to the whole family at once. Because nothing bills at the server level, there is nothing to schedule: the entry exists for discovery and topology only.
Server-level leaks to look for
The waste patterns here are indirect but real. A forgotten logical server is the usual reason its child databases were forgotten too; orphaned databases almost always hide under servers nobody has opened in months. Servers duplicated per developer or per experiment multiply the surface to audit. And a server whose databases have all been deleted costs nothing but keeps stale firewall rules and logins alive, which is a hygiene problem worth closing out even without a billing motive.
Finding logical servers in the portal
Azure portal → SQL servers lists every logical server in the subscription. Opening one shows its databases and elastic pools (the actual bill-carriers) along with the firewall, auditing, and Microsoft Entra admin settings the server governs.