--- title: "Add an Azure node" description: "Add an Azure resource for agentless scanning." product: "Guardian" edition: "Classic" type: "workflow" url: "https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/azure-node/" --- # Add an Azure node Add an Azure resource for agentless scanning. Guardian supports multiple types of Azure nodes. For example, you can add Azure Virtual Network (**VNet**) nodes, Azure Virtual Machine (**VM**) nodes, Azure Storage nodes, and more. Applies to: `Guardian Classic` !!! note Additionally, you can import Azure nodes in bulk rather than individually, as the below process describes. For more information, see [Add Nodes in Bulk via Azure](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-nodes-in-bulk/azure-nodes/index.md). ## Dependencies To add an Azure node, the following dependencies must be met: - **Linux Connection Manager** – Set up in Guardian. For more information, see [Linux Connection Manager](https://docs.cloudhouse.com/guardian/classic/inventory/connection-managers/connection-managers/linux/linux-connection-manager/index.md). - **Microsoft Azure Account** – Account set up and Client secret key generated. For more information, see [Microsoft Azure Account](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/account-setup/microsoft-azure-account/index.md). - **Service Permissions** – Permissions set for the service intended to be scanned. For more information, see [Supported Azure Services](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/supported-cloud-services/supported-azure-services/index.md). ## Add an Azure node Adding an Azure node to your Guardian instance lets you monitor and track the configuration of an Azure resource. To add an Azure node for Agentless scanning, complete the following steps: 1. In the Guardian web application, navigate to the **Add Nodes** tab (**Inventory** > **Add Nodes**). The **Add Nodes** page is displayed. ![Add nodes tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/add-nodes-tab.png) 2. Type 'Azure' in the search bar. 3. Select the 'Azure' node type you want to add and click the **Go Agentless** button to proceed. The **Connect Agentlessly to [Node Type]** page is displayed. ![Go agentless azure](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/go-agentless-azure.png) 4. Here, complete the following options: ![Connect agentlessly azure](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/connect-agentlessly-azure.png) **Connection Manager group** drop-down list : The Connection Manager group that is responsible for scanning your Azure node. Select a Connection Manager group from the drop-down list. **Node Name** field : The name of the node. The value you enter here will be used as the display name in Guardian. **Resource Group Name** field : The name of the resource group the node belongs to in Azure. **Subscription ID** field : The unique alphanumeric string that identifies your Azure subscription. For more information on how to source this, see [Microsoft Azure Account](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/account-setup/microsoft-azure-account/index.md). **Microsoft Entra Tenant ID** field : The Globally Unique Identifier (**GUID**) that represents your Microsoft Entra ID (previously Azure Active Directory) instance. For more information on how to source this, see [Microsoft Azure Account](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/account-setup/microsoft-azure-account/index.md). **Microsoft Entra Client ID** field : The unique identifier assigned to your application, registered within the Microsoft Entra ID (previously Azure Active Directory) instance. For more information on how to source this, see [Microsoft Azure Account](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/account-setup/microsoft-azure-account/index.md). **Client Secret** field : The unique identifier that the application uses to prove its identity when requesting a token. For more information on how to source this, see [Microsoft Azure Account](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/account-setup/microsoft-azure-account/index.md). **[Node Type] Name** field : The name of the node in your Microsoft Entra ID (previously Azure Active Directory). !!! note The name of this field changes depending on the Azure node type you select. For example, for 'Azure Virtual Network' node, this field would be labeled 'Virtual Network Name'. 5. Once you've completed the above options click **Scan Node** to add the Azure node to your Guardian instance. Now, Guardian performs an initial scan of the node. You can wait on this page for the scan to finish, at which point you will see a **View Scan** button. To view the results of this initial scan, click **View Scan**. However, you can also navigate elsewhere while Guardian performs its initial scan of the node. You can then view the status of the scan on the [**Job History**](https://docs.cloudhouse.com/guardian/classic/control/job-history/job-history/index.md) page (**Inventory** > **Job History**). For more information on what to do next after adding a node, see below. ## Where next - [*Read* **Node Scan Results** What every scan of a node collected.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/nodes/node-scan-results/index.md) - [*Organise* **Node groups** Group nodes by type, location and more.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/node-groups/node-groups/index.md) - [*Tune* **Scan options** Choose what each scan collects.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/scan-options/scan-options/index.md) - [*Compare* **Configuration differencing** Compare nodes, groups and scans.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/configuration-differencing/configuration-differencing/index.md) - [*Govern* **Policies** Define the configuration you expect.](https://docs.cloudhouse.com/guardian/classic/control/policies/policies/index.md) - [*Connect* **Integrations** Sync nodes and act on events.](https://docs.cloudhouse.com/guardian/classic/control/integrations/integrations/index.md)