Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Microsoft Azure uses system proxy settings instead of SolarWinds Proxy settings so testing connection while adding a cloud service account may fail

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

Updated July 16, 2018

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.

Environment

  • Orion Platform 2017.3 or later
  • SAM 6.5 or later with cloud monitoring
  • VMAN 8.1 or later with cloud monitoring

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 Orion 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 Orion server to expand the Orion Platform's privileges so it uses proxy settings at the system level instead of the user level.

 

Last modified

Tags

Classifications

Public