The Founder Is the Ceiling

image

I’ve watched plenty of MSP owners import a new strategy — a pricing model, a sales motion, an AI practice — and then sit back waiting for results that never quite arrive. The framework is fine. The consultant was competent. The slide deck is tidy. Nothing lands. After the third or fourth time you see this pattern, you start to suspect the strategy was never the problem. The person running it was running the same way they always had, with the same instincts, the same blind spots, the same calendar. And the strategy, for all its elegance, quietly gathers dust.

Strategies borrow their ceiling from the founder

Here’s the uncomfortable bit. Every strategy in your business is quietly capped by whoever owns it at the top. A sales playbook built for disciplined follow-up doesn’t survive contact with a founder who hates picking up the phone. A managed services model built around proactive account reviews doesn’t work for an owner who still treats quarterly business reviews as optional. A cyber practice built on hard conversations about risk doesn’t get off the ground when the founder is uncomfortable delivering bad news to clients. The strategy isn’t weak. It’s just being run through the wrong instrument. You can buy a better playbook, hire a better consultant, pay for a better PSA, and you’ll still end up with results shaped by your own habits. That’s not a criticism. It’s just mechanics. The business is a reflection of the person at the top, and the ceiling on your strategies is almost always the ceiling on you.

The tool is a mirror, not a transformation

This is where I see Copilot quietly doing more than most owners realise. Not as a productivity gadget — as a mirror. When I open Copilot in Outlook and ask it to summarise the week’s inbox, I’m confronted with what I’ve actually been spending my time on, not what I thought I was spending my time on. When I ask Copilot in Teams to pull the decisions out of a client meeting, I notice which decisions I keep ducking. When I use Copilot Chat to pressure-test a proposal before I send it, I catch lazy thinking I would have signed off on a year ago. None of that changes my strategy. It changes me. That’s the part that makes the strategy finally move. The upgrade isn’t in the tool. It’s in the habit of using the tool to confront how I actually work, then doing something about what I find. That is a very different thing to rolling Copilot out across the tenant and calling it a transformation.

The hardest part is seeing yourself

Most founders I talk to are genuinely willing to change their business. Far fewer are willing to change themselves. We’ll restructure the team, rewrite the service catalogue, and re-platform the ticketing system before we’ll look honestly at our own calendar, our own decision-making, or our own tolerance for avoidance. The interesting thing is that the same Microsoft 365 tools we’re selling to clients — Copilot, Loop, Planner, SharePoint — are the ones that expose our own patterns if we let them. A Loop page tracking your weekly commitments will tell you the truth about your follow-through in about a fortnight. That’s a confronting experience, and it’s where the real upgrade starts.

Before you import your next strategy, ask a harder question. What would I have to become for this to actually work in my business? If the honest answer is “someone I’m not yet”, the strategy isn’t the first thing that needs upgrading. You are. Everything else in the business eventually rises or falls to that line. That’s not an easy sentence to sit with. It’s also the one I keep coming back to whenever I watch a good strategy fail to stick.

What is connecting Copilot agents to Dataverse, Graph, and connectors, really?

image

When people hear “Copilot Studio agent,” they picture a chatbot. That’s the wrong mental model. A modern agent is a reasoning layer sitting on top of three very different pipes: your business data in Dataverse, your organisational content in Microsoft Graph, and the wider universe of SaaS via Power Platform connectors.

Each pipe has its own auth story. And that’s where almost every SMB and MSP rollout I see comes unstuck.

That’s not a configuration problem. That’s an identity problem dressed up as a configuration problem.

Step-by-Step: wiring an agent to the three pipes
Set the agent’s authentication first

Before you add a single tool, go to Settings → Security → Authentication in your agent. Pick Authenticate with Microsoft. This uses Microsoft Entra ID to identify whoever is chatting — and it’s the prerequisite for almost everything that follows.

Skip this step and your agent runs as nobody. Which means it can’t read Dataverse on the user’s behalf, can’t honour SharePoint permissions, and can’t call a connector as the signed-in user. Get the front door right and the rest gets easier.

Add a Dataverse table as knowledge

Open Knowledge → Add knowledge → Dataverse. You can wire up to 15 tables per agent. Two things that catch people out:

  • Dataverse search must be enabled on the environment first.

  • Add synonyms and glossary terms for any column where your users speak a different dialect to the schema.

“Why doesn’t it find my open opportunities?”

Because your column is called statuscode and your users say “stage.” Synonyms fix that.

Add a Microsoft 365 Graph connector for content

Graph connectors are the other knowledge model — they index external content (Jira, ServiceNow, file shares, intranets) into the same semantic graph that Copilot already uses for Teams, SharePoint, and mail. Set them up in the Microsoft 365 admin center → Search & intelligence → Connectors. ACL-based permission trimming is preserved, so users only see what they’re allowed to see. Microsoft has a clear overview here.

Notice what’s missing? Dataverse is agent-scoped knowledge. Graph connectors are tenant-scoped knowledge. Different governance owners. Plan accordingly.

Add a connector as a tool

In your agent, Tools → Add a tool → Connector. Pick a standard, premium, or custom Power Platform connector. Now the agent can act — create a row, post to Teams, hit your line-of-business API.

Tool = action. Knowledge = retrieval. Don't confuse the two.
Pick the right credentials mode

Every tool asks one question that quietly decides your security posture: Maker Credentials or End User Credentials?

  • Maker Credentials: the connection runs as you, the builder. Easy demos. Terrible for anything user-specific.

  • End User Credentials: each chatter authenticates with their own account. Slightly more clicks for users. The only sensible default for production. Details here.

My recommendation? Default to End User and only fall back to Maker when there’s a genuine service-account scenario — like reading a shared mailbox.

Why this actually changes behaviour

Here’s the real win. Once authentication is correctly threaded through the agent, the same prompt produces different, personally-relevant answers for every user — because it’s their identity flowing into Dataverse, their Graph results coming back, their connector permissions being honoured.

That’s not a chatbot. That’s a tenant-aware assistant.

The other thing I notice with clients: governance conversations get easier. “Who can see what?” becomes a question of existing Entra groups and Dataverse row security — not a brand-new permissions matrix you have to invent for the agent.

Get the auth pattern right once and every agent you build afterwards inherits it. Get it wrong and you’ll be unpicking the same mess for months.

Wire the pipes. Mind the credentials. Ship something your clients actually trust.

Align — Your Team Has To Be In On It

image

I’ve been watching a pattern play out in MSP after MSP lately, and it’s worth naming. The owner or managing director is genuinely switched on about AI. They’re up early on a Saturday tinkering with prompts. They’re subscribed to half a dozen newsletters. They’ve run a pilot on quoting, or proposal drafts, or ticket triage. They can tell you, with real confidence, what GPT-5 does differently to Claude.

Then Monday morning rolls around.

You walk past the techs’ desks and someone is printing a spreadsheet out to “have a proper look at it”. The account manager is manually copying fields from one system into another. The service coordinator is re-reading a long email thread for the third time trying to figure out what the client actually agreed to. Not one of them has opened an AI chat today. Maybe not this week.

The leader has moved. The business hasn’t.

The solo-operator trap

This is where most MSP AI journeys quietly stall. The owner is thinking AI-first. The team is still thinking the way they thought in 2022. And because the owner is the one doing all the experimenting, they can tell themselves a comforting story — we’re on it, we’re ahead of the curve, we’re investing in AI. On paper, yes. In the business, no.

Real adoption isn’t measured by how many prompts the boss has saved or how many pilots are running. It’s measured by what an average Tuesday looks like for the people doing the work. If the first instinct when someone hits a hard problem is to ring a colleague, send an email, or open a spreadsheet — AI hasn’t arrived yet. It’s just a hobby the owner has.

That’s a confronting thought, but it’s the honest one.

You are the coach now

The shift that moves the needle isn’t another tool or another pilot. It’s a change in your job description. At the next team meeting, you stop reporting on AI and start teaching it.

Walk your people through what you tried this week. Show them the prompt that didn’t work, then the one that did. Show them the output that saved you forty minutes on a scope. Let them see you thinking out loud. You don’t need to be an expert — you need to be visibly in motion. That’s what gives them permission to start moving too.

If you’re the most AI-literate person in the building and you keep it to yourself, you’re not leading. You’re collecting.

Make AI the front door

Here’s the non-negotiable I’d put in place this week, and it costs nothing. Every person in the business sets an AI chat — Claude, ChatGPT, or Gemini, pick one — as their browser homepage. Not Google. Not the intranet. Not the weather.

Every single time someone opens a browser, an AI chat window is the first thing they see. A blinking cursor, waiting for a question.

It sounds small. It’s not. Most of the friction stopping people from using AI isn’t capability, it’s habit. They forget it’s there. A homepage removes the remembering. It puts the tool under their nose, dozens of times a day, until asking it first stops feeling like a new behaviour and starts feeling like the normal one.

The real alignment test

So here’s the question I’d sit with. If I walked into your office on a random Tuesday and watched your team for an hour — not you, them — would I see an AI-first business, or would I see a business with an AI-first owner?

If the answer isn’t the same for both, that’s your next piece of work.

Need to Know podcast–Episode 365

In this episode, we dig into Cowork Skills and why they represent a genuine shift from “AI as a novelty” to “AI as part of how work actually gets done.” Not more prompts. Not more tools. But fewer decisions, less friction, and more consistency across the business.
If you’ve ever thought “Copilot is interesting, but it’s not really embedded yet”, this episode is for you.

Brought to you by www.ciaopspatron.com

you can listen directly to this episode at:

https://ciaops.podbean.com/e/episode-365-skills-not-apps/

Subscribe via iTunes at:

https://itunes.apple.com/au/podcast/ciaops-need-to-know-podcasts/id406891445?mt=2

or Spotify:

https://open.spotify.com/show/7ejj00cOuw8977GnnE2lPb

Don’t forget to give the show a rating as well as send me any feedback or suggestions you may have for the show

Resources

CIAOPS Need to Know podcast – CIAOPS – Need to Know podcasts | CIAOPS

X – https://www.twitter.com/directorcia

director@ciaops.com

CIAOPS Blog – CIAOPS – Information about SharePoint, Microsoft 365, Azure, Mobility and Productivity from the Computer Information Agency

Join my Teams shared channel – Join my Teams Shared Channel – CIAOPS

CIAOPS Merch store – CIAOPS

Become a CIAOPS Patron – CIAOPS Patron

CIAOPS Brief – CIA Brief – CIAOPS

CIAOPS Labs – CIAOPS Labs – The Special Activities Division of the CIAOPS

Support CIAOPS – Support CIAOPS

Get your M365 questions answered via email

Please fill out this form

A special thanks to the CIAOPS Patron community for making this podcast possible. You can find the benefits of a subscription to the community and become a member at https://www.ciaopspatron.com
CIAOPS MSP Skills

Microsoft Build

Choose how OneNote opens Microsoft 365 file links

How Storm-2949 turned a compromised identity into a cloud-wide breach

Disrupting Fox Tempest: A cybercrime service that turned “verified” software into a pathway for ransomware

Exposing Fox Tempest: A malware-signing service operation

A faster, more efficient Editor experience with Narrator in Word

Launched: Microsoft 365 Copilot Adoption Hub Redesign

Director or Doer? The AI Question Nobody’s Asking

image

Most of the AI conversations I have these days start the same way. Someone leans in and quietly asks, “Do you think AI is going to take my job?” I understand the worry — it’s everywhere, and it’s loud. But I think it’s the wrong question. The one worth asking is sharper and far more uncomfortable. Are you using AI, or is AI using you? That single reframing changes the whole game. And the window to land on the right side of it is narrowing faster than most people realise.

The Doer Trap

I see the Doer pattern everywhere. Someone types a rushed prompt, reads whatever comes back, tidies up a comma or two, and ships it. The email goes out. The deck gets shared. The summary lands in a meeting. The person feels productive because something got done — but they didn’t really direct any of it. The tool picked the angle, the structure, the tone, even the conclusion. They just drove the delivery truck.

The thing that makes this dangerous is that it feels like progress. Output is going up. Calendars are clearing. But the thinking is going down. The muscles that matter — judgement, taste, point of view — quietly shrink while everyone is busy celebrating how much faster the work moves. If AI is setting the pace, choosing the framing, and deciding what “good” looks like, you are no longer in charge of your own work. You are assisting it.

The Director Shift

The people I watch pulling away from the pack work very differently. They treat AI the way a good manager treats a capable team. They brief it properly. They tell it the audience, the constraint, the outcome they want, and what to leave out. They read the output the way an editor reads a draft — with scepticism, not relief. They push back. They ask it to try a sharper angle, to argue the opposite, to shorten by half. They know what great looks like before they ask for it, and they recognise when the answer is merely adequate.

Being the Director is harder. It takes domain knowledge, taste, and the patience to iterate. But the work that comes out the other side is genuinely yours. The ideas are yours, the standards are yours, the reasoning is yours. AI is doing the heavy lifting on the mechanics while you do the heavy lifting on the thinking. That’s the right shape of the partnership.

The Window Is Closing

Here’s what I think people underestimate. The gap between Directors and Doers is compounding. Every week spent actively learning how to brief, evaluate, and steer these tools is a week of skill you’re banking. Every week spent passively accepting output is a week of skill you’re quietly losing. Six months from now, a year from now, that gap will be visible from across the room — in the quality of decisions, the confidence of arguments, the crispness of output.

The people who dig in now, who actually invest the hours to learn this properly, aren’t just getting better at AI. They’re becoming more valuable than they were before AI existed. Their judgement is sharper. Their output is broader. Their leverage is higher. The people waiting for it to settle down are going to wake up behind, and it will take a lot more than a weekend of prompting tutorials to catch up.

So I’d stop asking whether AI is coming for your job. Ask instead who’s running whose day. Because that answer — today, this week, this month — is the one that decides where you end up.

When Your LLM Goes Down: Are MSPs Designing a New Single Point of Failure?

image

Over the past year, I’ve watched something fascinating—and slightly uncomfortable—happen inside MSPs and their clients’ businesses. AI tools, particularly Microsoft 365 Copilot, have gone from “interesting experiment” to “critical part of how work gets done” at a pace I don’t think many people fully appreciate yet.

And that raises an uncomfortable question we haven’t really answered:

What happens when the LLM isn’t there?

Not slow. Not “a bit less helpful.”
Actually unavailable.

AI Has Quietly Moved Into the Critical Path

In some of the environments I’m seeing, Copilot isn’t just helping draft emails or summarise meetings. It’s shaping decisions.

Staff are using it to draft client responses, interpret data, build proposals, prepare board slides, and make sense of complex information faster than they ever did before. Managers are using it to think through options, not just document outcomes.

That’s important, because it means AI has crossed a line. It’s no longer a convenience layer. It’s becoming part of the business process itself.

From an MSP perspective, that should set off the same internal alarm bells as any other critical dependency. Because if your client’s process assumes Copilot is available, then Copilot downtime is no longer “an inconvenience”. It’s downtime.

The New Form of Business Continuity Risk

We’re very good, as an industry, at talking about disaster recovery in traditional terms. Backups. Redundancy. Failover. RPOs and RTOs.

But AI introduces a different kind of risk—cognitive dependency.

Here’s a simple scenario I’ve already seen play out in smaller ways:

A staff member is used to Copilot summarising long email threads before client calls. One day it’s unavailable. They’re still expected to run the meeting, but they haven’t read the full thread because the process evolved around “the AI will summarise it”.

No data was lost. No system was breached. But productivity drops, confidence drops, and errors creep in.

Now scale that to proposal preparation, reporting, or internal decision-making processes that assume AI assistance.

We haven’t lost data—but we’ve lost thinking capacity under time pressure.

“The AI Will Be Back Soon” Is Not a Strategy

One of the more dangerous assumptions I hear is:
“Microsoft will fix it quickly.”

Maybe. Probably. But that’s not business continuity planning. That’s hope.

As MSPs, we need to start asking different questions during AI discussions:

  • What manual process exists if AI is unavailable for a day?

  • Do staff know how to complete the task without AI, or have we trained that muscle out of them?

  • Which workflows are AI‑assisted—and which are AI‑dependent?

This isn’t about rejecting AI. I’m fully in favour of using Copilot when it genuinely improves outcomes. But professional-grade technology adoption has always meant understanding failure modes, not just success stories.

Designing AI‑Resilient Workflows

The smarter MSPs I’m working with are starting to treat AI like any other tier‑one system:

  • Document the “AI unavailable” version of key workflows

  • Set expectations with clients that AI enhances productivity but is not guaranteed

  • Train staff to validate, understand, and reconstruct work without AI assistance

  • Decide consciously where AI is optional versus where it must never be the only path

Ironically, the organisations doing this best often get more value from Copilot, not less. Why? Because they understand it as an accelerator—not a replacement for thinking.

The Question MSPs Should Be Asking Right Now

AI isn’t going away. Dependency will increase, not decrease. That makes this a leadership issue, not a technical one.

So here’s the question I think every MSP owner should be asking themselves:

If Copilot vanished tomorrow, which of my clients’ processes would break—and would they even realise why?

If the answer makes you uncomfortable, that’s a good thing.

That discomfort is the early warning system telling you it’s time to evolve disaster recovery thinking for the age of AI.

AI Didn’t Remove Programming – It Lowered the Bar

image

One of the most dangerous misunderstandings I hear is:
“AI means we don’t need programming anymore.”

The opposite is true.

We need more programming literacy—just a different kind.

AI doesn’t replace logic, structure, or clarity. It amplifies them. When an AI tool “writes code” for you, what it’s really doing is translating your intent into something executable. If your intent is vague, messy, or logically broken, the output will be too.

MSPs already see this in practice:

  • A poorly described Power Automate flow that works once and then quietly breaks.

  • An AI-generated script that technically runs but makes unsafe assumptions.

  • A Copilot prompt that looks clever but produces useless business output.

The common issue isn’t the tool. It’s the thinking behind the instructions.

Understanding basic concepts—inputs, outputs, conditions, loops, exceptions—has never been more important. The difference now is you don’t need to memorise syntax. You need to think clearly and explain cleanly.


This Is a Business Advantage, Not a Technical Party Trick

Here’s where many MSPs miss the opportunity.

They see AI-assisted “programming” as something clever techs play with internally. In reality, it’s fast becoming a deliverable business capability.

Think about your SMB clients:

  • They know their processes are inefficient.

  • They can explain what they want, but not how to build it.

  • They don’t want a six‑month dev project for a simple workflow problem.

An MSP that can sit with a client, map a process in plain English, and turn it into an automated solution is no longer just “support”. You’re helping redesign how the business operates.

And the simplicity is the point.

A one‑page English description that becomes:

  • A ticket triage workflow

  • An onboarding checklist generator

  • A management report assembler

  • A light internal chatbot using their own documents

None of that needs hardcore development skills anymore—but all of it still needs structured thinking.


Your Team Doesn’t Need Coding Skills – They Need Programming Awareness

This is where MSP leaders need to be deliberate.

You don’t suddenly need Python experts across your service desk. What you do need is:

  • Staff who can break problems into steps

  • People who can explain outcomes unambiguously

  • A shared understanding of how logic flows

If your team can already document SOPs well, they are halfway there.

I’ve seen MSPs get real value by:

  • Treating AI prompts like mini specifications, not chat questions

  • Reviewing AI-generated automations as a team, not blindly deploying them

  • Teaching junior staff how to describe a problem, not just which tool to click

Those are capability investments, not tool training.


The MSPs Who Win Will Treat This as a Core Skill

We’ve crossed a line. Programming is no longer gated by language barriers—it’s gated by thinking quality.

That changes what “technical literacy” means for MSPs.

The firms that thrive over the next few years won’t be the ones chasing every new AI tool. They’ll be the ones that:

  • Build strong internal habits around logical thinking

  • Help clients translate business problems into clear instructions

  • Package simple automation as repeatable, billable outcomes

If English is now the language of code, the question is simple:

Are you teaching your people how to speak it clearly—or assuming the tools will do that for them?

That’s a strategic choice every MSP leader needs to make, sooner rather than later.