Can your outside IT company (your MSP) run Claude for you?

Partly. Your outside IT company (people in the trade call it an MSP) should look after the parts of Claude that work like the rest of your IT: sign-in, devices and security. The monthly work of teaching Claude how your teams do their jobs fits their contract and their working day badly, though some providers do it well and you can test whether yours does. We sell Claude setup and that monthly work ourselves, so weigh what follows with that in mind.

The Claude details in this post come from Anthropic's own pages, as of October 2026.

What does your IT company do well with Claude?

A good part of Claude's setup is ordinary IT work, the kind your IT company already does for your other tools.

Sign-in comes first. Single sign-on lets your staff log in to Claude with the company account they already use for email. Anthropic's single sign-on guide says it's on the Team and Enterprise plans and is set up by someone with the Owner or Primary Owner role in your Claude account. It also needs the DNS settings for your email domain (the records that prove you own it) and your identity provider, which is the system that runs your company logins. An outside IT company often looks after both already.

Devices are next. On Team and Enterprise, administrators can control the Claude Desktop app (the version installed on a computer) with the same tools IT companies use to look after laptops, and Anthropic's page on configuring Claude Desktop names Jamf Pro, Kandji, Microsoft Intune and Group Policy. One of those settings turns off the app's own updates, so IT decides which version everyone runs. Amit Kothari has written about keeping a whole fleet of laptops on one Claude version. It's careful work, and it suits the people who already manage your machines.

Microsoft 365 may need them too. Connecting Claude to Microsoft 365 for the whole company takes a Claude Owner to switch it on and a Microsoft Entra Global Administrator (the top admin role in your Microsoft account) to give a one-time consent. If your IT company holds that Microsoft role, this step needs them.

They should also agree Claude's security settings before anyone uses it, such as which of your other tools Claude may connect to. Amit's longer piece on what IT should be able to produce before anyone builds on Claude lists those jobs.

What fits an IT contract badly?

The ongoing work on skills. A skill is a saved set of steps Claude follows for one kind of job, such as pricing a quote the way your company does, and our post on what a Claude skill is explains more. Three things make that work an awkward fit for the usual IT contract, and none of them is about how good your IT company is.

The first is where the knowledge lives. Anthropic's tutorial on skills says you don't have to be technical to start creating them.

A good skill depends on knowing how your sales team prices a job and what your best proposals say, and getting that right means sitting with the people who do the work more than once and checking Claude's answers with them.

The second is that Claude keeps changing. Anthropic's release notes show new entries on 9 different dates between September 1 and October 21, 2026. Someone has to read each change and work out whether it helps or breaks one of your skills. Nobody raises a ticket for a change that hasn't caused a problem yet, so this has to be someone's planned work.

The third is how the contract counts. IT companies usually charge per person, per device or per help request. Flamingo, which sells software to IT companies, calls charging per person the most common model in 2026. Fixing a skill that drafts proposals badly doesn't fit any of those units, so the work has to be squeezed into tickets or sold as a separate project.

People who advise IT companies are pushing them to do more with AI. Sunny Kaila of IT By Design, a firm that works with IT companies, wrote about a business owner who asked their provider for help adopting AI safely, with security at the center, and was told no. He was surprised, and he argues that AI help is becoming part of being a trusted technology partner. That owner put security at the center, which we think belongs with your IT company. Your IT company also has your trust and your logins already, so you could fairly argue that skills should follow. Our view is that writing your sales team's skills is a poor use of an IT contract, for them and for you.

How can you test your own IT company?

Some will pass this test, and if yours does, use them. Ask these questions and listen for specific answers:

• Who would sit with our sales team to write a skill, and for how many hours?
• Can you show us a skill you've written for another customer's team, with the names taken out? A security setting doesn't count.
• If we want a small change to a skill every month, how would you charge for it?
• Who reads Claude's release notes for us?
• Where would our skills be kept, and could we see every past version and take them with us if we left?

A partner badge is a weaker sign. Anthropic's announcement of its Claude Partner Network says membership is free and that "any organization that is bringing Claude to market is eligible" to join. So the badge alone doesn't show they've done this work. Amit covers what the partner program gives its members in more depth.

What should you check in your IT contract?

We can't tell you what your contract says, and this isn't legal advice. One read of the scope section, the part that lists what they look after, lets you sort Claude's jobs into three piles.

• Likely theirs, if the contract covers your accounts and laptops: sign-in, installing Claude on the laptops they look after, and network rules (which websites your office network lets through).
• Needs a decision: who gives the Microsoft consent, and who takes the call when Claude won't connect to a tool. A connector is the link that lets Claude read a tool such as your email or your files. A Claude Owner or Primary Owner switches each connector on, and apart from a few exceptions Anthropic lists, each person still signs in to it on their own, so a "won't connect" problem might be for your IT company or for whoever runs Claude for you.
• Probably not theirs: a call saying the proposal skill got your pricing wrong.

Put the first two piles in a short email to your IT company and ask them to confirm it, so both sides know who takes which call.

How do we work with your IT company?

We set Claude up with them. They keep sign-in, devices and security, and they have the last word on security settings, which we agree with them before anything goes live. We do the monthly work on skills with your teams, and an AI board, a few of your own people, decides what changes. The homepage shows how that split works, and how to set up Claude for your company covers the whole setup.

If you'd like help working this out with your IT company, talk to us.