Cosmos DB account nothing queries
A provisioned-throughput Cosmos DB account that consumed no request units at all over the window, billing its provisioned RU/s in full.
Why it happens
A provisioned-throughput Cosmos DB account bills hourly on the RU/s it has provisioned rather than on what it uses, so an account nobody queries is charged in full: roughly $0.008 per 100 RU/s per hour, with a practical floor of 400 RU/s per container, which is about $23 a month for the smallest container before storage, and storage bills separately on top. Sustained zero request-unit consumption means no container in any region served anything while the account charged as though it did. Serverless accounts are excluded because they bill per request consumed, so an idle one has no throughput to reclaim. The rule fires only on zero and never on low consumption, because the metric is also published as an average and an average cannot rule out a burst, and a bursty database genuinely needs its throughput.
What the agent does about it
A provisioned-throughput Cosmos DB account that consumed no request units at all over the window, billing its provisioned RU/s in full.
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
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.
Unattached managed disk
A managed disk attached to nothing, billing its full provisioned size every month.