• /
  • Log in

Azure VMs monitoring integration

New Relic infrastructure monitoring provides an integration for Microsoft Azure Virtual Machines (VMs) that reports data from your Azure VMs service to New Relic. This document explains how to activate this integration and describes the data that can be captured.


New Relic's integration for Azure Virtual Machines reports data about your VMs service, like the VM ID, the VM size, the availability set, and the region name. You can monitor and alert on your Azure VMs data from New Relic, and you can create custom queries and chart dashboards.


Requirements include:

Activate integration

To enable this integration follow standard procedures to activate your Azure service in New Relic.


You must install the infrastructure agent on each VM to see metrics from that host. Connecting your Azure subscription allows New Relic to access VM metadata.

Configuration and polling

You can change the polling frequency and filter data using configuration options.

Default polling information for the Virtual Machines integration:

  • Polling interval: 5 minutes
  • Resolution: 1 data point per minute

Find and use data

To find your integration data, go to one.newrelic.com > Infrastructure > Azure and look for the integration.

You can query and explore your data using the AzureVirtualMachineSample event type. The provider value is AzureVirtualMachine.

For more on how to find and use integration data, see Understand and use data.

Inventory data

Inventory data is information about your system's state and configuration. For details on how to find and use inventory data, see Understand and use data.

The Azure Virtual Machines integration reports this inventory data:

  • availabilitySet
  • bootDiagnosticsEnabled
  • image
  • linuxConfiguration
  • name
  • networkInterfaces
  • osDisk
  • provisioningState
  • regionName
  • resourceGroupName (deprecates resourceGroup)
  • vmId
  • vmSize
  • windowsConfiguration

Other system data

The Azure Virtual Machines integration also collects the following attributes about the service and its configuration:

  • Region
  • Availability zone
  • Instance type
  • Instance ID


If you use Host not reporting alert conditions, the importing of Azure metadata for your VMs will change the hosts registry and result in false alert notifications. To prevent false positives:

  1. For each Azure instance, disable its Host not reporting alert condition.
  2. Update the infrastructure agent for all instances that used this alert condition.
  3. Re-enable each Host not reporting alert condition.

For more help

If you need more help, check out these support and learning resources:

Create issueEdit page
Copyright © 2021 New Relic Inc.