This guide provides step-by-step instructions for obtaining API credentials (Client ID, Tenant ID, and Client Secret) from Microsoft Entra ID (formerly Azure AD) and configuring them in Logsign USO for seamless integration.
Register an Application in Microsoft Entra ID
To enable API access, you must create an application in Microsoft Entra ID and obtain the necessary credentials.
Access Microsoft Entra ID
1. Open a web browser and navigate to Microsoft Entra Admin Center.
2. Log in using a Microsoft account with administrative privileges.
3. Select Microsoft Entra ID from the left-hand navigation panel.
Register a New Application
- Go to Enterprise Applications and click + New registration.
- Enter an appropriate Name for the application (e.g., "Logsign USO Integration").
- Under Supported account types, select Singletenant.
- The Redirect URI will be configured later.
- Click Register to create the application.
Retrieve the Client ID and Tenant ID
After registration, go to the Overview page.
Copy and securely store the following:
Client ID (Application ID)
Tenant ID (Directory ID)
Configure Authentication and API Permissions
Create a Client Secret
1. Navigate to Certificates & secrets.
2. Under Client secrets, click + New client secret.
3. Provide a Description and set an expiration period.
4. Click Add.
5. Copy and securely store the Client Secret, as it cannot be retrieved once the window is closed.
Configure API Permissions
Go to API Permissions and click + Add a permission.
Select Microsoft Graph.
Under Application Permissions, add:
- DeviceManagementManagedDevices.Read.All
- DeviceManagementManagedDevices.ReadWrite.All
- DeviceManagementManagedDevices.PrivilegedOperations.All
These three cover everything this integration's methods call (listing devices, rebooting, shutting down, resetting passcodes, remote-locking, and triggering Defender scans/signature updates). The integration authenticates with client-credentials (app-only) flow, so Delegated permissions are not used; do not add Device.Read.All, DeviceManagementApps.Read.All, or DeviceManagementConfiguration.* unless you separately need them for something outside this integration.
Click Add permissions.
Click Grant admin consent to approve the requested permissions.
Configure Microsoft Intune in Logsign USO
Once you have obtained the Client ID, Tenant ID, and Client Secret, follow these steps to configure Logsign USO:
Open Logsign USO
Log in to your Logsign USO platform.
Navigate to Settings
Go to Settings > Responses.
Select Microsoft Intune as the provider.
Enter API Credentials
Fill in the required fields:
- Client ID → Enter the Client ID obtained from Microsoft Entra ID.
- Tenant ID → Enter the Tenant ID obtained from Microsoft Entra ID.
- Client Secret → Enter the Client Secret securely stored earlier.
- Insecure Skip Verify → optional; leave off (unchecked) unless you have a specific reason to bypass TLS certificate verification against the Graph API. Enabling it removes a security check and should not be used in production without a clear reason.
There is no separate Scope field in this form; the integration always requests https://graph.microsoft.com/.default internally, which grants a token for whatever application permissions were consented to above.
Available Methods
Once configured, the device exposes the following actions, usable from an Incident, Alarm, or Action Rule:
- get_managed_devices (Analysis) — lists managed devices.
- reboot_now (Containment) — reboots the target device.
- shutdown (Containment) — shuts down the target device.
- reset_passcode (Containment) — resets the device's passcode.
- remote_lock (Containment) — locks the target device remotely.
- windows_defender_scan (Containment) — triggers a Windows Defender scan on the target device.
- windows_defender_update_signatures (Containment) — triggers a Windows Defender signature update on the target device.
There is no isolate, terminate, or wipe method in the current integration; if you need full device wipe or network isolation, that is not yet supported through this integration.