Skip to main content
Version: 0.4 · current

Azure

OverviewReviewed October 11, 2026
Applies to:Excubius 0.4Roles: Entity admin, Editor
PlansFree · Core · Pro · EnterpriseDeploymentSelf-hosted

The Azure module watches Azure resources through the platform's own APIs: virtual machine power and CPU, Azure SQL Database load and storage, PostgreSQL flexible servers, VPN tunnels and application gateways, and Recovery Services backup jobs. Its values come from the Azure Monitor source, read with read-only roles.

What it monitors​

AreaChecksWhy it matters
Virtual machinesPower state, CPU as the host sees itA deallocated VM is an outage the guest cannot report
Azure SQL DatabaseDTU or vCore use, storage used, deadlocksA database at its DTU or storage limit throttles or stops writes
PostgreSQL flexible serversCPU, memory and storageThe same limits for PostgreSQL in Azure
NetworkVPN gateway tunnel state; Application Gateway backend health and 5xx responsesA dropped tunnel or an unhealthy backend cuts users off from healthy servers
BackupFailed Recovery Services vault backup jobsA backup that fails silently is a restore you cannot do
Service HealthAzure Service Health eventsTells you when the problem is Azure's, not yours

Thresholds follow the Azure Monitor recommended alert rules. Every check, with its rule, cause and action, is in the reference for Azure checks. Pending updates of Azure VMs, from Azure Update Manager, are in the Updates module; posture of storage, key vaults and network security groups is in Cloud security.

Before you begin​

  • The Azure Monitor source, with the server's managed identity or a service principal. See Connect Azure Monitor.

  • Read-only roles on each subscription, or on a management group:

    RoleRole IDFor
    Readeracdd72a7-3385-48ef-bd42-f606fba81ae7Inventory, Resource Graph checks such as power state and backup jobs, fired alerts
    Monitoring Reader43d0d8ad-25c7-4714-9337-8ba259a9fe05Platform metrics
  • The module is on. The feature monitoring.azure covers this module and Azure Data Factory; the feature sources.azure_monitor covers the source.

Azure Service Health events are read by the native collector with the server's identity, on a Monitoring platform itself resource; the source does not compute them.

Add a resource​

You do not add Azure resources by hand. The Azure Monitor source lists them with one Resource Graph query over its subscriptions, limited to the resource types you choose, and adds them under the source's entity. Their checks appear the first time the source reports them.

A VM that New Relic or NinjaOne also reports is one resource: sources match it by its resource ID, its fully qualified name or its host name.

Next steps​