Notifications
Clear all
Topic starter
23/06/2026 9:22 pm
TL;DR: High-growth MSPs are not avoiding complexity but operationalising it, with 22% growing revenue by more than 20%, 70% supporting devices beyond Windows, and 75% managing more SaaS applications, according to JumpCloud’s webinar-based post. The underlying signal is that scale now depends on policy, automation, and governance across mixed estates, not stack simplification.
NHIMG editorial — based on content published by JumpCloud: High-growth MSPs are thriving in complexity
By the numbers:
- 22%, rly a quarter, 22%, of MSPs surveyed grew their revenue by more than 20% in the past year.
- 70% are supporting devices beyond Windows.
- 75% are managing more Software-as-a-Service applications.
Questions worth separating out
Q: How should MSPs govern access across mixed device environments?
A: MSPs should define a common policy baseline for every supported device class, then layer exceptions only where business need is explicit.
Q: Why do SaaS sprawl and shadow IT create identity risk for MSPs?
A: Because each unsanctioned application creates its own authentication path, access entitlement set, and lifecycle burden.
Q: What do high-growth MSPs get right about automation?
A: They use automation to make policy execution repeatable, not to replace governance.
Practitioner guidance
- Standardise policy baselines across all managed endpoints Define a single control baseline for Windows, macOS, Linux, iOS, and Android, then document where exceptions are allowed and who approves them.
- Automate the controls that fail under ticket-based handling Prioritise workflows for patching, configuration enforcement, compliance checks, and recurring access tasks so the same policy executes the same way every time.
- Bind shadow IT discovery to identity lifecycle processes Map unmanaged SaaS and AI-enabled apps to owners, access paths, and offboarding steps so discovery is followed by entitlement cleanup.
What's in the full article
JumpCloud's full blog covers the operational detail this post intentionally leaves for the source:
- The survey framing behind the 2025 MSP Performance Report and how the questions were structured
- The practical examples of policy standardisation across Windows, macOS, Linux, and mobile estates
- The vendor's operational guidance on uncovering and managing shadow IT and AI-driven SaaS usage
- The closing implementation advice on auditing stacks, consolidating tools, and planning AI agent governance
👉 Read JumpCloud's analysis of high-growth MSP operations and complexity →
MSP growth and complexity: what changes for identity teams?
Explore further
25/06/2026 2:39 am
Complexity is now the operating condition, not the exception. The webinar’s core finding is that high-growth MSPs are succeeding by building governance around diversity instead of trying to eliminate it. That matters because hybrid devices, broader SaaS usage, and client-specific requirements are the baseline environment now, not temporary noise. The practitioner conclusion is that scale comes from control design, not from architectural nostalgia.
A few things that frame the scale:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security.
A question worth separating out:
Q: How should organisations treat AI agents in identity governance?
A: They should treat AI agents as identities with ownership, access limits, monitoring, and revocation requirements. If an agent can act on systems or data, its access should be lifecycle-managed like any other non-human identity. The key is to prevent privileges from persisting after the task or service need has ended.
👉 Read our full editorial: Managed service provider growth now depends on complexity
