---
title: "VDI App: Azure Machine is Not Associated as Azure Machine in Topology View"
slug: "solve-azure-machine-is-not-associated-as-azure-machine-in-topology-view"
updated: 2025-09-02T07:33:28Z
published: 2025-09-02T07:33:28Z
canonical: "support.controlup.com/solve-azure-machine-is-not-associated-as-azure-machine-in-topology-view"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.controlup.com/llms.txt
> Use this file to discover all available pages before exploring further.

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

## Issue

You deployed the ControlUp Agent on an Azure machine (see [the setup guide for Azure-AD joined machines](/tim-reorg/docs/real-time-dx-manage-and-monitor-azure-virtual-machines-joined-to-azure-ad)) and you can see the Azure machine in the Real-Time DX Console. ![Azure machine in the Real-Time DX Console](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-GX484KIR.png)

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](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-82155ILX.png)

## Technical Background

Virtual machines in the VDI App are associated according to the internal property **AssociationMask** which you can query with the [Invoke-CUQuery](/tim-reorg/docs/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](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-RXSE8U9Y.png)

## 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](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-2132AH7G.png)

## 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](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-51C5SBU0.png)

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](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-C9RTD1UH.png)