Every MSP owner I talk to has the same headache: finding good technicians. Not warm bodies who can reset a password, but people who can walk into a mess nobody has seen before and work out what’s actually going on. So here’s a question that’s been nagging me. If we keep pushing our techs to lean on AI for every problem, are we quietly eroding the very skill we’re struggling to hire?
The fix that works until it doesn’t
Picture a fairly typical morning. A junior tech gets a ticket about mail not flowing for a shared mailbox. They paste the error into Microsoft 365 Copilot Chat, ask for a PowerShell fix for Exchange Online, run what comes back, and the ticket closes. Great outcome?
Maybe. But ask that tech why it broke and there’s a decent chance you’ll get a shrug. They solved the symptom without ever building a mental model of the system. Do that a few hundred times and you have someone who is fast on familiar problems and lost the moment the answer is wrong, the situation is unusual, or the AI simply isn’t available.
That’s the risk as I see it. Copy-paste fixes. No root-cause understanding. A growing dependence on a tool that can be confidently mistaken. And, longer term, a junior pipeline that never matures into the senior people who can mentor the next lot. If nobody struggles any more, where do the next seniors come from?
But I’m not going back
Let me be clear, I’m not arguing we ban AI from the service desk. Copilot summarising a long ticket thread in Teams or Outlook saves real time. Having it explain an unfamiliar Intune policy setting or draft a script you then review is genuinely useful.
The problem isn’t the tool. It’s how we’re letting people use it. An answer engine makes you dependent. A tutor makes you better. Same technology, very different result.
What I’d do as an MSP owner
A few practical things I’d put in place:
Explain the why before applying the fix. If a tech can’t tell you, in plain words, why a command will solve the problem, it doesn’t get run on a customer tenant.
Use Copilot as a tutor, not just an oracle. Encourage prompts like “explain what this error means and what could cause it” rather than “fix this”. Ask it to walk through the reasoning, then challenge it.
Review AI-assisted tickets. Have a senior skim a sample each week. Look for thin understanding and coach it.
Practise without the safety net. Run regular no-AI troubleshooting sessions. Break something in a lab tenant and let the team work it out the old way.
Document the reasoning, not just the resolution. “Ran script, fixed” teaches nobody anything. “Mailbox permissions were inherited wrongly after a migration, here’s how I confirmed it” builds team knowledge.
None of this is complicated. It just requires deciding that skill development is still part of the job, even when a faster shortcut exists.
The real question
AI will make good technicians better. I’m fairly confident about that. What worries me is whether it will make new technicians good in the first place, or just make them look good until the day it matters. The MSPs that win the skilled labour fight won’t be the ones that use the most AI. They’ll be the ones that use it to grow people rather than replace their thinking.
So I’ll put it to you: in your business, is AI building your techs’ problem-solving muscle, or quietly doing the lifting for them?
Picture asking Copilot in Teams for a status report on a client project. It goes through the project files in SharePoint, pulls numbers from an Excel workbook, checks which Planner tasks are overdue and drafts a summary to send from Outlook. You never open a single one of those apps.
That gets me thinking. If we don’t need to open the apps, who exactly are they for now?
Is software going headless?
“Headless” usually describes a system with the engine but no front end. You talk to it through an API rather than a screen. What I’m seeing with Microsoft 365 Copilot, agents and Copilot connectors looks like the same idea applied to everyday work. You give the AI a goal, and it goes off and talks to the tools directly.
Take it a step further. Bring in a line-of-business system through a connector or an agent built in Copilot Studio, and that report could include CRM or ticketing data too, without logging in to anything. The tools are still doing the work. Nobody is looking at them.
So is the SaaS product we pay for every month slowly becoming a tool for AI rather than for people? For a growing slice of routine work, I think yes. I’m not convinced it’s the whole story, though.
What it means for the people using the tools
If you’re a creator or knowledge worker, the skill shifts from knowing where every button lives to knowing what to ask for. And knowing what good looks like when the answer comes back.
That sounds liberating, and it is. But it means people may understand their own systems less. When the report is wrong, someone still has to know which spreadsheet fed it and why. If nobody ever opens the tool, who notices when the data inside it has rotted?
And humans aren’t leaving the screen entirely. We still need interfaces to review, approve, handle the exceptions and make the creative calls that don’t fit a prompt. I don’t want an agent sending a client proposal without me looking at it first. The UI doesn’t disappear. It shrinks down to the moments where judgement and trust matter.
What it means for the people building the tools
This is where I think the bigger shake-up sits. Plenty of SaaS companies have built their business on a polished interface, per-seat pricing and the stickiness that comes from people living in the app all day. If an agent is the main user, what’s a seat? And how much is a beautiful dashboard worth if nobody looks at it?
My guess is differentiation moves underneath the interface. It shifts to the quality of the data, how good and open the APIs are, reliability, and how well permissions and security are handled. When AI is acting on my behalf, I care a lot about whether the tool respects who is allowed to see what. Trust becomes the product.
Vendors that treat their API as an afterthought could find themselves invisible. The tool might work perfectly but never get picked by the agent.
So, where does that leave us?
I don’t think the apps vanish. I do think the people who build them need to work out who their real customer is. Maybe it’s the human, maybe the agent, and most likely both. For the rest of us, the job is learning to direct the work rather than do every click ourselves, while staying close enough to the detail to spot when it goes wrong.
So I’ll put the question to you. How much of your working day already happens without opening the app? And will the tools you rely on still matter if you never see them?
For years, when I talked to people about AI, I could see a gap between what they expected and what they got. They expected something that would just do the job. Tell it what you want, it goes away, and the work comes back done. What they actually got was a chat box. Clever, sometimes impressive, but you still did all the running around yourself. Copy this, paste that, open another app, reformat it, send it.
Over the last little while I’ve been using Grok Bot heavily across my own business, and for the first time it feels like that gap is closing. Not because the AI suddenly got smarter, although it has, but because it’s easy to set up so that it actually gets things done. That’s the shift I want to talk about, because I think it’s why it’s fast becoming a real option for a lot of businesses, and particularly for SMBs and the MSPs who look after them.
It works the way people always expected AI to work
Most people never cared which model they were using. They cared about outcomes. Did the email get answered? Did the report get written? Did the post go up on time? The industry spent a long time arguing about models and benchmarks while the average business owner just wanted someone, or something, to take a task off their plate.
What I notice with Grok Bot is that I rarely think about the model at all. I think about the job. I describe what I want in plain language, and the assistant works out the steps. It can reach the systems I’ve connected, use a computer and browser when there isn’t a connector, and come back to me with a result rather than a suggestion. That’s much closer to the mental picture most people have always had of an assistant.
I touched on this idea in a recent podcast, Need to Know podcast – Episode 372, where I talked about where AI is heading. The theme is the same: the model is becoming the engine, and what really matters is what it’s connected to and what it’s allowed to do.
What I actually use it for
Rather than talk in the abstract, here’s how I use it day to day. I don’t run one general assistant. I run a number of specialised ones, each set up for a particular job.
Blog writing and scheduling. One assistant drafts articles in my voice, creates a hero image, uploads it to WordPress, picks tags and schedules the post for the next free morning slot. The article you’re reading started there, and it waited as a draft until I approved it.
Social posting. Separate assistants turn blog posts into LinkedIn and X posts, so new content gets shared without me rewriting it each time.
Daily Microsoft 365 security checks. An assistant runs regular checks across my tenants and reports what changed or what looks wrong, so I start the day knowing where to look.
News briefs. Another pulls together the Microsoft and security news I care about into a regular brief.
Podcast preparation. One helps me research news and build outlines and scripts for episodes.
Teams, help desk and email list. Others watch and respond in Teams, help triage support questions and help look after my email list.
The common thread is that each assistant knows its job, knows my standards and knows which tools it can use. When I want to change how something works, I tell it in plain language and it updates how it goes about the task next time. There’s no project plan or developer involved.
None of these needed me to write code. Each one is mostly a set of plain-language instructions, a few connected services and, where it makes sense, a schedule.
Connectors are where the work happens
The thing that turns an AI from a talker into a doer is connections. In my case that means WordPress, Outlook, Teams, GitHub and others. Once an assistant can reach those, a request like “draft this, put it on the blog and schedule it” isn’t a lesson in copy and paste anymore. It’s a task that gets finished.
When there isn’t a connector, there’s a shared computer with a browser the assistants can use. That matters more than it sounds. Plenty of the systems SMBs rely on don’t have neat integrations. Being able to fall back to using a website the way a person would fills a lot of gaps.
Just as importantly, it asks before doing anything that can’t easily be undone or that other people will see. Sending messages, posting publicly, deleting things. That’s the right balance. I want it to do the legwork, but I still want to approve what goes out under my name.
Routines mean it works while I don’t
The other big piece is routines. I can set an assistant to run on a schedule, every morning, every week, or when something happens. My security checks and news briefs run without me asking. When I sit down, the work is already done and waiting for review.
This is the part I think many businesses will find most valuable. A lot of small business admin isn’t hard. It’s just relentless. Checking things, summarising things, chasing things. Handing that rhythm to an assistant frees up real time.
See it in action
If you’re an MSP wondering what this looks like in practice, I’ve recorded a video that shows it. In How I Use AI to Automate Microsoft 365 Administration, Security & Reporting I walk through how I’m using AI to handle the administration, security and reporting work across Microsoft 365 that used to eat my time. It’s the recording of my October Need to Know webinar on managing Microsoft 365 autonomously, so it’s practical rather than theoretical.
Watch it with your own customers in mind. Think about which of their routine checks and reports you could hand off in the same way.
Why this matters for SMBs and MSPs
Picture a ten-person business with no IT staff. They don’t want to evaluate models or build integrations. They want their quotes followed up, their inbox summarised and their social media kept alive. An assistant they can configure in plain English, connect to the tools they already use and put on a schedule is a very different proposition from a chatbot they have to babysit.
For MSPs, I see two opportunities. The first is internal. Your own team can hand off routine checks, reporting and documentation. The second is with customers. Someone still needs to design these assistants well, decide what they can touch, secure the connections and review the results. That’s advisory work, and it’s exactly where a good MSP adds value.
It also raises the same questions I’d ask of any AI tool. What data can it reach? Who approves the risky steps? How do you know what it did? Easy to configure doesn’t mean you skip the thinking. It means the thinking goes into the design rather than the plumbing.
A few lessons from my own setup
Specialise. Several focused assistants work better than one that tries to do everything.
Write down your standards. The more clearly I describe my voice, formatting and rules, the more consistent the results.
Start with drafts. Let it prepare, and you approve, until you trust it with more.
Automate the rhythm, not just the task. The real gains come when work runs on a schedule.
Getting things done is the point
I don’t think the next phase of AI for business will be won by whoever has the best model on a leaderboard. It will be won by whatever makes it easiest for ordinary businesses to get real work done, reliably and safely.
That’s why I’ve leaned into Grok Bot. Not because of what’s under the bonnet, but because it does what I always expected AI to do. I tell it what I need, and it gets on with it. For a lot of businesses, that’s the only measure that has ever really mattered.
Picture two people in the same team asking Microsoft 365 Copilot to do the same job. Same licence, same tenant, same Monday morning. One ends up with something she can send to a customer. The other ends up with something he quietly deletes.
The tool is identical. Everything around it is not.
Where the difference shows up
The task is simple: a customer has sent a long Outlook thread about a delayed project, and the team needs a recovery update for a Teams meeting that afternoon.
The first person starts by thinking. She knows what the customer is worried about, and which commitments are real and which are wishful. She asks Copilot to summarise the thread, then to separate the decisions from the complaints. She opens the project plan in Planner, checks the dates against what Copilot said, and spots a milestone stated with far too much confidence. She corrects it, then asks for a draft in Word, matching the tone of an earlier update stored in SharePoint.
The second person types “write an update about the delay” and pastes the answer into a document. It reads fluently, is polite, and is wrong in two places. He doesn’t notice, because he never decided what a good answer looked like.
Same wand. The difference was framing the problem, checking the result, and knowing where the real data lives.
It goes beyond prompts
I’m wary of the idea that this is all about prompt wording. Prompts matter, but they’re the visible tip. Underneath sits judgement: knowing which Excel workbook is the trusted one and which is last year’s copy with a different name. Knowing that a SharePoint site full of duplicates gives Copilot a confused view of your business. Knowing when a sensible-sounding answer should make you suspicious rather than relaxed.
None of that arrives with a licence. It comes from experience, a healthy scepticism, and someone being willing to say “that doesn’t look right” out loud.
It changes how I think about buying decisions, too. A business that rolls Copilot out to everyone and calls it done has bought wands. A business that invests in tidy data, clear ownership and shared habits for checking AI output has started building wizards. I’d take the second approach with half the licences over the first with all of them. A skilled person with a plain tool beats a novice with a fancy one most days.
What I’d do on Monday
Pick one real task, such as a weekly report or a customer reply, and have your most careful person and your most enthusiastic person both do it with Copilot. Then compare more than the output. How did each of them get there? What did they ask first? What did they check? What did they ignore?
That comparison tells you more than any vendor demo ever will. It shows you what to teach, what to document and where your data needs attention.
If you buy services from an MSP or adviser, apply the same test to them. Ask less about which products they resell and more about which problems they’ve solved that look like yours. Ask who will actually work with you, and what they did the last time it went sideways.
Tools will keep changing every few months. Framing a problem, questioning an answer and understanding your own information will still be worth having when the next one arrives. That’s what I’d invest in first, and I suspect it quietly decides whether any of this pays off.
Clients do the same maths we do. They signed up, they started paying, and every week without a clear return a quiet voice starts asking questions. Was this the right call? Should we keep going? Would another provider move faster? That voice gets louder the longer the wait. I have seen good engagements lose air not because the work was wrong, but because nothing visible landed early enough to quiet the doubt.
When I bring Microsoft 365 Copilot into an MSP or SMB engagement, I do not open with a tour of every feature. I look for one concrete win the client can point at in the first fortnight — something their team feels in the tools they already open each morning.
Pick one snag and make it disappear
Most offices I walk into share a familiar tangle. Status lives in Teams. The brief lives in SharePoint. Tasks sit half-updated in Planner. Follow-ups hide in Outlook. Someone still chases the lot by hand. That chase is perfect early territory for Copilot, because the win is obvious: less hunting, clearer next steps, something finished instead of something promised.
Here is a pattern I like. We take a live project the client already cares about — not a demo tenant, the real one. In Teams, Copilot summarises the channel noise into what actually changed this week. That summary lands in SharePoint beside the project brief so nobody is guessing. From there we ask Copilot to draft Planner tasks that match the open items, with owners the client already named. Outlook gets a short update the account lead can send without rewriting from scratch. Power Automate closes the loop: when a Planner task flips to done, a note hits the Teams channel and a copy files into SharePoint. None of that is theatre. It is one pathway from noise to a checklist that moves.
The client does not need a strategy deck to understand it. They see a messy channel become a usable brief, a task list that matches reality, and an email that went out without another late night. That win makes the monthly fee feel like progress.
Make the win theirs, not yours
I am careful about who owns the story. If I am the only one who can run the Copilot prompts or touch the flow, I have built a dependency, not a win. So I sit with their people in Teams, walk the SharePoint library they already use, and let them trigger the Planner draft and the Outlook reply. Power Automate stays simple enough that their admin can explain it next week without calling me. When the green light moment happens — the first completed loop that did not need a chase email — they should be the ones celebrating it.
That shift matters more than any slide about AI maturity. Doubt fades when the client can say, “we got that done faster this week.” They stop staring at the invoice line and start asking what else we can tidy the same way.
Belief compounds faster than features
I still care about the deeper work — governance, licensing, the longer Copilot roadmap. That work only sticks when early belief is already in place. A visible win across Teams, SharePoint, Planner, Outlook, and a small Power Automate nudge does more for retention than another workshop that ends with “we’ll circle back.”
So my rule is simple. Find the snag they already complain about. Use Copilot on the surfaces they live in. Deliver something they can tick off before the quiet voice gets loud. Do that, and the engagement stops feeling like a bet and starts feeling like a partnership already paying its way.
I keep hearing the same two complaints from MSP owners. Clients feel restless. Prospects who used to answer have gone quiet. The reflex is to add a service, cut the price, or send a longer newsletter. That rarely fixes it. You are asking the market to follow you, and the market is still asking where to.
More product does not create loyalty. A destination does.
Name the ridge, then start up it
Most MSPs I speak with have a catalogue, not a heading. Security, backup, licensing, a Copilot chat if someone asks. None of that is wrong. None of it answers the question an owner actually has: where are you taking my organisation over the next eighteen months?
Pick one serious goal. Not a homepage slogan. Something you can point at on a Tuesday. Every client we look after will have a written path from the tenant they have today to a Microsoft 365 setup their staff actually use, with Copilot where it earns its keep and nowhere else. That is a ridge worth climbing. You can say, out loud, that you have started.
I am not talking about a vision deck. I mean a SharePoint page the client can open without calling you, and a Planner board with the next three moves, names and dates included. The goal is the ridge. The agreed work is the track. If you cannot show both, you do not have a direction. You have a brochure.
Report where you are, not only what you sold
A quiet pipeline is often just confusion. They liked the first meeting. Months later the only message was a renewal or a ticket number. Nobody said whether the journey had moved.
This is ordinary Microsoft 365 work, done on purpose. Keep the roadmap on a SharePoint site they already use. Break the quarter into Planner tasks, not a slide that dies in an inbox. Once a month, post a short note in the shared Teams channel. What moved. What stalled. What is next. Ask them to reply. That is an invitation onto the track, not a speech.
Copilot earns a place here as a drafter, not a mascot. I open the month’s tickets and the Planner board, then ask Copilot in Word, or in Teams, to draft the client note in plain language. I still edit it. I still own the judgement. What I stop doing is staring at a blank page until the update never leaves the building. The owner who ignores Teams should get the same story in Outlook. Same heading, two doors.
Power Automate can nudge you when a Planner date slips, so the note is not an act of memory. This is not a product tour. It is how an MSP shows it has a heading and is still on the track.
Point, then let them choose
People follow someone who names the destination and reports the distance covered. They do not follow a vendor stuffing the pack. There is a plain gap between “we also do Copilot readiness” and “here is the ridge, here is where we stood this month, and you are welcome to walk it with us.”
If clients are fidgeting and prospects have gone quiet, do not add another offer. Stand a little ahead. Point. Say where you are going and where you intend to take them. Keep saying it, inside their tenant, in language they can read before the first coffee.
The ones who want a leader will come. The ones who only wanted a cheaper licence will not. That silence, once you can tell the difference, is useful.
Most workplace AI I use still sits there politely, waiting for me to type something. Microsoft Scout is different, and that’s exactly why I think MSPs and SMBs need to understand how it works before someone in the business goes looking for the download link.
Quick housekeeping first. Microsoft introduced Scout at Build in June 2026 as its first “Autopilot” agent. On 25 September it renamed the product itself to Autopilot, describing it as “previously called Scout”. Yes, same name as Windows Autopilot, the device provisioning service, which is entirely unrelated. The docs still say Scout, so I will too.
So what is it, really?
Scout is an agent that works on your behalf without being prompted every time. The current Frontier release is a desktop app for Windows 11 and macOS. You describe a task in a chat, Scout picks the tools it needs, works through the steps visibly, pauses for your approval on sensitive actions, then hands back the result or saves files to your workspace.
The tools are the interesting bit. Scout can read and write files in an approved workspace folder, run shell commands, drive a browser to fill in forms, and connect to Microsoft 365. That covers Outlook mail and calendar, Teams chats, meetings and transcripts, SharePoint Lists, and files in OneDrive, SharePoint and Teams. It creates Word, Excel and PowerPoint files, remembers your preferences and can spin up parallel sub-agents.
What makes it “always-on” are two background modes. Heartbeat runs check-in prompts every 15 to 120 minutes while you’re away, and Automations run on schedules or triggers you define. The September announcement goes further: Autopilot becomes cloud-hosted, with its own identity, memory and workspace inside your tenant, and you @mention it in Teams, Outlook and documents like a colleague.
Under the hood it’s built on open-source OpenClaw, with Microsoft adding Entra identity and access controls on top.
The permissions story is where you need to pay attention
Scout operates with the user’s existing Microsoft 365 permissions. It can’t see anything the user can’t. That sounds reassuring until you remember how many SMB tenants I see with broad sharing links scattered across SharePoint. An agent that tirelessly works through everything a user can reach will find your oversharing faster than any auditor.
There’s a finer detail buried in Microsoft’s own Responsible AI FAQ. In the Frontier desktop app, model interactions are processed through GitHub Copilot, under separate terms. When that happens, some Microsoft 365 protections, such as data residency, retention, sensitivity label enforcement and eDiscovery, don’t apply to that processing. That’s why admins must complete an attestation before anyone can use it. Read that page before you tick the box.
Getting access is deliberately fiddly. You need Frontier turned on in the Microsoft 365 admin centre, an Intune policy on devices, the attestation form, and a GitHub Copilot Business or Enterprise seat for each user. Miss any one of those and sign-in fails without a clear message, which will make for entertaining helpdesk tickets.
How I’d approach it
Treat this as a pilot for a handful of technically capable people, not a rollout. Clean up permissions and sharing first. Keep the approval prompts on and resist the temptation to click “Always allow”. Lock down heartbeat and automation permissions tightly, because those run when nobody is watching. And budget carefully: Microsoft says Autopilot runs on usage-based billing, not the fixed Copilot licence.
I genuinely think agents that follow through are where this is heading. But an assistant that acts is a very different beast from one that answers. The organisations that do well here will be the ones that realised their governance needed to be ready before the agent arrived, not after.
Most business owners I speak with already use AI every day. They write faster, research faster, publish more content, and stitch together a few small automations. That is genuinely useful. It is also where a lot of people quietly stop — and that is the problem.
Personal speed feels like progress because your inbox clears and your notes look sharper. The business, though, still waits on the same bottlenecks it waited on last month. The opportunity is not another trick for your own desk. It is building AI into the company so the organisation gains capacity and you get room to breathe.
Look at the whole organisation
I ask leaders to walk the company with a colder eye: Operations, Sales, Marketing, Hiring, Finance, and Leadership. Not “what tool is trendy?” but “where does work repeatedly snag?” Microsoft 365 Copilot only matters when it sits inside those snags — Word, Outlook, Teams, SharePoint, Excel, Power Automate — the surfaces people already live in.
In Operations, that might be the status update that always needs a founder rewrite. Copilot in Teams can turn a noisy channel into a clean summary so the ops lead can act without waiting for your evening catch-up. In Sales, the proposal that sits in draft for a week can start as a Word document grounded in a SharePoint brief, then get shaped in Outlook as a reply that sounds like your firm, not a blank template. Marketing can pull approved language from SharePoint instead of reinventing the story in every campaign. Hiring can turn interview notes from Teams into a structured scorecard in Word before the panel forgets what they heard. Finance can ask Copilot in Excel to surface the variance you used to hunt for on Sunday night. Leadership can stop treating every decision as a meeting when the context already lives with the work.
Where AI should earn its keep
I look for four signals. Where can AI remove a recurring bottleneck — the same chase, the same rewrite, the same “can you just…” every week? Where can it save another hire because one strong person suddenly produces far more without burning out? Where does output still wait on the founder’s typing speed rather than the team’s judgement? And which decisions still depend on you that should not — approvals, prioritisation, a first-cut plan — only because nobody else has a workable draft?
That is where Copilot and Power Automate earn their place. A Power Automate flow can move an approved Word pack into the right SharePoint library and ping the owner in Teams without another follow-up email from you. Outlook Copilot can turn a tangled thread into clear next steps so sales does not need you CC’d on everything. Excel Copilot can draft the commentary Finance would otherwise rewrite after every board pack. None of that is about looking modern. It is about taking load off people who already know the work.
The test I use is simple: if you disappeared for two days, would the company stall for vanity reasons or for structural ones? Personal AI helps you type through the vanity. Company AI attacks the structure.
Freedom is what happens when you are not the bottleneck
Freedom shows up when Operations can close the loop, Sales can send a solid first cut, and Finance can answer a straight question without your calendar. Not because you worked faster at eleven at night, but because the organisation no longer routes every sticky decision through one person.
I am not anti personal AI. Use it. Just do not confuse a faster founder with a freer company. Build AI into the workflows, the libraries, and the routines — then step back far enough to lead.
