CloudMonitor started with three problems: credentials that expire, resources nobody switched off, and endpoints that quietly stopped answering. Those are still the core. But the scan now reaches a good deal further, and more of the work happens after a finding is raised. This post is the round-up. Everything in it is available today, and anything still in Beta is marked as such.
Microsoft 365 and Entra ID
Connect your directory and CloudMonitor checks it the same way it checks a subscription. It looks for users with no MFA, stale and guest accounts, privileged role assignments and Conditional Access gaps. It also tracks app-registration client secrets and SAML signing certificates that are about to expire, unused licenses, Intune Apple push, VPP and enrollment tokens, and Microsoft Secure Score with its trend over time. It also reads Microsoft 365 Service Health and Message Center for the services your tenant uses. The directory can be connected on its own. You don't need an Azure subscription to use it.
Domains, DNS and email
A domain that lapses takes everything with it, and nobody's cloud console warns you. CloudMonitor now tracks domain registration expiry on the same 90-to-0-day ladder as secrets and certificates. It checks SPF, DKIM, DMARC and MTA-STS, DNS drift, DNSSEC, CAA records and dangling DNS, and it grades security headers. Certificate Transparency watch flags a certificate issued by a CA you never approved, and lookalike domains registered against yours.
Cost and governance
Beyond idle VMs, the cost scan now covers reservation and Savings Plan expiry, cost anomalies and budget burn, and priced waste. The governance checks cover quota headroom, operating systems past vendor support, missing tags, policy and resource locks, backup coverage, and Defender and Advisor recommendations. None of these will page you at 2 AM, and most of them will cost you money or an outage if nobody looks.
GitHub: the first SaaS connector (Beta)
GitHub is the first SaaS platform you can connect. It went live only after its scanner ran against a real organization and every finding was checked by hand. With a fine-grained token that is read-only throughout, CloudMonitor checks every repository for:
- default-branch protection;
- open Dependabot, code-scanning and secret-scanning alerts;
- deploy keys and token expiry.
A CI/CD board shows workflows that are failing, stuck or flaky on the default branch. It never re-runs a workflow and never reads your code. The SaaS connectors post has the exact token permissions and what is next.
Diagnostics: one cause, not three alerts
When a Key Vault secret expires, the app that depends on it starts failing, and then the endpoint in front of the app goes down. That used to arrive as three separate findings. Diagnostics now joins related signals into one likely cause per problem, using a map of how your resources depend on each other and a deterministic set of rules. Each diagnosis shows its confidence and the chain behind it. On plans with AI Insights, you can also ask for a plain-English explanation of any cause.
Alerts where your team already works
Alerts can go to email, Slack, Microsoft Teams, Discord, PagerDuty or a webhook of your own. They can also open tickets in ConnectWise, Autotask, HaloPSA or NinjaOne. Every destination is included on every plan. For each destination and each type of alert, you choose whether alerts arrive one at a time or in an hourly, daily or weekly digest, and whether you hear when they resolve. Outages arrive at once by default, and paging and tickets always do. You can acknowledge, snooze or assign an alert from the dashboard, and when the problem clears, a PagerDuty incident resolves itself.
Running IT for clients
If you look after other people's environments, each client sits in its own isolated tenant under your MSP account. One cross-client worklist shows what is critical or expiring across all of them. You can send clients a one-time onboarding link, and each client gets a read-only portal of its own. The MSP bundle adds your name and logo to the monthly report emailed to each client, plus the compliance evidence pack. We link your clients to your MSP account when you set up, so just ask.
Open by default
Every plan includes a read-only REST API at /api/v1, so you can pull inventory, findings and alert history into your own dashboards or scripts. Single sign-on with your own identity provider works over OpenID Connect, on every band. Users are unlimited, with admin and read-only roles. An activity log records who did what, and you can export all of your data at any time.
What hasn't changed
CloudMonitor is still read-only. It reads metadata, never secret values, and nothing it watches ever needs write permission. AWS and Google Cloud are still in Beta: their scanners have been verified against emulated APIs, not yet against a live customer account. The other SaaS scanners are written but stay off the list until each one passes the same real-account check GitHub did. If there is one you need, tell us.