---
title: "Microsoft Azure account"
description: "Find the IDs and secret Guardian needs to scan Azure."
product: "Guardian"
edition: "Classic"
type: "workflow"
url: "https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/account-setup/microsoft-azure-account/"
---
# Microsoft Azure account

To add an Azure node to your Guardian instance for Agentless scanning, you need to set up and configure your Microsoft Azure account with the correct permissions. Log into the [Microsoft Azure Portal](https://portal.azure.com/#home) and complete the instructions described here to source the following:

Applies to: `Guardian Classic`

- [Subscription ID](#subscription-id).
- [Microsoft Entra Tenant ID](#microsoft-entra-tenant-id).
- [Microsoft Entra Application (client) ID](#microsoft-entra-application-client-id).
- [Client Secret](#client-secret).

## Subscription ID

The subscription ID is a unique alphanumeric identifier that is associated with your Azure subscription. Each subscription is associated with a different ID. This value is required to authorise Guardian's access to your node set.

To source the subscription ID, complete the following:

1. Once you are logged into the [Azure](https://portal.azure.com/#home) portal, locate the **Azure services** list and click **Subscriptions**. The **Subscriptions** page is displayed.

    ![Subscriptions](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/node-types/microsoft-azure-account/subscriptions.png)

2. Locate the subscription you want to authorise Guardian's access to and note the **Subscription ID** displayed in the second column.

    ![Subscription id](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/node-types/microsoft-azure-account/subscription-id.png)

## Microsoft Entra tenant ID

The tenant ID is a unique alphanumeric directory identifier that is assigned to your organisation when you sign up for an Azure Active Directory B2C (Azure AD B2C) subscription. A tenant ID can represent an identity, an organisation, or a person. This value is required to identify where your node set is located.

To source the tenant ID, complete the following:

1. Once you are logged into the [Azure](https://portal.azure.com/#home) portal, locate the **Azure services** section and click **Microsoft Entra ID**.

    ![Microsoft entra id](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/node-types/microsoft-azure-account/microsoft-entra-id.png)

2. In the **Overview** tab, note the **Tenant ID** by clicking the copy icon shown next to it.

    ![Tenant id](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/node-types/microsoft-azure-account/tenant-id.png)

## Microsoft Entra application (client) ID

An application (client) ID is a unique alphanumeric identifier that is assigned to each application registered in your Microsoft Entra ID (previously Azure Active Directory). This value is required to grant Guardian access to your Azure application.

To source the client ID, complete the following:

1. Once you are logged into the [Azure](https://portal.azure.com/#home) portal, locate the **Azure services** section and click **App registrations**.

    ![App registrations](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/node-types/microsoft-azure-account/app-registrations.png)

2. In the **Owned applications** tab, your current applications are displayed. Locate the application you want to add to Guardian for monitoring and note the **Application (client) ID** displayed in the second column.

    ![Application client ids](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/node-types/microsoft-azure-account/application-client-ids.png)

## Client Secret

A client secret is a unique alphanumeric identifier that is assigned to each application registered to your Microsoft Entra instance. The secret ID is registered against the client ID and it is used to prove its identity when requesting an access token in Guardian.

To source the client secret, complete the following:

1. Once you are logged into the [Azure](https://portal.azure.com/#home) portal, locate the **Azure services** section and click **App registrations**.

    ![App registrations](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/node-types/microsoft-azure-account/app-registrations.png)

2. In the **Owned applications** tab, your current applications are displayed. In the **Display name** column, click the application you want to source a secret ID for.

    ![Display name application](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/node-types/microsoft-azure-account/display-name-application.png)

3. In the side navigation, click **Certificate & secrets**.

    ![Certificates secrets](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/node-types/microsoft-azure-account/certificates-secrets.png)

4. Then, in the **Client secrets** tab, you can note a previously generated **Secret ID** displayed in the fourth column, or generate a **New client secret** by clicking the button provided.

    ![Secret id](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/node-types/microsoft-azure-account/secret-id.png)

Once you have sourced all of the above information, you can use it to add Azure nodes to your Guardian instance for monitoring.

!!! tip

    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) and [Azure Node](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/azure-node/index.md).