PostgreSQL flexible server nothing connects to

This saving is not permanent. After 7 days, Azure automatically starts the server again, so the resource starts billing again unless something stops it a second time.

Why it happens

A flexible server bills a fixed hourly compute rate while it runs, independently of query traffic, so a General Purpose 4 vCore server is about $260 a month before storage. Sustained zero on both active connections and newly succeeded connections means nothing is using the database while it charges in full. Both signals are required because either alone can be innocent, since a pooling application holds connections open against a database it never queries and a health probe reconnects without holding one. Stopping the compute is reversible and keeps the data, but Azure automatically starts a stopped server again after 7 days, so the saving reported here is what one stop delivers rather than a full month, and sustaining it means repeating the stop. Storage and backup keep billing while stopped and are excluded from the figure.

What the agent does about it

An Azure Database for PostgreSQL flexible server with no active connections and no new connections over the window.