# Troubleshooting Azure Integration for Cloud Insights For detailed error information, including the specific error message returned by Azure, navigate to the **Integration Logs** tab under **Cloud Insights > Settings**. For more information about viewing integration logs, see [Cloud Insights Settings: Integration Logs](https://docs.thousandeyes.com/product-documentation/cloud-insights/settings#integration-logs). | Integration Status | Description | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | Pending | Initial status after the integration has been saved, indicating setup is in progress and awaiting validation. | | Failed | Monitoring is unsuccessful due to errors, such as incorrect permissions or connectivity issues, requiring troubleshooting. | | Connected | No errors detected, indicating the integration is fully operational and actively monitoring resources. | | Connected :warning: | Partially connected integration, indicating the integration is connected but errors have occured, such as incorrect permissions or an expired trial period. | ### Partially Connected Azure Cloud Insights Integrations Some **Inventory Monitoring** and **Flow Logs Monitoring** integrations may display the `Connected` status with a yellow warning symbol. This indicates a “Partially Connected” state. In this state, the integration is connected, but errors have occurred, causing ThousandEyes to only partially succeed in collecting inventory assets from your Azure subscriptions. When **Flow Logs Monitoring** integration errors occur, flow logs are prevented from being successfully ingested or processed. For more information on flow logs errors, see [Azure Cloud Insights Flow Logs Errors](#azure-cloud-insights-flow-logs-errors). ### Azure Cloud Insights Integration Errors If the service principal is created without the necessary role assignments — resulting in the subscription being inaccessible — the integration will transition to `Failed`, and you may encounter the following error: No subscriptions are accessible for inventory collection. Please verify the service principal's role assignments. ### Azure Cloud Insights Monitoring Errors The following errors can occur when setting up a new integration, including when attempting to **Test/Save** the integration: | Inventory Monitoring Error Type | Error Text | Description | | ------------------------------------ | ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Duplicate Name | *Data Integrity Violation.* | An integration with the same name already exists in your ThousandEyes account. | | Invalid Service Principal Parameters | *Failed to obtain Azure AccessToken.* | `AppId`, `TenantId`, or `Password` values supplied for the ThousandEyes integration are invalid. | | Service Principal Reuse | *Azure Integration with same Azure App ID and Tenant Id and Service Type already exists.* | Attempting to reuse an app registration (service principal) that is already assigned to another Azure Inventory Monitoring integration. | | Authentication Failed | *Authentication Failed.* | The client secret credentials provided for the service principal have expired or been removed. | | Subscription Failure | *No subscriptions are accessible for inventory collection* | If the service principal is created without the necessary role assignments—resulting in the subscription being inaccessible—the integration will transition to `Failed` | Note that the Azure portal uses the term "app registration" instead of "service principal". For issues related to configuring your Azure app registration, see [Azure Documentation: What is Application Management?](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/what-is-application-management). ### Azure Cloud Insights Service Bus Queue Errors The following errors can occur when ThousandEyes attempts to read from your Service Bus Queue, resulting in a `Failed` integration state: | Service Bus Queue Error | Description | | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | Resource Not Found | `Service Bus Queue URL` points to a non-existant service bus namespace or queue. | | Unauthorized Access | The Azure *Service Bus Data Receiver* is not assigned at the scope of the dedicated service bus queue created for this integration. | | Service Bus Queue Reuse | `Service Bus Queue URL` is already in use by another integration. | ### Unmonitored Subscription Warnings Cloud Insights does not process VNet flow logs from unmonitored subscriptions, as it cannot enrich these logs with the necessary information. Flow logs from such subscriptions are therefore dropped. Warnings related to these flow logs appear in the **Integration Logs** tab under **Cloud Insights > Settings**. Open the detailed view to see exactly which VNet flow log blob triggered the warning. ### Azure Cloud Insights Flow Logs Errors The following errors can occur when ThousandEyes attempts to download and process flow logs: | Flow Logs Error | Description | | ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Unauthorized Access | The Azure *Storage Blob Data Reader* role is not assigned at the scope of the storage account where the flow logs are stored. This error can also occur when your storage account is not accessible via the internet. | | Storage Account Not Found | The flow log's blob URL points to a non-existing storage account. | | Container Not Found | The flow log's blob URL points to a non-existing container. | | Blob Not Found | The flow log's blob URL points to a non-existing blob. | | Parsing Error | Failure to parse the flow log, such as when the storage account contains files that are not VNet flow logs. | | Failure to process incoming flow logs | Errors occurred while downloading or parsing some of the incoming flow logs. | You can find the flow log's blob URL for an error in the **Integration Logs** tab under **Cloud Insights > Settings**.