Assistants versus copilots
The two shapes of AI tool in IT work, what each can see, and when to reach for which.
Two shapes of AI tool show up in IT work, and they call for different habits.
An assistant is a general chat tool such as ChatGPT or Claude. You paste in context, ask a question, and get an answer. It knows nothing about your environment beyond what you type, which makes it flexible but also blind. You are the integration layer: you supply the facts and you carry the output somewhere useful.
A copilot is AI wired directly into a product you already run. Microsoft Copilot in Windows and Microsoft 365, Security Copilot in Intune and Defender, and the AI features inside many RMM and ticketing tools sit inside the console and can see real data. Security Copilot in Intune, for example, can help build device queries and surface noncompliant endpoints from inside the admin center.
The tradeoff is straightforward. An assistant is private in the sense that it only sees what you paste, but it has no live context. A copilot has rich context but broader access, so its permissions and data handling matter more.
A useful rule: reach for an assistant when you need thinking, drafting, or explanation, and reach for a copilot when the value is in live data the vendor already holds. Learn what each copilot can actually change, not just read, before you trust it with an action.
Pick one assistant and one copilot you have access to. Write one sentence each on what data it can see and what actions it can take without asking you first.
Enjoying the free lessons? Get an email when we publish new courses and updates — no spam, unsubscribe anytime.
Discussion (0)
Ask a question or share what worked for you. Comments are reviewed before they appear.
No comments yet. Be the first to start the discussion!