Network Management

Unable to add Azure government cloud account due to invalid ResourceUri in SolarWinds Self-Hosted Platform

This article discusses an issue where adding an Azure Government (Azure Gov) cloud account in SolarWinds Self-Hosted Platform fails with the UI error Connection failed. It walks through how to confirm the symptom, explains why a successful Entra ID sign-in can still result in an error from Azure Resource Manager , and provides the configuration change and app pool recycle required to resolve it.

First published date

5/13/2026 9:40 PM

Last published date

5/13/2026 9:59 PM

Overview

When adding or testing an Azure Government cloud account in SolarWinds Cloud Monitoring, the SolarWinds Web Console returns the generic error Connection failed. Please check your credential information and try again., even though the Microsoft Entra ID (Azure AD) sign-in logs for the SolarWinds service principal show the authentication as Successful. 

The Cloud Monitoring job log shows that the Azure Resource Manager (ARM) call to retrieve subscription details returns HTTP 401 Unauthorized.

2026-04-07 13:30:12,492 [7] DEBUG SolarWinds.CloudMonitoring.Azure.AzureClientBase - Response recevied. Starting ReadAsStreamAsync
2026-04-07 13:30:12,492 [7] ERROR SolarWinds.CloudMonitoring.Azure.AzureClientBase - Get request 'subscriptions/<subscription-id>?api-version=2022-09-01' failed. StatusCode: Unauthorized, Content: System.IO.MemoryStream
2026-04-07 13:30:12,508 [STP SmartThreadPool Thread #0] INFO  SolarWinds.CloudMonitoring.Jobs.TestConnectionJob.TestAzureConnection - Please check your credential information and try again.
2026-04-07 13:30:12,633 [STP SmartThreadPool Thread #0] ERROR SolarWinds.CloudMonitoring.Jobs.TestConnectionJob.TestAzureConnection - TestConnection failed: System.AggregateException: One or more errors occurred.
 ---> SolarWinds.CloudMonitoring.Azure.Contract.Exceptions.AzureClientException: StatusCode: 401
   at SolarWinds.CloudMonitoring.Azure.AzureClient.CreateExceptionForFailedResponse(HttpResponseMessage response)
   at SolarWinds.CloudMonitoring.Azure.AzureClient.<MakeRequest>d__30`1.MoveNext()
   ...
   at SolarWinds.CloudMonitoring.Azure.AzureClient.<GetSubscriptionDetailsAsync>d__13.MoveNext()

Product section

Network Performance Monitor

Cause

This is caused by the CloudMonitoring.Azure.ResourceUri value in Advanced Configuration being set to a custom Application ID URI.

CloudMonitoring.Azure.ResourceUri is sent as the resource (audience) parameter when requesting an OAuth 2.0 access token from Microsoft Entra ID using the client credentials flow. Microsoft Entra ID happily issues a token whose aud (audience) claim equals that custom App ID URI, which is why the Azure AD Sign-in logs show success.

However, SolarWinds then uses that same token to call the Azure Resource Manager endpoint for Azure Government.

ARM validates the aud claim of the bearer token. Because the token was issued for a different resource and not for ARM, ARM rejects it.

Resolution

A. Update CloudMonitoring.Azure.ResourceUri to the correct Azure Resource Manager audience for Azure                 

     Government, recycle the SolarWinds Orion Application Pool, and re-test the cloud account.

  1. Open the Advanced Configuration page on the Main Polling Engine / Web Server:

    http://<your-orion-server>/Orion/Admin/AdvancedConfiguration/Global.aspx

  2. Locate the CloudMonitoring.Azure section and confirm the Azure Government endpoints. For Azure Gov, the values should be:

         3. Locate the NetMan.CloudMonitoring.Azure section and confirm:

        4. Click Save.

B. Recycle the SolarWinds Orion Application Pool to apply the change:

    • Open IIS Manager.

    • Expand the server > Application Pools.

    • Right-click SolarWinds Orion Application Pool > Recycle.

C. Re-test the credentials in the SolarWinds Web Console:

  • Settings > All Settings > Add Cloud Account (or Edit the existing Azure Gov account).

  • Re-enter / confirm the Tenant (Directory) ID, Client (Application) ID, Application Secret, and Subscription ID.

  • Click Test. The connection should now succeed and the subscription details should load.

Related:

Switch from commercial cloud monitoring to government cloud monitoring in the SolarWinds Platform

Configure Microsoft Azure for cloud infrastructure monitoring in SAM or VMAN