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.
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 ⚠️
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 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.
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:
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?.
Last updated