---
title: Troubleshoot Azure Infrastructure 360
source: https://docs.newrelic.com/docs/infrastructure/infrastructure-360/azure/troubleshoot-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).

If you run into issues with [Infrastructure 360](https://docs.newrelic.com/docs/infrastructure/infrastructure-360/introduction-infrastructure-360) on Azure, review the following troubleshooting scenarios.

**No Azure entities appear after enabling auto-discovery**

If no entities appear after enabling auto-discovery, check the following:

-   **Check permissions**: Ensure your Azure app registration has Reader permissions for the subscription and necessary resource groups.
-   **Verify subscription**: Confirm that you configured the correct Azure subscription ID in your New Relic integration.
-   **Wait for the first scan**: The initial discovery can take time. Check back after the next scheduled scan (default is 3 times per day).
-   **Verify preview access**: Confirm that you enrolled your New Relic account in the Infrastructure 360 preview by checking **Administration > Preview & Trials**.

**Entity relationships aren't displaying**

If relationships between entities aren't showing, check the following:

-   **Check whether the appropriate APM agent is installed**: Many relationships require you to install New Relic APM agents that actively report data from your applications.
-   **Check entity naming**: Ensure your Azure resources use consistent naming that allows auto-discovery to match them with APM entities.
-   **Verify network connectivity**: Confirm your Azure resources can reach New Relic's data collectors.
-   **Review resource tags**: Some relationships depend on proper tagging strategies in both Azure and your APM configuration.

**Auto-discovery scans are failing**

If your auto-discovery scans consistently fail, check the following:

-   **Check API limits**: Ensure you haven't exceeded Azure API rate limits. Consider reducing scan frequency temporarily.
-   **Verify app registration**: Confirm your Azure app registration is still valid and hasn't expired.
-   **Review permissions**: Ensure the app registration still has the necessary permissions after any Azure policy changes.
-   **Check subscription status**: Verify your Azure subscription is active and accessible.