Network Management

Azure VM polling stops working after upgrading the SolarWinds Platform to 2025.4

This article provides information about a known issue where Azure VM polling fails in the SolarWinds Platform after upgrading to version 2025.4.

First published date

12/1/2025 12:10 PM

Last published date

12/1/2025 12:10 PM

Overview

After upgrading the SolarWinds Platform to version 2025.4, some users have reported that polling for Azure VMs fails. The users may see an unknown status on the Azure VMs. This issue was introduced after changes made in a previous update intended to address performance issues with Azure Databricks VMs. 

You may see the following errors in the logs:

ERROR SolarWinds.VIM.CloudMonitoring.Pollers.Azure.AccountAutomonitoringPoller - Unable to get Azure VMs.

WARN SolarWinds.VIM.CloudMonitoring.Pollers.Azure.AccountAutomonitoringPoller - Poller failed - ResultError: ErrorCode=10000, ErrorMessage=Azure account automonitoring poller has failed with unexpected error.

Product section

Network Performance Monitor

Cause

SolarWinds Development has confirmed that the polling failure occurs when one or more monitored Azure VMs do not contain the required Azure property: properties.storageProfile.imageReference.publisher

This field identifies the publisher of the image used to build the VM. SolarWinds relies on this property during Azure VM polling.

Resolution

As of Dec 1, 2025, there is no fix or official workaround for this issue.

  • SolarWinds Development has acknowledged this as a known product bug.

  • A fix is currently being worked on. Please monitor this Knowledge Base article for updates.
  • A permanent resolution or patch will be announced here once available.