Create a cloud action - Microsoft Azure

Create a Microsoft Azure cloud action to automatically discover assets and services from your Azure environment. This ensures your Lansweeper inventory stays up to date with resources such as virtual machines, storage accounts, and other workloads hosted in Azure.

Prerequisites

• You have completed the steps in Prepare Microsoft Cloud for Cloud Discovery
• Your Azure Tenant ID, Application ID, and Key Vault URI are available.

Create a Microsoft Azure cloud action

1. In your Lansweeper Site, go to Discovery > Actions.
2. Select Create action.
3. Select Cloud as the action type.
4. In the pop-up, select Cloud provider - Microsoft Azure as the cloud source.
5. Select Create.
6. Enter a name and description for the action.
7. Enter your Tenant ID, Application ID, and Key Vault URI.
8. Select List subscriptions.
9. From the list, choose the Azure subscriptions to include in the discovery action.
10. Under Asset types, select the asset types to include in the action.
11. Optionally, select Add a resource group filter to include or exclude specific resource groups.
12. Optionally, select Add tag filter to include or exclude specific tags.
13. Select Create trigger.
14. Select Instant to run at a scheduled time on select days. Enter the name, time, and days you prefer.
15. Select Create.
16. Select Create action.

What to expect after the action runs

After the trigger runs for the first time, Lansweeper discovers the resources in the Azure subscriptions you selected and adds them to your asset inventory. Each discovered resource, such as a virtual machine, storage account, or database, becomes an asset with its own asset page showing details, relationships, and tags.

To see the scanned data for a resource, open the asset and go to the Cloud Properties section of its asset page.

Discovery runs on the schedule you set in the trigger, so the data refreshes with each successful run.

Troubleshoot the Azure cloud action

If the action doesn't return the results you expect, check the following:

• Connection validation fails. Confirm your Tenant ID, Application ID, and Key Vault URI are correct, and that federated credentials and the key vault are configured as described in Prepare Microsoft Cloud for Cloud Discovery.
• No assets are discovered. Confirm the app registration has the Reader role on each subscription you want to scan, and that you selected those subscriptions in the action.
• Some resource properties are missing. A few resource types need more than the Reader role. Add the required permissions with an Azure custom role, then check the asset's Scan issues tab.
• Key vault access errors. Confirm the key vault contains the LansweeperSiteID secret and that inbound access allows the Lansweeper IP ranges for your region.