Network Management

Azure V-Net Gateways and Site-to-Site Connections monitoring fails when a proxy is configured on the SolarWinds Platform

• Azure Cloud monitoring is missing Azure V-Net Gateways and Site-to-Site Connections when they have a proxy server configured. • VMs and Volumes are polled without an issue (these are polled through JobEngine, whereas VNet gateways are through Cortex service) • Customer can make the same API calls through 3rd party tools like Postman but fails in the SolarWinds Platform.

First published date

10/8/2025 4:29 PM

Last published date

12/11/2025 5:24 PM

Overview

Monitoring of Azure Virtual Network Gateways and Site-to-Site Connections fails to authenticate when the SolarWinds Platform Server is deployed behind corporate proxy servers without direct access to login.microsoftonline.com. The issue appears as authentication timeouts during Azure Active Directory login, even though Azure Management API calls successfully pass through the proxy.

Example error in VIM>CloudMonitoring>Collector>Collector_[].log:

ERROR RestApi.SolarWinds.Cortex.Client.ICortex - Exception occurred during request processing by 'InvokeCommandInternalAsyncHttp' method.

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

Product section

Network Performance Monitor

Cause

The Azure Cloud Monitoring SDK, used for monitoring Virtual Network Gateways via the SolarWinds Cortex service, operates through two separate communication channels:

Management API calls (to management.azure.com) - Work correctly through your proxy.
Authentication calls (to login.microsoftonline.com) - Fail because Microsoft's ADAL library uses its own HTTP client that ignores our proxy configuration. The HTTP client in Microsoft’s ADAL library attempts to connect directly to login.microsoftonline.com. This results in timeouts during Azure authentication, as access to login.microsoftonline.com from the SolarWinds server is most likely restricted.

Resolution

This issue is addressed in SolarWinds Platform 2026.1, available now as a release candidate. This fix will continue to be validated during this phase before general availability. Consider upgrading your environment. If you cannot upgrade, use the workaround below.

Ensure the SolarWinds server has direct network access to login.microsoftonline.com and management.azure.com on port 443.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.