Inside the Azure connector: what CloudMonitor actually checks

A scanner-by-scanner tour of what we read from a connected Azure subscription, what each check flags, and what we never touch.

When you connect an Azure subscription to CloudMonitor, our scanner does one job: read the Azure Resource Manager (ARM) API as a read-only observer and turn what it sees into findings. This post lists the scanners that run against an Azure subscription today, and what each one flags.

1. Compute

2. Storage & data

3. Networking

Network security groups are the high-signal target: an inbound Allow rule open to the whole internet on a sensitive port — SSH, RDP, SQL Server, MySQL, PostgreSQL, MongoDB, Redis, Elasticsearch and similar — or on every port. We also read public IP addresses (flagging ones attached to nothing), load balancers (rules with no health probe) and Application Gateways (WAF disabled, HTTP listeners with no HTTPS redirect, expired or expiring listener certificates). In public Azure DNS zones, a CNAME that points at a resource which no longer exists is flagged as a possible subdomain takeover.

4. Changes, Microsoft notices and governance

5. Scanners that need an extra role

Three scanners run against every Azure connection but only find something once you grant more than Reader. Without the extra grant they skip quietly and the rest of the scan carries on:

6. Cost and waste

Every night a spend check reads each subscription's daily usage, flags a day whose spend jumps well above the median of the week before it (or a new service that suddenly costs money), and reads your Azure budgets to flag spend reaching 75, 90 and 100% of a budget, or Azure's own forecast heading past it. That needs only Reader, and we never create a budget for you. A waste scan prices what costs money while doing nothing — unattached disks, old snapshots, public IPs and network interfaces attached to nothing, empty paid App Service plans, idle load balancers and NAT gateways — at Azure list price, and totals it per subscription. The Cost Explorer pages read the Azure Cost Management API (it needs Cost Management Reader) and cache spend by service; an account admin refreshes them from the page.

What the Azure connector does NOT do

How often it runs

It depends what the scan is looking for. Findings Azure has already raised — Defender for Cloud recommendations, risky Activity Log changes, Service Health incidents — are read every 5 minutes on a paid plan (every 15 during a trial). Exposure and state — storage and database public access, NSG rules open to the internet, public IPs, unauthenticated container ingress, App Service and AKS state, registry admin users — is re-checked every hour, because any of it can change the moment someone clicks something. Posture and expiry — Key Vault secrets and certificates, backups, governance, quotas, DNS, end-of-life dates, MuleSoft runtime versions — runs once a night, in a single pass, because its warning ladder steps in days. Utilization, cost and waste ride that same nightly pass. Endpoint and certificate monitoring runs every 5 minutes on a paid plan (every 15 during a trial). The cadence is the same for every customer; there is no setting or tier that changes it. An account administrator can ask for a fresh scan of a connection, at most once every 15 minutes per account; it runs with the next hourly scan.

The read-only roles we ask for are on the Connectors page.

← Back to all posts