The CloudRadial AutomationAI Microsoft Intune extension lets a workflow or agent work with the devices you manage in Intune: inventory managed devices, review compliance policies, configuration profiles, and apps, and take device actions such as sync, remote lock, passcode reset, retire, and wipe. This article covers what the extension can do, the app registration and secrets it needs, which tools require approval, and the skills that ship with it. It is for workspace users who build automations (Admin or Owner Role).
- What the Extension Covers
- Creating the App Registration
- Providing the Credentials to Your Runner
- Reads and Approval-Gated Changes
- Retire Versus Wipe
- Skills
- Tips for Working With Intune Data
What the Extension Covers
The extension calls the Microsoft Graph device management API and provides 14 tools across these areas:
| Area | What you can automate |
| Managed devices | List managed devices filtered by device name, user, compliance state, or operating system, and read one device's details, such as owner, operating system, compliance state, last sync, and serial number |
| Directory devices | Find a device in Entra ID by user or device name when you do not yet have its Intune id |
| Compliance and configuration | List device compliance policies and device configuration profiles |
| Apps | List the apps Intune has detected across managed devices, see which devices a detected app is installed on, and list the managed apps published through Intune |
| Device categories | List the categories used to group managed devices |
| Device actions | Sync a device, remotely lock it, reset its passcode, retire it, or wipe it |
Install it from Extensions like any other catalog extension. See Browsing and installing extensions for the general install flow. The tenant you connect must have an active Intune license.
Creating the App Registration
The extension signs in with an app-only (client-credentials) token for a Microsoft Entra ID app registration, so it runs unattended with no signed-in user. For the general steps of creating an app registration and a client secret, see Creating a Microsoft 365 app registration for the Microsoft 365 extension, but grant this app the Microsoft Graph application permissions below:
| Permission | Used for |
DeviceManagementManagedDevices.Read.All |
Reading managed devices, detected apps, and device categories |
DeviceManagementConfiguration.Read.All |
Reading compliance policies and configuration profiles |
DeviceManagementApps.Read.All |
Reading managed apps |
Device.Read.All |
Reading Entra directory devices |
DeviceManagementManagedDevices.PrivilegedOperations.All |
The device actions: sync, remote lock, passcode reset, retire, and wipe |
If you only want automations to read Intune data, you can leave out the privileged operations permission; the device actions then fail.
Providing the Credentials to Your Runner
Store four secrets in your runner's Key Vault with these exact names. They are separate from the other Microsoft extensions' secrets, so add them under these names even if you have already set another one up.
| Secret | Value |
Intune-ApiUrl |
The Microsoft Graph base URL, normally https://graph.microsoft.com/v1.0. It is the same for every tenant, but the extension still reads it from this secret. |
Intune-TenantID |
Your Entra tenant (directory) ID GUID |
Intune-ClientID |
The application (client) ID GUID from the app registration's Overview page |
Intune-ClientSecret |
The client secret value created under the app registration's Certificates & secrets |
The runner reads these secrets itself and the agent never asks you for them. For how to add secrets, see Accessing and updating your runner's Key Vault. If you manage a separate tenant for each client, see Managing companies and per-company credentials.
Reads and Approval-Gated Changes
Of the 14 tools, 9 are read-only and run without interruption. The other 5 are device actions, and every one of them is approval-gated, including sync: the run pauses and the request appears as an Action Required item in the Inbox until someone approves it. See Handling Action Required items in the Inbox.
| Tool behavior | Tools |
| Approval-gated | Sync a device; remotely lock a device; reset a passcode; retire a device; wipe a device |
| Read-only | List managed devices; read a managed device; find directory devices by user or name; list compliance policies; list configuration profiles; list detected apps; list devices with a detected app; list managed apps; list device categories |
The extension does not change policies, profiles, or app assignments.
Retire Versus Wipe
Both actions take a device out of service, but they are not the same. Confirm which device the request targets before you approve either one.
- Retire removes company data and management from the device and leaves the user's personal data. Use it to offboard a departing employee's device.
- Wipe factory-resets the device and is destructive. Use it for a lost or stolen device. A wipe can optionally keep the enrollment data, the user data, or both.
Skills
The extension ships five skills that guide an agent through common Intune tasks:
| Skill | Use it to |
| Inventory Managed Devices | Find, list, or read managed devices, for example a user's laptop, noncompliant Windows devices, or a device's serial number. Read-only. |
| Review Compliance | List compliance policies and configuration profiles, or find which managed devices are noncompliant. Read-only. |
| Review Apps | List detected apps, see which devices an app is installed on, list device categories, or list the managed app catalog. Read-only. |
| Remediate a Device (Sync / Lock / Reset) | Troubleshoot a device with a non-destructive action: force a sync, remotely lock it, or reset its passcode. Each action is approval-gated. |
| Retire or Wipe a Lost Device | Retire a departing employee's device, or wipe a lost or stolen one. Both are approval-gated; wipe is destructive. |
To give an agent these skills, see Creating custom agents and using them in workflows.
Tips for Working With Intune Data
- Refer to a device by name or by its user. The agent looks up the managed device id first, then acts on it.
- If a device is not in the managed device list, the agent can search Entra directory devices by user or device name instead
- List tools return the complete result in one call, so you do not page through results. Ask for a filter, such as compliance state or operating system, to keep large fleets focused.
- If reads work but device actions fail, check that the app has
DeviceManagementManagedDevices.PrivilegedOperations.All - Once the secrets are in place, ask the AI Playground to list your managed devices to confirm the connection works
If you are still having trouble, we’re here to help! Submit a ticket here for assistance, and don’t forget to check our status page to ensure there are no outages in your area.
Comments
0 comments
Please sign in to leave a comment.