Intune AI agent that answers device questions in

Teams and Slack, and runs the fix after approval.

No. Copilot in Intune is Microsoft's assistant for admins, powered by Security Copilot, and it answers fleet questions inside the Intune admin center. An Intune AI assistant from Workativ lives in Teams or Slack and is aimed at the person who owns the laptop or phone. Some teams use both: Copilot for the admin's own analysis, Workativ for everyone else.

Why a device shows as not compliant, whether an app is assigned to them, whether a new laptop has finished enrolling, what IT can see on a personal phone, and how to report a lost one. The agent reads that device's record in Intune and replies in plain words, with the fix when there is one.

Sync, restart, remote lock and app assignment on request, and retire or wipe behind an approval, which covers an Intune remote wipe for a lost phone. These are the remote actions Intune already has in its console. You choose which of them are switched on, and for which groups of users.

Through an app registration in your Entra tenant that calls Microsoft Graph. Reading devices and compliance needs read permissions only. Wipe and retire sit behind a separate privileged-operations permission, DeviceManagementManagedDevices.PrivilegedOperations.All for wipe, which you grant only if you want those actions in chat.

Yes. Intune's Multi Admin Approval can protect wipe, retire and delete, and Microsoft applies it to app-based Graph calls as well as to admins in the console. A request from the agent then waits for a second admin, and the requester still has to complete the action once it is approved. Chat approval and Multi Admin Approval can run one after the other.

It reads the ownership field in Intune. A personal device gets a retire, which removes company data and settings and leaves personal data alone. A company-owned device can get a wipe, which restores factory settings. The employee is told which one applies before anyone approves.

The employee reports it in chat, the agent locks the device, and the Intune remote wipe is queued for the approver. Microsoft limits a tenant to 500 wipes and 1,000 retires a day, counted across the console, bulk actions and Graph calls, so a mass request is checked against that before it runs.

No. Copilot in Intune is part of Security Copilot and is measured in security compute units, according to Microsoft's documentation. Workativ does not use that capacity, and it works with Intune on its own. If you already run Security Copilot, the two sit side by side.

A chatbot answers a question and stops. An agent reads the device record, decides what applies, runs the action after approval, and logs it. Workativ's older Intune chatbot page covers the question-and-answer side, and this page covers the agent.

Three to five days for most teams. The app registration is quick. Most of the time goes on deciding which actions to allow, who approves them, and testing against a handful of real devices, the way an Intune helpdesk would pilot a change.

Both Teams and Slack work alike. The dashboard shows the questions asked most, the actions run, how many were approved or declined, and which devices keep coming back as non-compliant. Logs can go to your SIEM.