Create a cloud action - Microsoft 365 / Entra ID

A Microsoft Entra ID and Microsoft 365 cloud action lets you discover user identities, groups, and license assignments across your Microsoft 365 tenant. This provides insight into identity and access management details for better asset governance.

Prerequisites

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

Create a Microsoft 365 / Entra ID 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 Identity access - Microsoft 365 / Entra ID as the cloud source.
5. Select Create.
6. Enter a name and description for the action.
7. Select Set up new connection, and enter your Tenant ID, Application ID, and Key Vault URI.
8. Select Validate connection to confirm access to Microsoft 365 / Entra ID.
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 user identities, groups, and license assignments in your Microsoft 365 tenant and adds this identity and access data to your inventory. Use it to see how users, groups, and licenses relate to the rest of your environment.

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

Troubleshoot the Microsoft 365 / Entra ID 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 data is discovered. In your app registration, confirm the Organization.Read.All and Directory.Read.All application permissions are added and that admin consent is granted.
• Key vault access errors. Confirm the key vault contains the LansweeperSiteID secret and that inbound access allows the Lansweeper IP ranges for your region.