I’m a forward-deployed engineer at GadellNet. My background is in software development, cybersecurity, and reverse engineering, and most of my day is spent building with Artificial Intelligence (AI). I write code with tools like Claude and Codex, and I build the AI products and integrations we use internally and with clients. So I’ll be honest: I’ve held a pretty low view of Microsoft Copilot. As a developer, it never felt built for me. When I compared it to the tools I use every day, it came up short. I couldn’t see when to use Copilot over the tools I already had.
In late October, I spent two days at a hands-on Microsoft Copilot bootcamp hosted by Pax8 at its Denver-area headquarters, alongside about 65 MSPs from across the US. I went in with an open mind, because I wanted to understand what Copilot could mean for someone who isn’t deep in the software world. As an MSP, that’s many of the people we support. I came out with a different view. I don’t think Copilot became the best AI tool overnight, I just realized I’d been asking the wrong question.
Use Copilot when your team works in Microsoft 365 and wants simple, everyday AI help; use Claude or ChatGPT for building, coding and complex analysis.
The wrong question
I had always reasoned this way: if Claude or ChatGPT is the best tool for me, why wouldn’t I want that for our clients too? It sounds right. But “best” depends on who’s using the tool and what they need from it.
Microsoft isn’t trying to build the most powerful AI product in the world. It’s trying to build the most accessible one. Copilot is built into the tools people already use every day, it’s easy to buy alongside the Microsoft licenses they already have, and it doesn’t take training to get started. For many, that matters far more than having the most advanced model.
Once I saw it that way, it became much clearer when to use Copilot and who it’s for.
When to Use Copilot
Copilot is a strong fit when:
- Your team lives in Microsoft 365. It works inside Outlook, Teams, Word, Excel and SharePoint, so your team doesn’t have to learn a new tool.
- You want quick, practical value. Summarizing email threads, drafting documents, recapping meetings and finding files are everyday wins that add up fast.
- Your users aren’t highly technical. Copilot doesn’t overwhelm people with choices. For someone just starting to use AI, simplicity is a feature, not a weakness.
- Simple licensing and governance matter. It fits into the Microsoft security and compliance setup you may already have.
When to use Claude or ChatGPT
Claude and ChatGPT shine when:
- You’re building something. Developers, analysts, and power users get more out of tools that let them write code, automate workflows, and connect to other systems.
- The work is complex or open-ended. These tools pull ahead when doing deep research, creating long documents, analyzing data, and completing multi-step reasoning.
- You need flexibility. They work across platforms, connect to a wide range of tools, and aren’t tied to one ecosystem.
- You want the cutting edge. New capabilities tend to show up here first.
Copilot or Claude? It’s Not Either/Or
Most organizations will end up with both. The office administrator who wants help drafting an email and the engineer building an automated reporting pipeline have very different needs. Forcing everyone onto the same tool means either overwhelming one group or holding back the other. The right answer is matching the tool to the person and the job.
Using AI Tools Safely
My security background makes this the part I care about most. Whichever tools a team uses, the real challenge is the same: making AI available without losing control of your data. Every new AI tool, plugin or connection is another way in and out of your organization’s environment.
At GadellNet, our focus is helping our clients adopt AI safely and securely. That means a clear governance plan, the right guardrails, and granular control over what AI tools can access and do. We’re building that control ourselves so our clients can unleash AI with confidence.
My Takeaway
I still use Claude every day, and I don’t see that changing. But I now feel much more confident about when to use Copilot and who to recommend it to. The best AI tool isn’t the most powerful one. It’s the one your people will actually use, set up in a way that keeps your business safe.
If you’re deciding when to use Copilot, Claude or both, contact us today.
Frequently Asked Questions: Copilot vs. Claude
Microsoft Copilot is a strong fit when your team already works in Microsoft 365 and wants quick, practical help with everyday tasks like summarizing email threads, drafting documents and recapping Teams meetings. It works best for people who aren’t highly technical, because it lives inside tools they already know and fits into the Microsoft security and compliance setup you may already have.
It depends on who’s using it and what they need. Copilot suits people who want AI inside Outlook, Teams, Word and Excel with little training. Claude suits developers, analysts and power users doing complex, open-ended work like coding, deep research, data analysis and building automated workflows. Most organizations get the best results by matching the tool to the person and the job.
Yes, and most organizations will end up with both. An office administrator drafting emails and an engineer building a reporting pipeline have very different needs. Giving everyone the same tool either overwhelms one group or holds back the other. What matters is a clear governance plan, so every AI tool your team uses has the right guardrails and access controls.
Start with a governance plan that defines which AI tools are approved, what data they can reach, and who can use them. Every new AI tool, plugin or connection is another path in and out of your environment, so control access at a granular level. Copilot works within your existing Microsoft 365 permissions, so clean up overshared files before you roll it out.
