An In-Depth Analysis of the Global Managed Service Provider (MSP) Market

image

1. Introduction

This report provides a comprehensive strategic analysis of the global Managed Service Provider (MSP) market [1][2] . It outlines the industry’s current state, future projections to 2030, and the primary forces shaping its trajectory, including technological transformation, market consolidation, and evolving financial models [3][4][5][6][7] . The central themes of this analysis are the market’s significant growth, driven by increasing IT complexity and a persistent cybersecurity skills gap, and the strategic shifts MSPs must make towards AI, specialization, recurring revenue models, and the development of new AI governance services to maximize value and remain competitive [7][5][8][9][10][11][12][13][14] .

  • Background and Context: Businesses are increasingly shifting from a reactive, break-fix approach to a proactive model for their IT management [15][16] . MSPs are at the forefront of this shift, offering continuous monitoring and specialized expertise that many organizations, particularly small and medium-sized businesses (SMBs), lack in-house [5][17][15] . This transition towards outsourced IT management is a key factor underpinning the industry’s robust expansion [4][18] .

  • Scope of the Report: This research covers the global MSP market with a focus on market size, long-term revenue projections, and a detailed financial analysis of valuation multiples [1][2][19] . It includes an analysis of key market drivers, a deep dive into the impact of AI, the strategic advantages of vertical specialization, an examination of the managed security services segment, an analysis of the evolving vendor partner landscape, and a new focus on the emerging service area of AI governance [3][9][4][20][21] .

  • Methodology: The findings in this report are based on a synthesis of data from multiple market research firms, industry analyses, and technology publications [1][2][15] . The varying projections for market size and growth rates reflect different analytical methodologies and the inclusion of various market sub-segments by these sources [1][7] .
2. In-Depth Market Analysis

The global MSP industry is experiencing a period of dynamic and substantial growth, signaling a strong and increasing reliance on outsourced IT services worldwide [22] .

  • Market Size and Growth Projections:

    • 2026 Forecast: The global MSP market is projected to reach a value between $380 billion and $460.59 billion by 2026 [1][7][23][24] .

    • Long-Term Outlook (2030): The market’s expansion is expected to accelerate significantly, with projections suggesting it will surpass $731 billion by 2030 [1][7][2][19][25] .

    • Compound Annual Growth Rate (CAGR): Forecasts for the market’s CAGR vary, with short-term estimates ranging from 8.7% to 20.3% [7][22] . The long-term CAGR for the period of 2024-2030 is projected to be approximately 13-14% [1][3][26] . While North America is the largest market, the Asia-Pacific region is expected to experience the fastest growth [7][22] .

  • Key Market Drivers:

    • Increasing IT Complexity: The widespread adoption of hybrid and multi-cloud environments has made IT infrastructure more difficult for businesses to manage internally [7][5][22][24][15] .

    • The Persistent IT and Cybersecurity Skills Gap: A severe global shortage of skilled IT and cybersecurity professionals is a primary catalyst for MSP growth [3][5][18][11][17] . The cybersecurity workforce gap was estimated at 4.8 million in 2024 [11] . This talent shortage makes it difficult and expensive for organizations to build and maintain comprehensive internal teams, with 76% of SMBs reporting a lack of sufficient in-house cybersecurity expertise [10][21][27][7] .

    • Rising Cybersecurity Threats: The growing volume and sophistication of cyberattacks, many now AI-assisted, are compelling businesses to seek specialized, continuous security monitoring from MSPs [7][4][28][24][16][29] .

    • Market Consolidation and “Platformization”: The industry is undergoing a significant wave of mergers and acquisitions (M&A) as larger firms acquire smaller ones to expand their service portfolios and geographic reach [3][4][30][31] . This trend is driven by customer demand for a simplified vendor landscape, with 63% of clients preferring to use fewer technology vendors [32] . This creates a strategic imperative for smaller MSPs to either scale, specialize, or position for acquisition [4] .

    • Cloud Adoption and Cost Optimization: The ongoing migration to cloud services creates sustained demand for expert management of cloud migration, maintenance, and cost optimization [5][33][3][24] . Outsourcing allows businesses to shift from capital expenditure (CapEx) to predictable operational expenditure (OpEx) and focus on core competencies [4][18][33][27] .

    • Influence of Major Vendor Ecosystems: Leading platform vendors like AWS, Google Cloud, and ServiceNow are actively shaping the market by overhauling their partner programs [1][18][22] . These changes, centered on AI and outcome-based rewards, compel MSPs to align their strategies with vendor roadmaps [12][13][14] .

    • Regulatory and Compliance Demands: Stringent data protection regulations like GDPR and HIPAA are driving businesses to seek expert help to meet complex compliance requirements [33][10][21][34][35] .
3. Financial Analysis and Valuation

MSP valuations are heavily influenced by the quality and predictability of earnings, with buyers placing a significant premium on recurring revenue and operational maturity [4][19] .

  • The Primacy of Recurring Revenue:

    • Monthly Recurring Revenue (MRR) and its annualized counterpart, Annual Recurring Revenue (ARR), are the most critical metrics in determining an MSP’s worth [33][2][36][37] . Buyers are essentially purchasing predictable future cash flows [38][11] .

    • Managed services typically yield higher gross margins of 50-60%, and in some cases up to 70%, compared to traditional IT projects, making the shift to a recurring revenue model crucial for profitability [39][40][41] .

    • The single most important driver of valuation is the percentage of total revenue that is MRR [37] .

  • Valuation Multiples (EBITDA):
    EBITDA (Earnings Before Interest, Taxes, Depreciation, and Amortization) is the primary metric driving valuation     [19] . Multiples vary significantly based on the MSP’s size, revenue composition, and specialization [4][19][42] .

    • Valuation by Size (EBITDA): [19]
      • $250K – $1M EBITDA: 4x – 5x

      • $1M – $2M EBITDA: 5x – 6x

      • $2M – $5M EBITDA: 6x – 8x

      • $5M+ EBITDA: 8x – 12x+
    • Valuation by Recurring Revenue %: [4]
      • 85%+ MRR: 10x – 15x EBITDA

      • 75% MRR: 8x – 11x EBITDA

      • 60% MRR: 6x – 9x EBITDA

      • < 40% MRR: 4x – 6x EBITDA
    • Premium Multiples: Cybersecurity-focused MSPs (MSSPs) can command a premium of 8x to 15x EBITDA, while AI-integrated platforms with over $35M in revenue can see multiples from 9x to 14x [4][18][42] .

  • Key Factors Driving Higher Valuations:

    • Quality and Composition of MRR: Buyers scrutinize revenue to ensure it is contractually protected and “sticky” [36] . Long-term contracts of 36 months or more can increase a valuation by 10-20% compared to month-to-month agreements [19] .

    • Alignment with Vendor Incentive Programs: Profitability, a key component of EBITDA, is directly enhanced by new vendor incentives [1][18][3] . MSPs that effectively leverage these programs can significantly boost their bottom line, making them more attractive acquisition targets [3][43][44][45][46][47] .

    • Client Health: Low customer churn, high retention rates, and low customer concentration (no single client representing more than 20-25% of revenue) are crucial for de-risking the business for a potential buyer [5][18] .

    • Private Equity Influence: Private equity remains a dominant force in the market, involved in an estimated 69-72% of MSP transactions in 2025 [1][18] .
4. Key Trend: The AI Revolution

Artificial intelligence is an essential tool for modern MSPs, profoundly impacting service delivery, efficiency, and profitability [5][6][4][48] . AI is fundamentally reshaping operations, moving the industry from a reactive to a proactive and predictive model [27][49] . While 90% of MSPs view AI as important, a significant “execution gap” exists, with only 4% having truly operationalized it [48][50] .

  • Impact on Operations and Efficiency:

    • Enhanced Operational Efficiency: AI automates routine tasks like ticket management and password resets, reducing human error and freeing up technicians [22][3][20][48] . This can cut operational costs by 25% and boost technician productivity by 15–25% [51][20][48] .

    • Proactive Problem Solving: AI-powered predictive analytics enable MSPs to anticipate and resolve IT issues before they cause downtime [5][9][27] . This can reduce unplanned downtime by as much as 50% [6] .

    • Dramatic Ticket Resolution Improvements: AI can slash ticket resolution times by 40–70% [51] . One report found a median resolution time of just 4.4 hours for AI-automated tickets, versus 71 hours for human-handled ones [26] .

    • Advanced Cybersecurity: AI is indispensable for modern threat detection, analyzing vast network data in real-time to identify anomalies and new attack patterns that traditional tools miss [6][51] .

  • From Automation to Agentic AI:
    The evolution is moving beyond basic Robotic Process Automation (RPA) to “agentic AI,” where autonomous agents can interpret context, learn from feedback, and act dynamically across different tools and environments     [49][52] . This shift is pushing MSPs to transition from being technology providers to strategic “managed intelligence providers,” offering guidance on strategy, governance, and business outcomes [4][8][53][54][55] .

  • Vendor-Driven AI Enablement and Strategy:
    Major vendors are aggressively pushing partners to adopt and deliver AI solutions through new programs and incentives.

    • AWS: AWS is heavily promoting “agentic AI” through its partner program, launching a new AI Competency and an AI Assessment Fund to help partners build pipelines [5][56][52][57][58] .

    • Google Cloud: Google Cloud has committed a massive $750 million fund to help its partner ecosystem drive customer transformations with agentic AI, supporting everything from assessments to deployment rebates for Gemini and Vertex AI [6][45][59][60][61][62] .

    • ServiceNow: ServiceNow has rebuilt its entire partner program for the “AI agent era,” centered on a new Build Partner Program to foster innovation and create a global marketplace for partner-built AI solutions [22][14][46] .
5. Key Trend: The Rise of Vertical Specialization

In an increasingly crowded and consolidating market, vertical specialization has emerged as a key strategy for MSPs to achieve higher profits, command premium pricing, and stand out from the competition [10][21][63][30] .

  • Premium Pricing and Higher Margins:

    • Specialized MSPs report profit margins that are up to 30% higher than their generalist competitors [64][63] .

    • They can command a 10-20% price premium, with premiums reaching as high as 25-35% in high-compliance verticals like healthcare [1][64][63][32] .

    • This is reflected in per-user pricing, which might be $100-$250/month in standard markets but can range from $200-$400+/month in regulated verticals like finance and healthcare [38] .

  • Market Differentiation and Growth:

    • The most prominent verticals for specialized MSPs are healthcare (28% of specialized revenue), financial services (18%), and manufacturing (11%) [51] . Other successful verticals include legal, non-profits, accounting, and retail [31][49][65] .

    • Focusing on a niche allows MSPs to build deep domain expertise (e.g., HIPAA in healthcare), which builds trust, client loyalty, and shortens sales cycles [1][64][37][30] .

    • This strategy delivers tangible growth, with leading MSPs focused on vertical markets seeing their annual recurring revenue grow by 11% in 2024 [36][32] .
6. The Emergence of AI Governance as a Service

As businesses rapidly adopt AI, a critical need for governance has emerged to manage the associated risks related to data privacy, compliance, and ethics [20][66] . This presents a significant, high-margin opportunity for MSPs to create new recurring revenue streams by offering AI governance services, elevating their role to that of a trusted strategic advisor [4][9][67][68] .

  • Core Components of an AI Governance Service Offering:

    • AI Readiness and Risk Assessments: Evaluate a client’s environment, data quality, and security posture to identify AI use cases, assess risks (including “shadow AI”), and develop a strategic adoption roadmap [21][69][70][67][53] .

    • AI Usage and Security Policy Development: Create and implement tailored AI policies defining approved tools, acceptable use, data handling rules, and ethical guidelines to ensure safe and compliant adoption [10][68][71][30] .

    • Compliance-as-a-Service (CaaS): Help clients navigate the complex web of AI regulations like the EU AI Act by providing ongoing compliance monitoring, documentation, and reporting [9][19][42][72] .

    • AI Auditing and Ongoing Monitoring: Provide continuous auditing of AI models for bias, fairness, and performance drift, and monitor systems for security threats like prompt injection and data poisoning [31][23][24][71][39][73] .

    • AI Training and Adoption Programs: Offer training for executives and end-users on how to use AI tools effectively, securely, and responsibly, including prompt engineering and validating AI-generated content [10][21][74] .

  • Essential Frameworks for AI Governance:

    • NIST AI Risk Management Framework (AI RMF): A voluntary framework that provides a structured approach for managing AI risks, organized around four functions: Govern, Map, Measure, and Manage [36][37][75][76] . MSPs can use this to guide client conversations and build risk remediation roadmaps [38][77] .

    • ISO/IEC 42001: An international standard for establishing and maintaining an AI Management System, which is becoming a key requirement in enterprise contracts [9][78][63][79] . MSPs can offer readiness assessments and implementation consulting for certification [80][81] .

    • EU AI Act: The first major binding AI regulation, it classifies AI systems by risk level [68][82] . MSPs can offer services to inventory AI tools and monitor transparency obligations, turning a regulatory burden into a recurring revenue opportunity [68][73] .

  • Best Practices for Comprehensive AI Governance:

    • Data Privacy and Security: Establish clear data governance policies for data classification, access controls, and encryption [33][19][83][50] . Implement Data Loss Prevention (DLP) to prevent sensitive data from being leaked to public AI tools [66][30][44] .

    • Model Transparency and Bias Mitigation: Implement Explainable AI (XAI) tools to make AI decisions understandable [31] . Regularly audit models and training data for bias [31][84] . Thoroughly document model design, data sources, and performance for auditability [85][86] .

    • Ethical Usage and Human Oversight: Maintain a “human in the loop” for critical decisions to ensure ethical outcomes and prevent errors [33][28][71][82] . Work with clients to define ethical AI principles centered on fairness, accountability, and transparency [31][87][88] .
7. Strategic Recommendations for MSPs

Based on the market analysis, MSPs should consider the following strategic actions to capitalize on growth opportunities:

  • Financial Strategy: Build a High-Valuation Revenue Model.

    • Aggressively shift from project work to a recurring revenue model, aiming for over 85% MRR to command the highest valuation multiples [4][11] .

    • Prioritize securing long-term contracts (36+ months) to increase valuation by an additional 10-20% [19] .

  • Go-to-Market Strategy: Specialize and Offer High-Value Services.

    • Pursue vertical specialization in a high-demand industry like healthcare or finance to achieve premium pricing and higher margins [10][64][63] .

    • Develop and package AI Governance as a Service to create a new, high-margin recurring revenue stream and position the MSP as a strategic advisor [28][67][68][89] .

    • Integrate AI governance into existing vCIO, security, and compliance offerings to provide a holistic solution [68][16][67] .

  • Technology & Partnership Strategy: Master the AI-Driven Ecosystem.

    • Capitalize on New Financial Incentives: Actively align with new vendor incentive structures, such as AWS’s cash benefits, Google’s outcome-based rewards, and ServiceNow’s revamped MDF, to boost profitability [3][18][7][43][45][46][47] .

    • Build and Market AI Specializations: Achieve formal vendor competencies like the AWS Agentic AI Competency and leverage vendor funds (e.g., Google’s $750M fund) to build and deploy AI solutions [5][6][52][45] .

    • Invest in AI Governance Expertise: Build in-house expertise on key frameworks like the NIST AI RMF and ISO 42001 [77][79] . Invest in training and tools to deliver AI security and compliance services effectively [38][39][90] .

    • Leverage Vendor AI for Internal Efficiency: Use the AI capabilities embedded into vendor partner portals to automate administrative tasks, reduce overhead, and free up resources for high-value client work [18][33][56][13][91] .

Executive Summary
  • Purpose: This report provides a strategic analysis of the global Managed Service Provider (MSP) market, detailing market projections to 2030, financial valuation metrics, and the impact of key trends like AI, market consolidation, and the emergence of AI governance.

  • Key Findings: The global MSP market is on a significant upward trajectory, projected to reach $731 billion by 2030 [1][19][25] . The market is being reshaped by several powerful forces:

    1. Market Consolidation: A high rate of M&A is driving “platformization” as clients seek fewer, more integrated providers [3][4][30][32] .

    2. The AI Revolution: AI is evolving from an efficiency tool to the backbone of service delivery, enabling a proactive and predictive service model and creating new revenue opportunities [1][27][49][65] .

    3. The Emergence of AI Governance: The rapid adoption of AI has created a critical need for governance, presenting a new, high-margin service opportunity for MSPs to guide clients on data privacy, compliance, and ethical usage [4][20][9][67] .

    4. Valuation Imperatives: Market valuation remains intrinsically linked to the percentage of Monthly Recurring Revenue (MRR); MSPs with 85%+ MRR can command premium EBITDA multiples of 10x-15x [4] .
  • Strategic Recommendations: To thrive, MSPs must build a high-quality recurring revenue base (>85% MRR), pursue deep vertical specialization, and critically, develop and offer comprehensive AI governance services [28][67][68] . This requires mastering new AI-driven vendor ecosystems, building expertise in frameworks like the NIST AI RMF, and capitalizing on new financial incentives [4][51][64][63][77][43][45][46] .

  • Conclusion: The MSP market is in a dynamic and sustained growth phase. Success is no longer just about managing technology; it’s about building a predictable, specialized, and advisory-led business model. MSPs that master the interplay of recurring revenue, deep vertical expertise, and strategic leadership in AI governance will be the definitive market leaders of the next decade.

One Edit Away From Digital Oblivion

image

There is a special kind of fear that only appears after you press save on a Markdown file and the entire publishing pipeline falls over.

Not a dramatic fear. Not screaming in the street. More the quiet, professional terror of staring at a screen thinking, “I only changed one line.”

That is the funny thing about modern work. We talk about transformation, automation and AI as if the future is floating gracefully above us. Then a missing bracket, a badly indented bullet, or one heroic colon in the wrong place reminds everyone that civilisation is still held together by plain text and hope.

The smallest change can have the loudest voice

I like Markdown. It is simple. It is readable. It keeps content close to the person writing it rather than burying it under layers of formatting gymnastics. A good Markdown file feels honest. What you see is almost what you get.

Almost.

Because one tiny edit can turn a neat document into a crime scene. A table stops rendering. A link eats the next paragraph. A heading becomes normal text. Suddenly the document that looked perfectly sensible in your editor appears in SharePoint like it has had a hard weekend.

This is where a lot of organisations get caught. They assume simple files mean simple risk. They do not. A Markdown file can be part of a blog, a knowledge base, a GitHub repository, an internal procedure, a training handout, or a client-facing instruction set. If that file drives a process, then the little typo is no longer little. It has been promoted.

Copilot is useful, but it is not a seatbelt for carelessness

This is also where Copilot changes the conversation in a useful way. I can paste a Markdown section into Copilot in Word or ask Copilot in Teams to review a draft before I send it around. I can ask it to spot broken structure, unclear steps, inconsistent headings, or a table that looks ready to start a small fire.

That does not remove responsibility. It just gives me another set of eyes before I publish something that makes future me question past me’s life choices.

The real benefit is not that Copilot makes the edit for me. The benefit is that it slows the moment down just enough for me to think. Is this still clear? Did I break the flow? Does the document still say what I intended? Have I just created a support ticket disguised as punctuation?

That last one matters.

Version history is cheaper than regret

The sensible answer is boring, which is usually how you know it works. Keep important files in SharePoint or OneDrive so version history is available. Use Teams to discuss changes where the people affected can see the conversation. If the document matters, do not treat it like a disposable note on the side of your monitor.

For MSPs and small businesses, this is not academic. Your documentation is part of your service delivery. A password reset process, onboarding checklist, security exception register, or client build guide can all live as ordinary files. If someone “just fixes a sentence” and breaks the meaning, the cost may not appear until someone follows the bad instruction perfectly.

That is how documentation gets dangerous. It does not need to be malicious. It just needs to be confidently wrong.

So yes, we may all be one edit away from Markdown oblivion. But we are also one review, one version history check, one Copilot pass, or one quick peer glance away from avoiding it.

The lesson is simple. Respect the little files. They know where the bodies are buried.

New Microsoft image model

I have a standard image prompt that I use to test Ai models. The previous iteration with MAI-Image-2.5-Flash and MAI-Image-2.5 is here:

https://blog.ciaops.com/2026/06/04/latest-microsoft-image-models/

Before that with MAI-Image-1.5 and Flux.2 Flex is here:

https://blog.ciaops.com/2026/05/16/copilot-image-generation-in-powerpoint/

the previous attempts:

https://blog.ciaops.com/2026/05/05/revisiting-copilot-image-generation-analysis/

and the first attempt:

https://blog.ciaops.com/2026/03/07/image-generation-analysis/

Microsoft has just released a new models and here is what I got when I used them:

MAI-Image-2.5-Pro

MAI_62dbc50ed84cdf44

It will be soon available across Microsoft 365 services and desktop apps. You can read more about the new models here:

https://microsoft.ai/news/introducing-mai-image-2-5-pro-and-mai-voice-2-flash/

The Bystander Effect Is Quietly Killing Your Marketing

image

There’s a famous bit of psychology that explains why a person can collapse on a busy footpath and twenty people walk past. It’s called the bystander effect. When responsibility is spread across a crowd, everyone assumes someone else will step in — so nobody does. The more people present, the less likely any single one of them acts.

I’ve come to believe the same thing happens in marketing, and most of us never notice it. We think the problem is that people are rejecting us. Usually they’re not. They’re just standing in the crowd, assuming the message was meant for the person next to them.

“Everyone” Is Nobody

When you write an email, a newsletter, or a webinar invitation addressed to everyone, you’ve accidentally recreated that footpath. The reader scans it, decides — without much thought — that it’s aimed at some other, more relevant person, and moves on. They don’t unsubscribe. They don’t send an angry reply. They simply file you under “not for me” and get back to their day.

That quiet non-decision is far more dangerous than a flat “no”. A rejection at least tells you the message landed. The bystander never even picks up the phone. You walk away thinking the offer was weak, when really the offer was fine — it just never felt personal enough for anyone to claim it.

I see this constantly with MSPs marketing to small business. We send a generic “we can help with your IT” message to a list of three hundred contacts and wonder why two people reply. The content isn’t the issue. The aim is. Three hundred people each assumed we were really talking to one of the other 299.

First Aid Trainers Got There First

Anyone who’s done a first aid course has been taught the fix already. When you’re standing over someone who needs help, you don’t shout “somebody call an ambulance” to the crowd. You point at one specific person — “you, in the blue jacket, call triple zero now.” The instant that individual realises they’ve been singled out, they move.

That’s the whole game. The moment a person understands you are talking to them, the bystander effect collapses and action becomes possible. Marketing is no different. The job isn’t to reach more people — it’s to make each person feel seen.

Naming the Person, Not the Crowd

So how do you point at the blue jacket without writing three hundred individual emails? This is where I think the tools we already pay for earn their keep.

Most MSPs sit on a goldmine of context they never use. You know which clients are still on ageing hardware, which ones asked about security last quarter, which ones have a renewal coming. That detail is scattered across Outlook threads, meeting notes, and a CRM nobody opens. The work of pulling it together used to be the reason we defaulted to “Dear valued customer”. It isn’t anymore.

I’ll draft a campaign in Word and ask Copilot to rewrite the same core message for three distinct groups — manufacturers worried about downtime, professional services worried about compliance, retailers worried about card data. Three versions in the time it used to take to write one bland one. Each reader recognises their own world in the words, and the bystander reflex never gets a chance to kick in.

Copilot in Outlook does the same thing one conversation at a time. Before I reply to a prospect, I can have it summarise everything we’ve ever discussed and surface the one concern they keep raising. The reply then opens with their problem, in their language — not my service menu. That’s the digital version of pointing across the room and saying the person’s name.

Even your segmentation gets easier. I’ll drop a client export into Excel and let Copilot group accounts by industry, size, or last contact, so the list I’m writing to is genuinely a room of similar people rather than a faceless mob. The narrower the room, the easier it is to talk to everyone in it as if they were one person.

One “Yes, You” Away

The shift here is small but it changes everything. Stop trying to be relevant to a crowd. Be unmistakably relevant to one type of person, and let them know you mean them.

Your next client is probably already on your list. They’re not ignoring you out of disinterest — they’re waiting in the crowd, quietly assuming the invitation belongs to someone else. The work isn’t louder marketing or a bigger list. It’s removing the doubt about who you’re speaking to.

Point at the blue jacket. Use the context you already have, the tools you already pay for, and address the person directly. You might be one moment of genuine recognition away from the conversation you’ve been chasing all quarter.

When the Fix Stops Being a Fix: Troubleshooting in the Age of Probabilistic IT

image

For most of my working life, troubleshooting an SMB environment was a hunt for a single, knowable cause. Something was broken, and somewhere there was a reason. A permission was wrong. A DNS record pointed at the wrong place. A service had stopped. You worked the chain backwards, found the link that had failed, fixed it, and the problem went away. The same input produced the same output, every time. That was the quiet contract underneath everything we did. IT was deterministic, and our whole troubleshooting craft was built on that assumption.

That contract is now breaking, and AI is the reason. The more our clients lean on tools like Microsoft 365 Copilot, the more we find ourselves chasing problems that don’t have a single cause and don’t behave the same way twice. We’ve spent decades learning to solve deterministic problems. We’re now being asked to solve probabilistic ones, and most MSPs haven’t noticed the ground shift under their feet.

“It Worked Yesterday” Now Means Something Different

Here’s the scenario I keep running into. A client calls because Copilot gave them a wrong answer. It summarised a meeting and missed the one decision that mattered. Or it drafted a reply in Outlook that referenced a document the user swears they never mentioned. Yesterday it was brilliant. Today it’s confidently wrong. Nothing changed on your side. No update shipped. No setting moved.

Under the old model, “it worked yesterday and not today” was a clue. It told you something had changed, and you went looking for the change. With AI in the mix, that same sentence tells you almost nothing. Large language models are probabilistic by design. The same prompt can produce a different response on Tuesday than it did on Monday, and that’s not a bug you can ticket your way out of. It’s how the technology actually works.

So when a client reports that “Copilot is broken,” your first instinct — find what changed — quietly fails you. There may be nothing to find. The behaviour you’re chasing isn’t a fault in the wiring. It’s variance in the output. And variance doesn’t sit still long enough to be caught with the tools we’ve always used.

The Cause Isn’t Always in the System

The harder adjustment is accepting that the problem often isn’t technical at all. When Copilot returns a poor result, the cause is frequently the question, not the code. A vague prompt, missing context, the wrong document open in the background, permissions that quietly scope what Copilot can and can’t see — these shape the answer far more than any registry key ever did.

I had a client convinced Copilot in Teams couldn’t read their project files. The real issue was that the files lived in a SharePoint site the user didn’t have access to, so Copilot, correctly, never touched them. The system was working exactly as designed. The human’s mental model was the thing that was broken. There was no error in any log, because there was no error. Try writing that up in a standard ticket resolution.

This is the part that unsettles seasoned engineers. We are trained to distrust “user error” as a lazy diagnosis. But with AI, the boundary between the tool and the person using it has genuinely blurred. The quality of what Copilot produces is now a function of context, phrasing, data access, and the user’s own clarity of thought. Half of real-world “AI problems” are actually grounding problems — Copilot simply wasn’t given the right material to work with. You can’t fix that with a script. You fix it by teaching.

From Repair to Probability Management

So what does troubleshooting look like when certainty is gone? It looks less like repair and more like managing probability. Instead of asking “what’s broken,” you start asking “why is this likely happening, and how do we make the good outcome more likely next time.”

That changes the work in practical ways. You start checking what Copilot can actually see — the SharePoint and OneDrive permissions, the Purview sensitivity labels, the data the user assumes is in scope but isn’t. You look at how the question was asked, not just what the system returned. You reproduce the issue several times, because one bad answer is an anecdote, not a pattern. You document tendencies rather than root causes, because a tendency is often the most honest thing you can record.

It also changes what you sell. The deterministic world rewarded MSPs who could find and fix. The probabilistic world rewards MSPs who can guide, set expectations, and shape how AI gets used across a client’s day. The value moves from the repair to the relationship.

Sitting With Uncertainty

None of this means our old skills are worthless. Plenty of SMB problems are still gloriously deterministic — a licence didn’t assign, a mailbox didn’t migrate, a Conditional Access policy locked someone out. Find it, fix it, move on. That work isn’t going anywhere.

But a growing slice of what lands in your queue now has no clean answer, and pretending otherwise only frustrates everyone. The MSPs who’ll do well from here are the ones who can hold two modes at once — the precision of the engineer and the judgement of an advisor who’s comfortable saying “here’s what’s most likely, and here’s how we improve the odds.” Learning to sit with that uncertainty, rather than fight it, might be the most valuable troubleshooting skill of the next decade. I’m still getting used to it myself.

The Robots Didn’t Kill Sales. Relevance Did.

image

Let me be upfront: this isn’t a post about watching other people lose their footing. I’ve seen it happen — quietly, without announcement — but pointing at cautionary tales reads as smugness, and it doesn’t help anyone. What does help is understanding the mechanism. Because the mechanism doesn’t care whose career it applies to, including mine.

The Slow Fade

When AI started making headlines, a certain explanation took hold in IT circles: the robots came and took over. Clients automated their way out of needing you. Algorithms undercut your value. Technology made your expertise redundant overnight.

I’ve sat in rooms where that story got told with great conviction. And I understand the appeal — it’s clean, it’s external, and it lets everyone off the hook.

But I don’t think it’s the real story. At least not for most people.

What I’ve actually watched happen is something quieter, and frankly more avoidable. Skilled people — genuinely skilled, with real depth — stopping. Stopping posting, stopping presenting, stopping sharing what they were learning. Getting busy, or burned out, or simply assuming that reputation would carry. And then discovering, over months rather than days, that the market had quietly moved on.

The market doesn’t issue a formal notice. It just stops calling.

Presence Is a Practice, Not a Trophy

Here’s the thing about credibility in professional services: it behaves more like a subscription than an asset. You don’t acquire it once and keep it indefinitely. You maintain it — week by week, post by post, conversation by conversation — by staying present in the space where your clients and prospects are paying attention.

The people I see holding their ground right now aren’t necessarily the most technically brilliant. What they share is a habit of doing something worth knowing about and then talking about it. They’ve been working through how Copilot in Teams handles a fast-paced client meeting — the kind where the conversation moves faster than anyone can type — and they write up what actually happened. Not a polished case study. A genuine account of what worked, what surprised them, what the documentation didn’t quite prepare them for.

That’s what gets shared. That’s what gets remembered. That’s what gets you back into the conversation when a prospect is deciding who to ring.

The alternative — doing excellent work quietly, trusting that results will speak for themselves — used to be viable. It worked when markets were smaller and word of mouth moved reliably. I’m not sure it works the same way now. Attention spans are shorter, competition is louder, and the gap between the visible and the invisible keeps widening faster than most people expect.

The AI Angle Nobody Wants to Admit

Here’s where I’ll give the “robots did it” crowd a partial concession: the shift toward AI tools has accelerated everything. But not quite in the way most people mean.

What it’s accelerated is the gap between people who are actively inside the change and people who are observing it from a safe distance. Clients are asking questions about Copilot, about automation, about what Microsoft 365 actually means for how their team works day to day. The people who get those calls are the ones who have been publicly working through those questions — who’ve shared what Microsoft 365 Business Premium looks like in practice for a 40-person firm, or explained what Copilot in Outlook actually does to a full inbox on a Monday morning, drawing from real client experience rather than a vendor one-pager.

The others get found too. Just by someone else.

So if you’re waiting until you feel fully prepared to share — waiting for the perfect case study, the right moment, enough certainty — I’d gently push back on that. The market is not waiting with you. It’s watching whoever is showing up.

The Account Runs Down

I think of staying relevant the way I think about any recurring obligation: you can miss a payment here or there without immediate consequence, but the balance erodes. And by the time you notice the problem, you’re already working against a deficit. Rebuilding takes longer than maintaining ever did.

The fix is not complicated, even if it takes discipline. Engage with something genuinely new — a client challenge, a corner of the Microsoft 365 stack you haven’t properly explored, a question your market keeps circling. Arrive at a real view. Then share it, in your own voice, without waiting until it’s polished enough to be mistaken for marketing material.

Work on things that matter. Then put them where the people who should know can find them.

That’s the whole playbook.

The careers that fade aren’t usually the ones that got disrupted by technology. They’re the ones that went quiet. The ones that assumed the work would carry its own story forward.

It doesn’t. You have to carry it.

Don’t go quiet.

AI Governance Starts Before Copilot Does

image

Most AI conversations with business owners start in the wrong place. They ask whether Microsoft 365 Copilot is worth buying. I think the better question is whether the business is ready for what Copilot will reveal.

I have seen the same pattern often enough now. A client gets excited about Copilot in Outlook, Teams, Word and Excel. Someone wants meeting summaries. Someone else wants faster proposals. The owner wants staff to stop using random public AI tools with company data. All fair enough. But then we look underneath and find the real issue: years of loose permissions, old Teams, forgotten SharePoint sites, stale guests and no clear policy on what staff should or should not ask an AI system to do.

That is where AI governance starts.

Governance is not a document no one reads

A policy is useful, but only if it changes behaviour. If the policy says “use AI responsibly” and nothing else, it has failed before it starts.

For Copilot, I want plain rules. What data can be used? What data must not be used? When does a human need to review the answer? Who owns the final output? What happens if Copilot surfaces something the user did not expect to see?

That last question matters. Copilot does not need to break into your tenant to create a problem. If a user already has access to a file, Copilot may be able to use that file as part of an answer. The silent risk is not Copilot ignoring permissions. The risk is that the permissions were never cleaned up in the first place.

The technology follows the tenant

This is why I keep coming back to the Microsoft 365 basics. Entra ID, MFA, Conditional Access, SharePoint permissions, Teams lifecycle, Purview sensitivity labels and Data Loss Prevention are not side issues. They are the foundation.

If identity is weak, every AI answer sits on a weak account. If SharePoint is overshared, Copilot can make that oversharing easier to discover. If labels do not exist, users have no clear signal that a document is sensitive. If DLP is sitting in test mode forever, the business has a policy theatre problem, not a protection model.

I would rather see a small, controlled Copilot pilot in a tidy tenant than a broad deployment in a messy one. Start with a few users. Pick real scenarios. Meeting follow-ups in Teams. Draft replies in Outlook. Summaries from known SharePoint libraries. Then watch what happens. What worked? What surprised people? What data did Copilot find that no one expected?

Guardrails should be practical

The best guardrails are boring. That is a compliment.

Require MFA. Tighten external sharing. Review old guests. Publish simple sensitivity labels. Apply DLP where it matters. Use Restricted SharePoint Search where the content estate needs time to be cleaned up. Train users to verify answers before sending anything to a client. Make it normal to say, “Copilot drafted this, but I approved it.”

That is not anti-AI. That is responsible adoption.

The businesses that do this well will not be the ones with the flashiest prompts. They will be the ones that treat Copilot as part of their operating model. Policy, security, people and process all moving together.

My view is simple. Do not start with the licence. Start with the trust model. If you can trust the identity, the data, the permissions and the controls, then Copilot becomes much easier to use with confidence.

AI governance is not there to slow the business down. It is there so the business can move without pretending the risks are someone else’s problem.

When the Product Is the Answer

MAI_d2738865c0ceccd4

A few years ago, I paid real money for an online course about something I could have googled. Not because the information wasn’t out there — it was — but because someone had packaged it up into a tidy sequence, with a PDF checklist at the end. That felt like value. I’d trade some cash for the shortcut.

I’m not sure that trade still makes sense.

There’s a question worth sitting with if you sell courses, run a newsletter, or operate any kind of advice business: what exactly are you selling? If the core of your offer is “I know how to do X, and for a fee, I’ll explain it to you,” then you’re competing — right now, today — with a chat interface that will do the same thing for free, in plain language, at any hour, and answer every follow-up question without sighing.

That’s not pessimism. It’s just arithmetic.

The Commodity Shift

The thing is, knowledge transfer was already becoming cheaper. YouTube, forums, documentation sites — the raw material was free or nearly so long before any of us had heard of a large language model. What the structured course or the curated newsletter offered was organisation and trust. Someone had done the sorting for you.

AI has now taken that arrangement apart. Ask Copilot in Microsoft 365 how to build a pivot table, how to structure a client proposal, how to read a balance sheet, or how to write a meeting agenda — and you’ll get a clear, accurate, step-by-step answer in seconds. It knows context. It remembers what you asked two prompts ago. It adjusts when you say “that’s too complicated, simplify it.” The experience of learning from it is genuinely conversational in a way that a pre-recorded video module is not.

For anyone whose business rests primarily on the instruction layer — here’s how to do the thing — that shift deserves honest attention.

What Doesn’t Commoditise

I don’t think this means the advice economy is finished. But I do think it clarifies what was always the actual product, beneath the packaging.

What an AI won’t give you is accountability. It won’t check whether you actually implemented what it told you, or notice that you’ve been stuck on step three for six weeks because there’s something uncomfortable underneath the technical question. A good advisor, coach, or community does that.

It also won’t give you judgement built from real exposure to your specific industry, your clients, your context. I can ask Copilot about pricing strategy for an MSP, and I’ll get a reasonable answer. But the answer from someone who has personally renegotiated forty MSP contracts and remembers what went wrong — that carries a different weight.

The value proposition that survives isn’t “I’ll explain the concept.” It’s “I’ve seen this pattern before, here’s what it usually means, and here’s what I’d actually do.” That’s the part that takes years to earn and can’t be scraped.

What I’m Watching

My own approach has shifted. The things I now put into writing — whether that’s a post, a session, or anything structured — I try to hold to a higher bar than “here’s how to do X.” Anyone can get that from Copilot. What I’m aiming for is the observation behind the explanation: the why, the tradeoff, the thing that only becomes clear once you’ve been surprised by the edge case.

The knowledge economy isn’t dying. It’s just shedding the parts that were never really the point.