List every AI tool your team uses, who administers it and what data it touches, and send that inventory to two or three managed IT providers. Choose the one that answers eight AI-specific questions concretely, puts AI tools and automations in its contract, and agrees to a first-month audit, not the one with the lowest per-user price.
Most managed service providers can keep laptops patched and email running. Fewer can tell you who owns your ChatGPT workspace, notice when an automation quietly stops, or review who can see what before Copilot starts summarising files. Those are the gaps AI tools create, and they're the ones to test for, because a general IT contract won't mention them unless you ask.
An AI tool inventory to hand every provider
The running example is an illustrative car repair garage with two sites and 14 staff: technicians, two service advisers, an office manager, a marketing assistant and the owner. Before approaching anyone, the owner listed every AI tool in use, including the ones he suspected staff had adopted without asking:
| Tool | Users | Data it touches | Admin today |
|---|---|---|---|
| Microsoft 365 Business Standard, with Copilot Chat | 14 | Email, files, customer job sheets | Owner |
| Microsoft 365 Copilot Business | 3 | Email, files, meetings | Owner |
| ChatGPT Business | 2 | Marketing copy, supplier research | A former employee's email address |
| AI receptionist on the main phone line | Shared | Callers' names, numbers, booking requests | Service manager |
| Garage management software with AI job-sheet summaries | 10 | Vehicles, job history, customer details | The software vendor |
| Power Automate flow sending invoices to the accounts inbox | None directly | Invoices | Built by an office manager who has left |
| Personal AI accounts and browser extensions | Unknown | Unknown | Nobody |
Two lines in that table are problems before any provider is involved: a business tool administered from a former employee's address, and an automation nobody now understands. The last row is the one every small business has; spotting shadow AI in your team covers how to fill it in. Sending the whole inventory to each provider tells them what you need supported and lets you judge how seriously they read it.
Where to find candidates, and the first filter
Referrals from businesses of a similar size are the best starting point, followed by the partner directories of the software you depend on, such as the Microsoft Marketplace partner directory for Microsoft 365. If a Copilot roll-out is part of the plan, the tutorial on hiring a Microsoft 365 partner for Copilot explains the partner badges.
The usual advice on how to choose a managed service provider still applies: references from similar businesses, response times in writing and clear exit terms. The AI questions come on top of that. Before any of them, apply a quick filter. Drop providers whose smallest client is several times your size, those who can't state response times for urgent issues in writing, and those whose only offer is a long fixed-term contract. Keep two or three, and send them the inventory with the questions below.
Eight AI-support questions, with answers that pass
- "Which AI tools do you support for clients our size?" A pass names tools (Microsoft 365 Copilot, ChatGPT Business, Claude Team) and roughly how many clients use each. "We support all the major platforms" is a fail.
- "How would you find out what AI tools our staff already use?" A pass mentions sign-in and app logs, an inventory of browser extensions on company devices, and a short staff survey. A provider whose only answer is blocking everything will drive the use onto personal phones.
- "Who will own the admin accounts for our AI tools?" A pass: the business owns the top-level accounts; the provider works through delegated access; single sign-on where the plan supports it. ChatGPT Business includes SSO, though automated user provisioning (SCIM) isn't on standalone Business, and a Claude Team Primary Owner can export organisation data including members' chats, so that role should sit with the business, not the provider. Single sign-on for AI tools explains the set-up.
- "How do you check file permissions before Copilot goes wider?" A pass describes permission and sharing reports, and restricting sensitive libraries before adding licences.
- "How do you monitor automations?" A pass mentions failure alerts sent to named people, and knows the platforms' own rules: Power Automate switches a flow off after 14 days of continuous failure (and after 90 days without a trigger, unless it has a Premium licence), and Zapier pauses a Zap when 95% of its runs error over seven days.
- "What's your policy on AI browser agents and extensions?" A pass has an approve-list and treats agents that act in the browser carefully. Anthropic's Claude in Chrome became generally available on 26 August 2026, and Anthropic itself advises against using it to manage financial accounts, so a good provider keeps agents off the office PC that runs banking and payroll. See spotting fake AI apps and risky extensions for the wider risk.
- "Do you earn anything from licences you recommend?" Many providers resell licences, which is normal. A pass is a straight answer and a willingness to show the licence price separately from their fee.
- "What AI do you use on our tickets and data?" Many IT management platforms now include AI; Atera, for instance, made its AI Copilot free on every plan from June 2026. A pass names the tools, says where your ticket data is processed and whether it's used to train anything, and puts that in writing.
Two replies to the same question, side by side
How a provider answers in writing tells you how it will work. Here are the replies the garage received to question 3, about who owns the AI admin accounts (illustrative, lightly shortened):
Provider A: "We'll take over administration of all your platforms as part of onboarding, so you won't need to worry about any of the technical side. Our team will hold the credentials securely in our password vault."
Provider B: "Your business should own every top-level account. We'd move the ChatGPT Business workspace to your address first, since it's currently tied to someone who has left, then set up single sign-on so staff log in with their Microsoft 365 accounts. We'd work through delegated admin roles and keep a record of what we change. If you ever leave us, you already hold the keys."
Provider A's answer sounds reassuring and would leave the garage dependent on it for every change, and stuck if the relationship ended. Provider B read the inventory, spotted the ex-employee problem without being told, and described an arrangement that survives a change of provider. Neither reply is technically wrong; only one is written for the customer.
Three proposals from managed service providers, compared
The garage received three proposals. Prices aren't shown because they depend on your size and the provider's model, but here is how to lay out everything else so the prices become comparable when you add them:
| Item | A: large provider, per user | B: small provider, per user | C: hourly support plus monitoring |
|---|---|---|---|
| Urgent response time in writing | 1 hour | 2 hours | Next business day |
| Microsoft 365 licence management | Included | Included | Billed hourly |
| AI tool administration (ChatGPT, Copilot settings) | Billable project | Included for listed tools | Billed hourly |
| Automation monitoring with alerts | Not offered | Included for named flows | Not offered |
| Permission review before Copilot expands | Billable project | Part of onboarding audit | Billed hourly |
| First-month audit with written findings | No | Yes | No |
| Quarterly review | Annual only | Quarterly | None |
| Exit: handover of admin and documentation | "On request" | Within 10 working days, listed | Not stated |
To compare on price, work out the monthly fee plus the AI and automation work you'd buy as extras in year one, divided by users. Proposal A may look cheapest per user until the AI administration, the permission review and any automation fixes are added as projects. Proposal C is cheap in a quiet month and expensive in a busy one, with no one watching the automations in between. For the garage, B's inclusions matched the inventory almost line for line, so it won even at a higher headline price.
Contract clauses that cover AI tools
A standard managed services agreement rarely mentions AI. Ask for a schedule that does:
- Supported tools are listed by name, with what "supported" means for each (accounts, settings, integrations, user questions).
- Licence changes need written approval. Microsoft's annual subscriptions only allow seat reductions in the first seven days after purchase or renewal, so an extra ten Copilot seats added without asking can't simply be removed next month.
- The business owns every top-level admin account, including emergency access. The provider uses delegated, time-limited access, such as Microsoft's granular delegated admin privileges (GDAP).
- Named automations are monitored, with failure alerts going to a named person at the business as well as the provider.
- New AI tools and extensions go through an approval step, and the provider keeps the approved list current.
- The provider's own AI use is disclosed: which tools touch your tickets or data, and on what terms.
- Exit terms are specific: the admin accounts, documentation and configuration you'll receive, and by when.
For what to expect of the AI vendors themselves on uptime and support, as opposed to your IT provider, see the uptime and support an AI vendor should promise.
What the first 30 days with a provider should include
Agree the onboarding plan before signing, with a deliverable for each week, so you can tell early whether the provider is doing what it promised:
- Week 1: access and inventory. Admin accounts confirmed in the business's name, delegated access set up for the provider, and the AI tool inventory checked against what's actually on the devices and in the sign-in logs.
- Week 2: the audit. A written list of findings with a risk rating and a proposed fix for each, like the one below.
- Week 3: urgent fixes. Everything rated high risk fixed or scheduled, with the owner signing off anything that changes licences or how staff work.
- Week 4: the first review. A 45-minute meeting on what was found, what was fixed, and what goes on the list for next quarter.
A provider that can't commit to written findings in the first fortnight will struggle to give you anything in writing later.
The first-month audit: six findings at the garage
Provider B's onboarding audit is where the choice paid for itself. Its written findings (illustrative, but typical of a business this size):
| Finding | Risk | Fix |
|---|---|---|
| ChatGPT Business workspace owned by a former employee's email address | High | Transfer ownership to the owner; set up SSO; remove the old address |
| An AI "email writer" browser extension on the reception PC, with permission to read every website | High | Remove it; add extensions to the approval list |
| Invoice flow in Power Automate failing for 11 days | High | Fix the expired connection; add failure alerts to the office manager |
| Three staff drafting customer emails in personal AI accounts | Medium | Move them to Copilot Chat under their work accounts; one-page rule sheet |
| "Customer jobs" document library shared with everyone, including workshop tablets | Medium | Restrict to advisers and office before adding Copilot seats |
| Four users on Business Basic raising password-reset tickets | Low | Compare the cost of upgrading with the tickets it would save |
The last finding is a good example of the detail a capable provider brings. Microsoft 365 Business Basic users can't reset a forgotten password themselves; self-service reset needs Business Standard or above, or an Entra ID P1 or P2 licence. Moving four users from Business Basic at $7 to Business Standard at $14 costs $28 a month. If those users forget passwords five times a month between them and each reset takes a quarter of an hour, that's 75 minutes a month; once an hour of that time costs you more than about $22, the upgrade pays for itself. The provider showed the sum instead of simply recommending the upgrade.
A failure the right provider would have caught
Look again at the third finding. The invoice flow had been built years earlier to copy invoices from the garage system into the accounts inbox. When a password changed, the connection expired and every run failed. After 14 days of continuous failure, Power Automate switches a flow off, and it doesn't turn itself back on when the problem is fixed. In the garage's case (illustrative), invoices worth several thousand dollars sat unsent for three weeks, and the first sign was a customer asking why they hadn't been billed.
No AI failed here; an automation did, and nobody was watching it. That's why automation monitoring belongs in the contract of any business that uses AI and automation tools, and why "we'll fix it when you tell us" isn't enough. A provider with failure alerts would have flagged it on the first morning.
When you don't need a managed provider for AI
A five-person independent bookshop with Microsoft 365, one ChatGPT seat and no automations probably doesn't need a managed contract for AI at all. A reliable IT person on call for problems, a half-day review of accounts and sharing each year, and a one-page list of approved AI tools covers it. The case for a managed provider grows with the number of tools, automations and sites, and with how much of the business stops if one of them fails. If you're unsure whether AI work belongs with IT at all, AI consultant versus your IT support company separates the two jobs.
A quarterly review agenda that keeps AI support honest
Whoever you choose, a short quarterly meeting keeps the contract matched to reality. The garage's agenda:
- Licences against use. Copilot's usage report in the Microsoft 365 admin centre shows active users over 7, 28, 90 and 180 days. Seats nobody uses are candidates to drop at renewal.
- New AI tools found or requested since the last review, and decisions on each.
- Automation failures: how many, how fast they were caught, what changed.
- Permission changes to shared libraries and sites, especially any that Copilot users can reach.
- Vendor changes: price rises, renamed or retired products. Suppliers do disappear; the calendar tool Clockwise shut down in March 2026 and deleted user data rather than transferring it, and Microsoft Lens stopped scanning after 9 March 2026. The provider should flag such changes before they bite.
- Two decisions for next quarter, each with an owner.
Forty-five minutes a quarter, with written notes, is enough. A provider who resists even that is telling you how much attention your AI tools will get the rest of the time.
Managed IT and AI: follow-up questions
Should my IT provider or an AI consultant handle our AI tools?
Usually both, for different jobs. The IT provider keeps accounts, security, licences and integrations running day to day. Deciding which tasks AI should do, and designing those workflows, is a different skill that some IT providers have and many don't. Ask your provider which of those it does well, and don't assume one covers the other.
Can a managed provider stop staff using free AI tools?
It can block or limit some tools and browser extensions on company devices, and it can monitor sign-ins to known services. It can't fully control personal phones or home computers. Blocking works best alongside an approved alternative, such as a business AI plan, and a short written policy, so staff have a sanctioned way to get the same help.
What notice period is normal in an MSP contract?
Terms vary widely, so read them before signing rather than assuming. Look for the notice period, whether the contract renews automatically, and above all what the provider must hand over when you leave: admin accounts, passwords, documentation and configuration. A clear exit clause matters more than a short notice period.
Further reads
- AI Security Risks for Small Businesses and How to Close Them — The wider set of AI security risks your provider should cover.
- What Is an AI Browser Agent, and Should Staff Use One? — What browser agents do, and when staff should use one.
- What If Your AI Vendor Shuts Down? Checks Before You Commit — Supplier risk checks your IT provider should help you run.
- SOC 2 and ISO 27001 Explained: Checking an AI Vendor's Security — Reading security certifications, for vendors and providers alike.
- Microsoft 365 Business Premium vs Standard for AI Security — Judge a provider's licence upgrade advice on its merits.
- AI Security Checklist Before Connecting Tools to Email and Files — Checks before any AI tool connects to email and files.
- How to Deflect Password Resets and Routine Requests With AI — Cut password and routine IT tickets: self-service reset licensing, which requests are safe to deflect, bot guardrails, sample chats and honest metrics.
- Best AI Help Desk Tools for Small MSPs (2026) — Eight help desk options for small MSPs compared on the AI that matters: summaries, triage, drafted replies, resolution help and pricing model.
- How Small IT Support Businesses Use AI to Resolve Tickets Faster — Use AI to prepare the evidence and next check for each ticket, while technicians approve changes and confirm that service is restored.
- How to Implement AI in a Small Business With No Tech Team — Running AI with no IT staff: who covers the technical jobs, which tools need no code, how to secure logins, and what to do when something breaks.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Microsoft Learn (Power Automate flow suspension; self-service password reset licensing; GDAP; new commerce cancellation policy); OpenAI ChatGPT Business help pages (SSO and SCIM); Anthropic help pages (Claude Team administration; Claude in Chrome safety guidance); Zapier help pages (auto-paused Zaps); Atera announcement on AI Copilot. Checked September 2026.