Service Bus namespace nothing is sending to
A Service Bus namespace with no messages in or out over the window and nothing left sitting in its queues.
Why it happens
A Premium Service Bus namespace bills about $677 a month for each messaging unit, and at least one unit is required, whether or not a single message crosses it; a Standard namespace bills a $10 monthly base charge. A namespace cannot be stopped, so the only way to stop the charge is to delete it, and that takes every queue, topic and subscription with it. The rule reports a namespace only when no message arrived and none left across the whole window, and when its queues held nothing at any point during it: a namespace with no traffic can still be holding undelivered messages, and deleting it would destroy them. Basic is skipped because it bills per operation and an idle one costs nothing.
What the agent does about it
A Service Bus namespace with no messages in or out over the window and nothing left sitting in its queues.
It will not fix this one
It reports this and takes no action. A check only earns the right to change something once the action behind it can re-read live state before it fires and knows the way back.
Related checks
Event Hubs namespace nothing is publishing to
An Event Hubs namespace with no events in or out over the window, holding no retained data and no capture backlog.
Idle virtual machine
A running VM whose CPU and network have been near zero for the whole window.
Oversized virtual machine
A running VM whose sustained peak fits comfortably inside the next size down.