Create a cloud action - Microsoft Intune

Prev Next

Create a Microsoft Intune cloud action to discover and manage endpoints enrolled in Intune. This helps keep your device inventory synchronized and provides visibility into compliance, security, and status information for each managed endpoint.

Prerequisites

Create a Microsoft Intune cloud action

  1. In your Lansweeper Site, go to Discovery > Actions.
  2. Select Create action.
  3. Select Cloud as the action type, and Microsoft Intune as the cloud source.
  4. Select Create.
  5. Enter a name and description for the action.
  6. Select Set up new connection, and enter your Tenant ID, Application ID, and Key Vault URI.
  7. Select Validate connection to confirm access to Microsoft Intune.
  8. Optionally, select Add a device category to include or exclude specific device categories.
  9. Select Create trigger.
  10. Select Instant to run at a scheduled time on select days. Enter the name, time, and days you prefer.
  11. Select Create.
  12. Finally, select Save and finish.

What to expect after the action runs

After the trigger runs for the first time, Lansweeper discovers the endpoints enrolled in your Intune tenant and adds them to your asset inventory. Each discovered device becomes an asset you can open, report on, and correlate with data from Network Discovery and IT Agent Discovery.

To see the Intune data for a device, open the asset and go to the Cloud Properties section of its asset page. This section shows the details synced from Intune.

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

Troubleshoot the Intune cloud action

Where to see scan problems

If a discovered device is missing data, open the asset and check the Scan issues tab. Permission or scanning problems for that asset appear there.

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 devices are discovered. In your app registration, confirm the DeviceManagementManagedDevices.Read.All application permission is added and that admin consent is granted.
  • Some device details are missing. Open the affected asset and check the Scan issues tab for permission or scanning problems.
  • Key vault access errors. Confirm the key vault contains the LansweeperSiteID secret and that inbound access allows the Lansweeper IP ranges for your region.