HOME

What Are We Really Paying for When Technology Just Works?

Nov 17, 2026By IT & Cybersecurity Strategist
IT & Cybersecurity Strategist

On November 12 and 13, 2026, a widespread Microsoft 365 outage disrupted email and other connected services for businesses and organizations around the world.

For some, it meant being unable to access their inboxes. For others, delayed communications and interruptions to everyday work.

The frustration was understandable. When businesses depend on technology, even a temporary disruption can have serious consequences.

But the incident also raises a question that rarely gets much attention when everything is working.

We notice immediately when technology fails. How often do we consider everything required to keep it running the rest of the time?

And do we fully understand what we're paying for when technology simply works?

The Costs That Never Really Disappeared

There was a time when businesses had to own much of the infrastructure behind their technology.

Servers needed purchasing, software required upgrades, equipment needed maintenance, and eventually everything had to be replaced.

Today, many businesses access those same capabilities through subscriptions.

But here's an important distinction.

Moving technology into the cloud didn't eliminate infrastructure costs. It changed who pays for and manages them.

The servers didn't disappear. Neither did the people maintaining them, the equipment replacements or the continuous investment required to keep everything operating.

Those expenses became part of the service businesses now pay for through recurring subscriptions.

Instead of managing every component themselves, businesses pay for access to technology that someone else operates and maintains.

That's a significant change, and one that's easy to overlook.

What Predictable Costs Actually Mean

Subscription-based technology has also changed how businesses budget.

Rather than making substantial upfront investments in infrastructure, they can often access sophisticated services through predictable monthly or annual payments.

Maintenance, platform updates and underlying equipment replacement become the provider's responsibility.

For businesses, that can mean fewer large capital purchases, less infrastructure to maintain and easier financial planning.

But predictable doesn't necessarily mean cheaper.

Subscription prices can increase. Additional capabilities may cost extra. Businesses still need administration, support and sometimes specialized expertise.

Over several years, recurring payments can become a substantial expense.

The advantage isn't automatically spending less. It's having a different way of distributing costs, responsibilities and financial uncertainty.

And whether that arrangement represents better value depends on the business.

What Does Five Years of Service Really Represent?

Consider what five years of using a cloud-based platform actually involves.

Employees communicate, collaborate, share information and complete their daily work.

Meanwhile, the provider maintains infrastructure, replaces equipment, applies updates and develops new capabilities.

Much of that work happens without customers needing to manage the underlying systems themselves.

Then a major outage occurs, and attention understandably shifts toward what went wrong.

But five years of technology service represents more than the number of hours a platform was available. It also reflects the infrastructure investments, maintenance responsibilities and ongoing improvements included in the service.

That doesn't excuse an outage.

A disruption lasting only a few hours can have serious financial or operational consequences, depending on when it happens and what services are affected.

And a strong availability record doesn't automatically compensate for a particularly damaging failure.

The point isn't to overlook the disruption. It's to recognize that neither the outage nor the years of service tell the complete story on their own.

The Other Side of Convenience

The Microsoft outage also exposed something that doesn't always receive enough attention when businesses choose technology.

The same arrangement that removes much of the responsibility for operating infrastructure also limits how much control customers have when that infrastructure fails.

When a provider experiences a major disruption, customers may have little ability to restore the affected service themselves.

And that loss of control extends beyond outages.

Subscription prices can change. Features can be modified or discontinued. Providers can make decisions that affect businesses without giving them much influence over those changes.

Switching providers isn't necessarily straightforward either.

Years of accumulated information, established workflows and employee familiarity can make moving to another platform expensive and disruptive.

Owning infrastructure provides a different degree of control, but it also means accepting responsibility for maintenance, investment, upgrades and failures.

Neither approach eliminates risk.

The difference is how those responsibilities and risks are distributed.

Looking Beyond the Invoice and the Outage

When businesses evaluate technology, the conversation often begins with price.

How much does the subscription cost? What will we spend over five years? Would owning the infrastructure be more economical?

Those are reasonable questions.

But the answers require more than comparing invoices.

A meaningful comparison considers the total cost of delivering the service, the responsibilities involved, the capabilities available and the consequences when something goes wrong.

It also considers how much control the business wants to retain and what it is prepared to manage itself.

The Microsoft outage deserves scrutiny. Organizations affected by it have every reason to expect reliability, transparency and accountability.

But it also provides an opportunity to examine the larger relationship businesses have developed with technology.

Over time, we've moved from owning and maintaining many of the systems we depend on to accessing them as services.

That shift has brought convenience, predictable expenses and access to capabilities that once required considerable investment.

It has also introduced dependencies, recurring financial commitments and limitations on control.

A major outage makes some of those limitations impossible to ignore.

The years between outages reveal the responsibilities, investment and complexity that businesses no longer have to manage directly.

Both deserve consideration.

Perhaps the real question isn't whether modern technology is worth what we pay for it, but whether we fully understand what we're gaining, what we're giving up, and what it would take to do things differently.