When Did Technology Choice Become an All-or-Nothing Decision?

Written by Rajat Bhargava on November 20, 2026

Connect

Editor’s note: This article was originally published by JumpCloud CEO Rajat Bhargava on his LinkedIn. Follow him to keep up with future posts, and consider subscribing to his newsletter, Machine Speed.


The recent Microsoft outage prompted a lot of discussion about resilience, including a few thoughts I shared here on LinkedIn. But the conversation has stayed with me for a different reason: We’ve made it remarkably difficult for businesses to change their minds about technology.

Most businesses don’t set out to become dependent on a single technology provider. They get there one reasonable decision at a time.

A company chooses a productivity suite that works well for its employees. It adds identity management because it’s convenient to use the same provider. Security tools follow, then device management, collaboration applications, and increasingly, AI capabilities. Each decision makes sense on its own. The products work together, procurement is simpler, and IT has fewer vendors to manage.

Then, a few years later, the business wants to make a change.

Maybe a better solution has emerged. Maybe the company is expanding into new markets, acquiring another business, or rethinking its approach to security. What should be a relatively straightforward technology decision becomes a much bigger undertaking because so many systems depend on one another and perhaps, even, depend on each other.

I’ve spent much of my career building technology businesses, and one thing I’ve learned is that the requirements you have today are rarely the requirements you’ll have five years from now. The ability to adapt is enormously valuable. Yet organizations routinely make technology decisions that limit that flexibility without fully recognizing the trade-off.

I think it’s time we reconsidered how much choice our technology strategies actually preserve.

Consolidation Has Benefits. So Does Independence.

There’s a reason organizations consolidate technology with large providers. Managing fewer vendors can reduce administrative overhead, simplify purchasing, and make it easier to connect systems. For IT teams with limited resources, those advantages are meaningful.

The problem begins when convenience becomes dependency.

Consider an organization that uses one provider for email, collaboration, identity, and device management. If the company wants to adopt a different identity solution, it may discover that authentication, access policies, device configurations, and application integrations are more closely connected than expected.

The technical work is only part of the challenge. There are contracts to consider, employees to train, processes to change, and risks to manage. Eventually, the perceived cost of making a change becomes so high that the organization stays with its existing approach, even when it no longer meets all its needs.

That’s an important distinction. A company should continue using a technology because it delivers value, not because leaving feels impossible.

And the answer isn’t necessarily to replace everything with a collection of independent products. Too much fragmentation creates its own problems, including higher costs, inconsistent security policies, and additional work for IT.

The goal should be an architecture that allows organizations to make deliberate choices about where integration is valuable and where independence is worth preserving.

AI Is Making Flexibility More Valuable

I believe this conversation becomes even more important as AI changes the technology landscape.

We’re still early in understanding how AI will reshape business operations. New models, applications, and autonomous agents are emerging quickly, and the capabilities organizations need are evolving alongside them.

A company might standardize on one AI platform today and discover a year from now that another provider offers a better solution for a particular workflow. Different teams may need different tools. Some applications will be built internally, while others will come from established software vendors or newer companies entering the market.

It’s difficult to predict which technologies will become essential. That’s precisely why organizations should be careful about building environments that make it unnecessarily hard to adopt them.

AI agents also introduce a new dimension to this challenge. As agents begin accessing applications, interacting with business data, and taking action on behalf of employees, organizations need a consistent way to manage their identities, permissions, and activity.

Those responsibilities shouldn’t depend entirely on which productivity suite or AI model a company happens to use.

Identity, access, and security need to provide a foundation that can accommodate new technologies as they emerge. Otherwise, businesses risk making their AI strategies dependent on decisions they made years before autonomous agents were even part of the conversation.

For business leaders, that flexibility has real value. It creates more room to experiment, adopt better capabilities, and respond to changing customer needs without continually rebuilding the underlying IT environment.

Modernization Doesn’t Have to Mean Starting Over

One of the biggest misconceptions about technology modernization is that organizations have to choose between keeping everything they have and replacing everything at once.

In reality, most businesses operate in environments that have developed over many years. They have applications employees rely on, investments that still deliver value, and systems that can’t be replaced overnight.

Those realities shouldn’t prevent them from making progress.

An organization might be satisfied with its existing productivity suite but want more flexibility in how it manages identities and devices. Another might need to support multiple operating systems or integrate technology from an acquisition. A third might want to introduce new AI capabilities without giving every agent broad access to existing systems.

These are opportunities to reconsider individual dependencies rather than overhaul the entire environment.

At JumpCloud, this philosophy has shaped what we’ve been building for years. We believe organizations should be able to choose the applications, operating systems, and productivity tools that work for them while managing identity, access, and devices through a unified platform.

That independence gives IT teams more control over how their environments evolve. It also means a business can retain the Microsoft services it values while making different choices in other areas.

Technology change will always involve planning and effort. But the architecture should make thoughtful change possible, not discourage it.

Technology Choice Is a Leadership Decision

It’s easy to treat technology architecture as something that belongs entirely to IT. But the consequences of those decisions extend well beyond the technology team.

The ability to integrate an acquisition, enter a new market, adopt an emerging technology, or respond to a changing security requirement can all depend on choices made years earlier.

CEOs and other business leaders don’t need to dictate which identity provider or device management platform their organizations use. They should, however, understand whether their technology strategy is creating flexibility or limiting it.

That means asking how difficult it would be to change a major provider, which systems share critical dependencies, and whether the organization can adopt new capabilities without disrupting everything around them.

There will always be good reasons to consolidate certain technologies. There will also be good reasons to keep others independent. The important thing is to make those decisions intentionally, with an understanding of what they mean for the future.

When we started JumpCloud, we believed businesses deserved more freedom in how they built and managed their IT environments. That conviction has only grown stronger as technology has become more central to nearly every business decision.

The next decade will bring changes we can’t fully anticipate, particularly as AI becomes part of everyday operations. The companies best positioned to take advantage of those changes won’t necessarily be the ones that committed most deeply to a single technology ecosystem.

They’ll be the ones that retained the freedom to evolve.

Technology should expand what a business can do next, not dictate what’s possible.


If you’re evaluating your dependencies, we put together a practical guide on the JumpCloud blog to help you realize you’re not as locked in as you may think. It walks through how to figure out where you still depend on Microsoft, what you can move in stages, and what makes sense to keep. Give it a read here.

Rajat Bhargava

Rajat Bhargava is an entrepreneur, investor, author, and CEO and co-founder of JumpCloud. An MIT graduate with over two decades of high-tech experience, Rajat is a ten-time entrepreneur with six exits including two IPOs and four trade sales.

Continue Learning with our Newsletter