Connect LogMeIn Resolve MDM to Microsoft Entra ID

To benefit from using automated workflows, LogMeIn Resolve MDM can be integrated with Microsoft Entra ID.

In LogMeIn Resolve MDM, navigate to System > Integrations.
Result: The Integrations page is displayed, where you can get a list of all available applications, or you can filter the list for applications that are already connected to LogMeIn Resolve MDM.
Select Microsoft Entra ID.
Result: The General tab is displayed by default.
Select Connect.
Result: The Microsoft Entra ID connection page is displayed.
Open Microsoft Azure and enable the integration between your LogMeIn Resolve MDM site and Microsoft Entra ID. To enable the integration, you need to register an application for LogMeIn Resolve MDM in Azure. For more information, see Register an application to integrate LogMeIn Resolve MDM with Microsoft Entra ID.
Provide the required credentials of the registered LogMeIn Resolve MDM site, then select Connect.
You can get the values for the required credentials when registering your LogMeIn Resolve MDM site with Microsoft Entra ID.
Provide the following credentials:
- Client ID (shown as Application (client) ID in Entra ID)
- Client secret (shown as Value, not Secret ID, in Entra ID)
- Tenant (shown as Directory (tenant) ID in Entra ID)

Results: Microsoft Entra ID is connected and ready to use. The connected status is shown on the Integrations page in LogMeIn Resolve MDM.

Register an application to integrate LogMeIn Resolve MDM with Microsoft Entra ID

Registering an application establishes trust between LogMeIn Resolve MDM and Microsoft Entra ID.

Before you begin: You must have an admin account on Microsoft Azure.

Register an application in Azure to integrate LogMeIn Resolve MDM with Microsoft Entra ID.
When the registration is ready, copy the Client ID and Tenant information from the Overview pane, as you will need them to set up the connection in LogMeIn Resolve MDM.
For more information, see Register an application in Azure.
Set the application permissions.
For more information, see Define permissions for an application in Azure.
Generate a client secret for the application and copy its value, as you will need it to set up the connection in LogMeIn Resolve MDM.
For more information, see Generate a client secret in Azure.

Register an application in Azure

Log in to Azure at https://portal.azure.com/ as an admin.
Navigate to Microsoft Entra ID.
To open Microsoft Entra ID, you can select View on the Manage Microsoft Entra ID tile.
Select App registrations.
Select New registration.
Define a name for your application. This will be the user-facing name for your app.
In Supported account types, select Accounts in this organizational directory only.
Select Register.

Note: The Overview page contains the details of your registered application. Copy the Application (client) ID and the Directory (tenant) ID, as you will need them to create the connection in LogMeIn Resolve MDM.
Learn more about registering an application from Microsoft's documentation.

Define permissions for an application in Azure

Before you begin: You must register an application in Microsoft Azure.

In Azure, navigate to the App registrations resource.
In the left navigation menu, select API permissions.
Select Add a permission.
To open the permission interface, select Microsoft Graph.
Select Application permissions.
Under User, select User.Read.All.
Under Group, select Group.Read.All for group filtering.
Select Add permissions.

Note: You need admin permissions to grant the User.Read.All and Group.Read.All permissions to your application.
Select Grant admin consent for Default Directory.

Note: You need admin permissions to perform this step.

Result: The status of the user permission is modified to Granted for Default Directory.

Generate a client secret in Azure

Before you begin: You must register an application in Microsoft Azure.

In Azure, navigate to the App registrations resource.
In the left navigation menu, select Certificates & secrets.
On the Client secrets tab, select New client secret.
Fill in the following fields:
- Description: the name of the client secret
- Expires: the expiration date of the client secret
Using the clipboard icon, copy the value of the secret, as you will need it to create the connection in LogMeIn Resolve MDM.

Important: Make sure you copy the value of the secret, not the ID of the secret.
Learn more about creating a client secret from Microsoft's documentation.

Troubleshooting common issues with Microsoft Entra ID integration

Some of the issues you might encounter with your Entra ID integration can easily be fixed.

Error: 400 – Bad Request

This error occurs when one or more of the following fields contains incorrect information:

Client ID (shown as Application (client) ID in Entra ID)
Client secret (shown as Value, not Secret ID, in Entra ID)
Tenant (shown as Directory (tenant) ID in Entra ID)

To correct this error, ensure that you use the credentials provided in the application that you created and you are not using the tenant properties of your Entra ID account. For more information, see Connect LogMeIn Resolve MDM to Microsoft Entra ID.

Error: 401 – Unauthorized

You might receive an Error: 401 – Unauthorized message while connecting Entra ID to LogMeIn Resolve MDM if one or more of the following fields contains incorrect information:

Client ID (shown as Application (client) ID in Entra ID)
Client secret (shown as Value, not Secret ID, in Entra ID)
Tenant (shown as Directory (tenant) ID in Entra ID)

Error: 403 – Forbidden

An Error: 403 - Forbidden message can appear during application registration if the configured permission type is not set to Application.

Correctly configured permission type in Azure

This error can also occur if you do not select Grant admin consent for Default Directory for the User.Read.All and Group.Read.All permissions while defining permissions for your application.

To correct this error, follow the steps in Define permissions for an application in Azure.

Insufficient privileges during filter testing

When testing an Entra ID user query filter, you might encounter the error "Insufficient privileges. Please check that all necessary app permissions have been assigned in Entra ID.". To correct this error, check that the Group.Read.All and User.Read.All permissions are granted in Entra ID. If they are missing, add them, then grant admin consent for both.

For more information on granting permissions, see Define permissions for an application in Azure.

Issues with Workflows when Entra ID is connected

Your Entra ID client secret might have expired if you encounter one or more of the following issues:

Your Workflows suddently don't work even though they used to.
You receive an Error: 401 – Unauthorized message during filter testing.
The Action log shows an error for a workflow.

To resolve this issue, generate a new client secret in Azure as described in Generate a client secret in Azure.

Article last updated: 3 March, 2025