Set up Infrastructure 360 for Azure

Prerequisites

Before enabling Infrastructure 360 for Azure, ensure you have:

• An Azure account with a subscription ID.
• An Azure app registration with the Monitoring Reader role.
• A New Relic account enrolled in the Infrastructure 360 preview.
• Permissions to manage cloud integrations in New Relic.

To enroll in the preview, go to one.newrelic.com > Administration > Preview & Trials and enroll for Infrastructure 360.

There are three ways to enable Infrastructure 360 for Azure:

Enable during Azure onboarding

If you're connecting Azure to New Relic for the first time, follow these steps:

1. Navigate to Infrastructure > Azure.
2. Select an account and click Set up integration.
3. Follow the prompts to create your Azure app registration. For detailed setup instructions, see Connect Azure integrations.
4. During integration setup, enable the Infrastructure 360 option when prompted.
5. Configure the scan frequency. By default, Infrastructure 360 scans three times per day. To change this, see Adjust scan frequency.

Enable for an existing Azure integration

If you already have Azure integrated with New Relic, follow these steps:

1. Go to Infrastructure > Azure and click Manage Infrastructure 360.
2. From the account list, find your Azure subscription and click Install (at the provider account level).
3. Configure the scan frequency as described above.
4. Click Save to enable Infrastructure 360 for your Azure account.

Enable from the Infrastructure 360 page

To enable Infrastructure 360 from this page:

1. Go to one.newrelic.com > Infrastructure > Infrastructure 360.
2. Enable the functionality for your Azure (and AWS) provider accounts under this New Relic account.

If this page is blank (you haven't enabled Infrastructure 360 for any provider yet), click Setup Infrastructure 360 and then enable the functionality.

Enable through Terraform

You can also enable Infrastructure 360 for Azure through Terraform instead of the New Relic UI. This is a step-by-step walkthrough for enabling auto-discovery for Azure integrations using Terraform.

Prerequisites

Before starting, ensure you have the following:

• Terraform installed: Terraform installed on your local machine.
• New Relic account ID: Your New Relic account ID (newrelic_account_id).
• New Relic user API key: A user key to authenticate with New Relic (newrelic_api_key).
• Linked provider account ID: The ID of the Azure account as recognized by New Relic (provider_account_id). This is often found in the New Relic UI under Infrastructure > Azure.
• Region: Your New Relic data region (US or EU).

terraform {
  required_providers {
    newrelic = {
      source = "newrelic/newrelic"
    }
  }
}

variable "provider_account_id" {
  description = "The Azure Subscription ID Equivalent in Newrelic (Linked Account ID)."
  type        = number
}

variable "new_relic_region" {
  description = "The New Relic region (e.g., 'US', 'EU', or 'JP')."
  type        = string
  default     = "US"
}

variable "newrelic_account_id" {
  description = "The New Relic account ID."
  type        = number
}

variable "newrelic_api_key" {
  description = "The New Relic API key."
  type        = string
}

provider "newrelic" {
  account_id = var.newrelic_account_id
  region     = var.new_relic_region
  api_key    = var.newrelic_api_key
}

resource "newrelic_cloud_azure_integrations" "auto_discovery_integrations" {
  linked_account_id = var.provider_account_id

  # This block enables auto-discovery for the account
  auto_discovery {}
}

For more information, see the New Relic Terraform provider documentation.

Use Infrastructure 360

Once enabled, Infrastructure 360 lets you check the relationships among all your Azure entities, including infrastructure, APM, and databases.

View discovered entities and relationships

To view discovered entities and their relationships:

1. Go to All entities and filter for collector.name = auto discovery.
2. Select any Azure entity to see its infrastructure map, which shows relationships between:
   • Azure entities (virtual machines, databases, storage accounts).
   • APM entities (applications, services).
   • Cross-platform connections (Azure resources connected to APM services).

Cross-subscription relationships

If a discovered resource connects to a resource in a different Azure subscription, Infrastructure 360 resolves the relationship automatically:

• If the target subscription is also integrated with Infrastructure 360, the map shows the real target entity and its details.
• If you haven't integrated or monitored the target subscription, the map shows an unknown or uninstrumented entity in its place — the connection is still visible, but entity details aren't available.

Correlate configuration changes with alerts

Infrastructure 360 tracks configuration changes on your Azure resources so you can quickly tell whether a recent change caused an alert or incident, instead of investigating infrastructure and application data separately.

1. Go to All capabilities and select Azure Services.
2. Select any entity from the list and click Configuration explorer to see its current settings, tags, and properties.
3. Compare the timestamps in the configuration changes timeline against your alerts or incidents. A configuration change around the same time as an alert is a strong signal of root cause, letting you correlate configuration changes with your alerts and incidents.

Monitor discovery activity

Auto-discovery provides visibility into its own operations:

Manage Infrastructure 360 settings

Adjust scan frequency

You can customize how often Infrastructure 360 scans your Azure environment:

1. Go to Infrastructure > Azure and click Manage Infrastructure 360.
2. Find your Azure account and click Edit.
3. Select your preferred scan frequency from the dropdown menu.
4. Click Save to apply the changes.

Consider increasing scan frequency if you make frequent changes to your Azure environment, or decreasing it if your infrastructure is stable and you want to reduce API calls.

Disable Infrastructure 360

If you re-enable Infrastructure 360 later, it recreates any entities and relationships that no longer exist, during its next scheduled scan.

To disable Infrastructure 360, follow these steps:

1. Go to Infrastructure > Azure and click Manage Infrastructure 360.
2. Find the account where you want to disable Infrastructure 360.
3. Click Edit and turn off the scan toggle.
4. Click Save to confirm the change.

What's next

If you run into issues, see Troubleshoot Azure Infrastructure 360.