Microsoft 365 Just Got Claude Skills (and Nobody’s Using Them)

Microsoft is letting Claude — a competitor’s AI — plug directly into Office at the same depth as its own Copilot. Almost nobody is using it yet, but the reason Microsoft did this is the most strategic move I’ve seen in the whole AI cycle. Once you wire Claude into Microsoft 365, you can build workflows Copilot simply can’t do alone. Let me show you what that looks like, how to set it up, and why Microsoft is opening the gates.

What’s Now Possible

Claude now connects to Microsoft 365 at the connector level — the same access toggles as Copilot. That means Claude can reach into your inbox, your documents, your spreadsheets, and your calendar, all from a single interface. The difference is what you can build on top of it. Copilot lives inside each app individually; Claude with the connector sits outside the apps and reaches into all of them at once.

How to Connect Claude to Microsoft 365

In Claude, go to Connectors, find Microsoft 365, and click Connect. It takes you to the Microsoft login, you enter your details, and you’re in. One important caveat: this only works with a school or business account, not a personal one. Once it’s connected, you can ask the kinds of questions you’d normally ask Copilot — “give me a summary of the emails I received this week,” for example. That part overlaps with Copilot. The real value shows up when you start treating Claude as the hub and building skills on top.

Building a Skill Copilot Can’t Match

A skill is a custom routine Claude runs on demand. Go to Customize, then Skills, and you can browse pre-built ones or write your own. The one I built handles an entire Monday client check-in: it pulls billable hours from an Excel file, filters for any clients approaching their retainer limit, drafts proactive emails to those clients in my tone explaining the burn rate and suggesting next steps, and saves the drafts into Outlook for review before I even sit down. That’s five steps across three different Microsoft apps in one routine. Copilot can’t do it — not because it isn’t smart enough, but because it lives inside each app separately. You have to be in Outlook for the Outlook Copilot, in Excel for the Excel Copilot. Claude works across all of them at once.

Why Microsoft Is Letting This Happen

So why would Microsoft let a rival AI into the house it built Copilot for? Two reasons. First, Microsoft sells seats. Whether you’re talking to Copilot, Claude, or whatever comes next, you’re paying for the underlying Microsoft 365 license — the AI is a feature on top, and the seat is the actual product. Second, Microsoft made a sharp bet: the AI layer is the wrong place to fight, because the best models will always be roughly interchangeable. The data is the moat. If your work lives in 365, you’ll keep paying for 365 even if you drop Copilot. So every other AI that gets good inside Microsoft is one more reason to never leave. Open the gates, keep the territory.

If you’re already in Microsoft 365 and paying for Claude separately, this is worth a closer look. There’s still a reason to keep Copilot too — just not the one you’d expect — and I’ll cover that in another video. If this was helpful, subscribe, and check out the related video above.