Azure infrastructure monitoring

Put VM runtime and cloud spend beside website health.

Dashy packages read-only Azure subscription discovery, VM inventory, runtime state, resource-group context, and month-to-date cost awareness as dashboard signals.

Connect Azure Compare plans

Azure board runtime + cost

App VMrunninguksouth

Cost£184month to date

API VMrunningStandard B2s

Resource group4active services

Worker VMstoppedexpected running

Consent: Read-only
Scope: Subscriptions
Spend: Budget signal

Connect Use Microsoft OAuth with read-only Azure Management access and no VM action permissions.

Discover Cache subscriptions, resource groups, VM metadata, runtime state, and available cost snapshots.

Package Create Azure VM runtime and Azure cost summary checks from the cached integration data.

Review Show cloud runtime, stale sync state, month-to-date cost, and website health on the same board.

Cloud context

Use Azure checks where service health depends on cloud runtime or spend.

VM runtime: Power state, expected running state, region, VM size, OS, and stale runtime warnings.
Cost summary: Month-to-date subscription cost, currency, data-through date, retrieval time, and permission warnings.
Resource context: Subscription and resource-group inventory so agencies and teams can group signals cleanly.
Read-only boundary: Start, stop, deallocate, resize, and other privileged VM actions stay outside the launch scope.

Permission boundary

Connect Azure for evidence, not infrastructure control.

Azure monitoring should help owners see runtime and spend context without giving Dashy permission to operate cloud resources.

Owner consent: Azure checks start only after the account owner connects Microsoft with read-only Azure Management access.
Cached evidence: Dashy stores subscription, resource group, VM metadata, power state, cost snapshot, sync time, and permission warnings for dashboard history.
No control plane: VM start, stop, resize, delete, network, key, role assignment, and deployment actions stay outside the launch permission set.
Public output: Shared boards should show aggregate runtime, stale-sync, and budget-awareness signals while subscription identifiers and raw cloud inventory stay private.

SaaS teams

See website and VM state together

Keep public uptime, SSL, DNS, API checks, and Azure runtime state on one operational board.

Founders

Notice cost movement earlier

Use month-to-date cost snapshots as budget-awareness signals beside customer-facing service health.

Agencies

Group client cloud context

Map subscriptions and resource groups to client boards without exposing workspace controls publicly.

Azure starts as a read-only infrastructure signal.

Connect Microsoft only after the account owner is ready. Dashy keeps privileged VM control actions separate from the first launch.

Open Azure integration Review agency boards