VDI App: Azure Machine is Not Associated as Azure Machine in Topology View

Prev Next

Issue

You deployed the ControlUp Agent on an Azure machine (see the setup guide for Azure-AD joined machines) and you can see the Azure machine in the Real-Time DX Console.
Azure machine in the Real-Time DX Console

However, in the VDI App, the Azure machine is not associated in the Machines dropdown list. The Machines (Azure) item is grayed out and you can't select and filter the machine.
Machines (Azure) item grayed out

Technical Background

Virtual machines in the VDI App are associated according to the internal property AssociationMask which you can query with the Invoke-CUQuery cmdlet on the monitor machine.

For example, if you want to know the AssociationMask of all monitored machines, use the following query:

(Invoke-CUQuery -Scheme main -Table Computers -Fields AssociationMask, FQDN).Data

AssociationMask = 1 means that the machine is a virtual machine with the ControlUp Agent installed, but it is not identified as an Azure machine.
Invoke-CUQuery output results

Root Cause

Make sure that the Azure subscription does not show any errors. In our case, the ControlUp Monitor could not connect to the subscription due to missing shared credentials.
ControlUp Monitor not connected to the subscription due to missing shared credentials

Solution

Make sure that no errors are displayed in the data sources screen and status is Connected. This means that the monitor successfully connected to your Azure subscription with the provided shared credentials.
monitor successfully connected

You can now log into the VDI App and check that the machine is available from the Machines (Agent) and Machines (Azure) dropdown.
Machines (Azure) dropdown visible