Applications Systems

Microsoft Azure uses system proxy settings instead of SolarWinds Proxy settings so testing connection while adding a cloud service account may fail

Azure Cloud Monitoring does not use Solarwinds Global proxy settings so clicking Test Connection after adding a cloud service account via the SolarWinds Platform Web Console may fail. Use this workaround to switch from local system settings to Global proxy settings.

First published date

11/9/2018 5:24 PM

Last published date

4/15/2025 9:51 PM

Overview

When adding a cloud service account to monitor Microsoft Azure VMs, Azure uses the system proxy settings instead of SolarWinds global proxy settings. When you add a cloud account and click Test Connections (as described in Add another cloud account ), the connection may fail.

Product section

Server Application Monitor

Cause

By default, Azure runs in system context using the LocalService account instead of the SolarWinds global proxy settings. The AzureTestConnectionJobService doesn't return proxy parameters so testing a connection in the SolarWinds platform Web Console after adding a new Azure account may fail. This issue will be fixed in a future release.

Resolution

Configure a domain policy for the SolarWinds server to expand the SolarWinds Platform's privileges so it uses proxy settings at the system level instead of the user level.

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.