Microsoft Intune
Connect Microsoft Intune to Risotto to manage devices directly from Slack conversations
The Organization-wide integration between Risotto and Microsoft Intune provides access to workflow tools that let teams manage devices directly from Slack conversations via Intune's MDM platform.
Prerequisites
Before setting up the Microsoft Intune integration, ensure you have:
- Global Administrator Access - Administrative privileges in your Microsoft Entra ID tenant
- Application Registration Rights - Ability to register applications in your tenant
- Microsoft Graph API Permissions - Access to configure application permissions
- The Org Admin or Manager role in Risotto
Permissions Required
- User.Read.All - resolve a requestor's email to their Entra user
- DeviceManagementManagedDevices.Read.All - list a user's managed devices and view detailed device information
- DeviceManagementManagedDevices.PrivilegedOperations.All - required only if you enable the Restart Device, Lock Device, or Wipe Device tool
- BitlockerKey.Read.All - required only if you enable the Get BitLocker Recovery Key tool; allows reading recovery keys from Microsoft Graph
The Assistant can also build script tools that call Microsoft Graph for Intune through this connection. Grant the app registration the permissions that those calls need.
Setup
Register Application in Microsoft Entra ID
Navigate to Identity > Applications > App registrations.
Click New registration. Give it a descriptive name (e.g., "Risotto"), leave the default settings, then click Register.
On the app's Overview page, copy the Application (client) ID and Directory (tenant) ID.
Create Client Secret
Navigate to Certificates & secrets > Client secrets and click New client secret. Add a description and expiry, then click Add.
Copy the secret Value and store it securely — it cannot be viewed again after this step.
Configure API Permissions
Navigate to API permissions > Add a permission > Microsoft Graph > Application permissions and add the following:
User.Read.AllDeviceManagementManagedDevices.Read.AllDeviceManagementManagedDevices.PrivilegedOperations.All(only if using the Restart Device, Lock Device, or Wipe Device tool)BitlockerKey.Read.All(only if using the Get BitLocker Recovery Key tool)
Click Grant admin consent for <your tenant> and confirm — each permission's status should show a green check.
Open the Intune integration in Risotto
In the dashboard, go to Settings > Integrations and click the Microsoft Intune card. On the App registration card, click Connect.
Enter the app registration details
In the Microsoft Intune dialog, fill in these fields, then click Save:
- Tenant ID: the Directory (tenant) ID.
- Client ID: the Application (client) ID.
- Client Secret: the client secret value.
Both IDs are GUIDs, such as
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.Risotto tests the connection before it saves. If the test fails, nothing is saved and the dialog shows the error. When it succeeds, Risotto shows "Microsoft Intune settings saved", and the App registration card shows Connected with your tenant ID and client ID.
When you save, Risotto checks that the app registration has
User.Read.AllandDeviceManagementManagedDevices.Read.Allwith admin consent. If one is missing, the save fails with "The app registration is missing these Microsoft Graph application permissions, or admin consent for them:" and the missing permission. Risotto does not check the optional permissions on save.
Use the same app registration as Entra ID?
If you already connected Microsoft Entra ID as your identity provider, you can add the Intune permissions to that app registration and enter the same values in both connections. Risotto stores the Intune credentials apart from the Entra ID credentials, so each connection uses only its own values.
A separate app registration for Intune is often the better choice. It keeps the device permissions apart from the user and group permissions, and you can rotate each client secret on its own schedule.
More than one device management platform
The support agent and the Assistant look up a requester's devices in every connected platform, in this order: Jamf Pro, Microsoft Intune, Iru (formerly Kandji), Workspace ONE, then Fleet. They show the devices of all platforms together, each with the platform that reported it. If one platform does not respond, the agent still gets the devices from the others. A device that is enrolled in two platforms shows once for each platform.
Tools for a specific platform, such as the Iru FileVault key tool or the Intune BitLocker key tool, keep using their own platform's connection.
Intune Get Device Information
The tool lists the devices enrolled to a user in Intune, with the name, model, OS, serial number, last check-in, and compliance of each. For one device, it also returns details such as the device ID, owner type, and encryption status. When the user has more than one device, the agent asks which one by name and model, then gets the details of that device. A new tool is named Get Intune Device Details.
- email_address (optional): the user to look up. The default is the ticket requestor.
- device_id (optional): one device of that user.
- Restrict to Requestor Only (default: on): the tool returns only the devices of the ticket requestor. Turn it off to let your team look up other users' devices.
The tool only reads. It does not change a device.
Intune Restart Device
The tool restarts a device of the requester. A new tool is named Restart Device, and Requires Approval is on by default.
- The tool works on all platforms.
- If the requester has more than one device, the agent asks which one, by name and model.
- email_address and device_id (optional): the same as in the device information tool.
- Intune queues the restart. The device restarts the next time it checks in, usually within a few minutes if it is on and online. The agent tells the requester that the restart is queued, not that it is done.
- The requester loses unsaved work on the device.
Tool option:
- Restrict to Requestor Only (default: on): the tool restarts only the devices of the ticket requester.
Intune Lock Device
The tool locks a macOS, iOS, iPadOS, or Android device of the requester. A new tool is named Lock Device, and Requires Approval is on by default.
- Intune cannot lock a Windows PC. The tool refuses Windows devices and locks nothing.
- If the requester has more than one device, the agent asks which one, by name and model.
- email_address and device_id (optional): the same as in the device information tool.
- Intune queues the lock. The device locks the next time it checks in.
- When Intune locks a Mac, it sets a 6-digit PIN to unlock it. An admin finds the PIN on the device's Overview page in the Intune admin center.
Tool option:
- Restrict to Requestor Only (default: on): the tool locks only the devices of the ticket requester.
Intune Wipe Device
The tool erases all data on a Windows device and resets the device to factory settings. You cannot undo a wipe. A new tool is named Wipe Device, and Requires Approval is on by default. Keep approval on, so that a person accepts each wipe before it runs.
- The tool wipes only Windows devices. It refuses macOS devices, phones, and tablets.
- The tool sends a full wipe. It does not keep enrollment data or user data.
- The agent first finds the device with the device information tool. Then it sends device_id, device_name, model, and serial_number (all required). The approver sees these values.
- After approval, Risotto compares the name, model, and serial number with the device in Intune. If one value does not match, Risotto wipes nothing.
- email_address (optional): the same as in the device information tool.
- Intune queues the wipe. The device erases its data the next time it checks in.
Tool option:
- Restrict to Requestor Only (default: on): the tool wipes only the devices of the ticket requester.
Runbook templates
On the Runbooks page, click Browse templates to start a runbook from one of these Intune templates:
- Intune Lost or Stolen Device: finds the device and locks it when it is a Mac, iPhone, iPad, or Android device. Intune cannot lock a Windows PC. When the user confirms that a Windows PC was stolen or will not be recovered, it asks to wipe the PC, and IT approves the wipe before it runs. The runbook always ends with an escalation to IT.
- Intune Restart Device: warns that unsaved work is lost, asks the user to confirm, and queues the restart. It escalates the ticket when the device has not restarted after 15 minutes.
Get BitLocker Recovery Key
The Get BitLocker Recovery Key tool retrieves the BitLocker recovery key for a Windows device managed by Intune — the Windows counterpart of the Jamf/Kandji FileVault key flow. If the user has multiple devices, the tool accepts a serial number to pick the right one.
Tool options:
- Restrict to Requestor Only (default: on) — the tool only returns keys for devices assigned to the ticket requestor. Disable to allow IT staff to query devices for other users.
- Send via DM Only (default: on): Risotto sends the recovery key to the requester in a direct message (Slack or Microsoft Teams), not in the ticket thread. If Risotto cannot send the direct message, it does not post the key in the thread. The tool fails, and the agent escalates the ticket. A tool that was saved with this option off keeps posting the key in the ticket thread until you turn the option on.
If you need additional assistance with this integration, contact your Risotto CSM.
Something wrong or missing? Report an issue · View as Markdown