---
title: Set up Infrastructure 360 for Azure
source: https://docs.newrelic.com/docs/infrastructure/infrastructure-360/azure/onboarding-infrastructure-360-azure
---

> #### 💡 PREVIEW
>
> We're still working on this feature, but we'd love for you to try it out!
>
> This feature is currently provided as part of a preview program pursuant to our [pre-release policies](https://docs.newrelic.com/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy).

## Prerequisites [#prerequisites]

Before enabling [Infrastructure 360](https://docs.newrelic.com/docs/infrastructure/infrastructure-360/introduction-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 [#onboarding-enable]

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](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/get-started/activate-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](#adjust-frequency).

## Enable for an existing Azure integration [#existing-enable]

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 [#landing-page-enable]

To enable Infrastructure 360 from this page:

1.  Go to **[one.newrelic.com](https://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 [#terraform-enable]

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 [#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).

### Set up your workspace [#setup-workspace]

Set up a local folder for your Terraform configuration:

1.  Open your terminal or command prompt.
2.  Create a new folder for your project:

    ```bash
    mkdir terraform-integrate
    cd terraform-integrate
    ```

### Create configuration files [#create-config-files]

Create the following three files inside your `terraform-integrate` folder. You can use any text editor.

#### providers.tf

This file tells Terraform which plugins to download.

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

#### variables.tf

This file defines the inputs required to run the script.

```hcl
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
}
```

#### main.tf

This is the core script that enables the auto-discovery feature.

```hcl
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 {}
}
```

### Run Terraform [#run-terraform]

Now that your files are ready, run these commands in your terminal from within the `terraform-integrate` folder.

1.  **Initialize**: Downloads the necessary New Relic provider plugins.

    ```bash
    terraform init
    ```

2.  **Plan**: Checks the configuration and shows you what will happen. Terraform prompts you to enter your IDs and keys here.

    ```bash
    terraform plan
    ```

    Enter the values when prompted for `newrelic_account_id`, `newrelic_api_key`, and the other variables.

3.  **Apply**: Executes the plan and enables the integration.

    ```bash
    terraform apply
    ```

    Type `yes` when asked to confirm.

For more information, see the [New Relic Terraform provider documentation](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/guides/cloud_integrations_guide#azure).

## Use Infrastructure 360 [#using-infrastructure-360]

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

> #### 💡 NOTE
>
> Infrastructure 360 supports entity relationships through native New Relic APM agents (Java, .NET, Python) and OpenTelemetry (.NET).
>
> For Azure Kubernetes Service (AKS) clusters specifically, connecting your application to its AKS cluster requires the New Relic Kubernetes agent or OpenTelemetry. Infrastructure 360 doesn't establish that connection on its own, but once it exists, it completes the chain by mapping the relationship from your application through the AKS cluster to the other Azure infrastructure it depends on.

### View discovered entities and relationships [#view-entities]

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 [#cross-subscription]

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 [#correlate-config-changes]

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 [#monitor-discovery]

Auto-discovery provides visibility into its own operations:

| Component              | Default frequency                       | Customizable |
| ---------------------- | --------------------------------------- | ------------ |
| Entity discovery scans | 3 times per day                         | Yes          |
| Configuration updates  | Near real-time (10 minutes)             | No           |
| Relationship mapping   | With each entity and configuration scan | No           |

## Manage Infrastructure 360 settings [#manage-settings]

### Adjust scan frequency [#adjust-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 [#disable]

> #### ⚠️ IMPORTANT
>
> When you disable Infrastructure 360, you lose access to:
>
> -   Automatically discovered entities and their configurations.
> -   Relationship mapping between Azure resources and APM services.
> -   Real-time infrastructure topology updates.

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 [#next-steps]

If you run into issues, see [Troubleshoot Azure Infrastructure 360](https://docs.newrelic.com/docs/infrastructure/infrastructure-360/azure/troubleshoot-infrastructure-360-azure).