Why enterprises are rethinking hybrid and multicloud

Cloud was supposed to simplify enterprise IT. For many organizations, it did, at first.

But years of migrations, acquisitions, SaaS adoption, application modernization, decentralized technology decisions, and rapid AI investment have created something more complicated.

According to Flexera's 2026 State of the Cloud Report, 73% of organizations now operate hybrid cloud environments. At the same time, estimated wasted cloud spend has risen to 29%, reversing a five-year downward trend.

The issue isn't necessarily that enterprises have adopted too much cloud.

It's that the technology environment surrounding cloud has become increasingly difficult to manage as one connected enterprise.

Today's organization may operate applications across multiple public clouds, private infrastructure, SaaS platforms, traditional data centers, branch locations, and edge environments. Different business units may use different platforms. Security teams may manage multiple sets of policies. IT teams may lack end-to-end visibility. And cloud costs can be distributed across providers, accounts, applications, and departments.

Now AI is adding another layer.

The result is an important shift in the cloud conversation.

For CIOs and technology leaders, the strategic question is no longer:

How much of our infrastructure should move to the cloud?

It is: How do we reduce complexity and extract more business value from the cloud environments we already have?

How did enterprise cloud environments become so complex?

Cloud complexity grows when organizations accumulate platforms, applications, infrastructure, security tools, and operating models faster than they can integrate and govern them.

In many cases, today's hybrid and multicloud environments were never designed as a single architecture. They evolved.

One business unit selected one cloud provider while another chose a different platform. An acquisition brought another technology stack into the organization.

Certain applications moved to the cloud while legacy workloads remained on-premises. SaaS adoption expanded outside centralized IT. Edge environments emerged to support operational requirements.

Individually, many of these decisions made sense.

Collectively, they created complexity.

This distinction matters because multicloud is sometimes presented as if organizations deliberately designed environments around multiple providers from the beginning. In reality, cloud complexity can also be the cumulative result of years of business and technology decisions.

Flexera's 2026 research notes that growing multicloud adoption can result from mergers, siloed application teams, and inherited architectures rather than deliberate strategy.

The challenge for technology leaders is therefore not simply managing multiple clouds.

It is turning an environment that evolved organically into an architecture that operates intentionally.

Hybrid cloud isn't the problem

The answer to cloud complexity is not necessarily consolidation into a single platform.

For many enterprises, hybrid infrastructure is the right operating model.

Applications have different requirements. Some workloads benefit from public cloud scalability. Others need to remain within private environments because of performance, security, regulatory, latency, or cost considerations. Operational technology and edge computing introduce additional requirements. Organizations may also want flexibility to avoid unnecessary dependence on a single provider.

Hybrid architecture allows enterprises to place workloads where they make the most sense.

IBM research has found that 71% of surveyed executives believe realizing the full potential of digital transformation is difficult without a solid hybrid cloud strategy. Yet only 27% of organizations surveyed demonstrated the characteristics IBM associated with advanced cloud transformation.

The implication is important:

Adopting hybrid cloud is not the same as successfully managing hybrid cloud.

The problem begins when environments become fragmented.

When cloud platforms, networks, applications, security controls, and data are managed independently, organizations can lose many of the benefits they expected cloud adoption to provide.

The objective should therefore not be eliminating hybrid infrastructure.

It should be eliminating unnecessary fragmentation within it.

The hidden costs of cloud complexity

Cloud costs are easy to see on an invoice.

The broader cost of cloud complexity is much harder to quantify.

It can appear as slower application performance, duplicated tools, unused resources, inconsistent security controls, longer troubleshooting cycles, integration challenges, or IT teams spending more time maintaining infrastructure than enabling innovation.

These costs tend to accumulate quietly.

1. Financial waste

The most obvious cost is underutilized or unnecessary cloud resources.

Organizations may pay for idle capacity, oversized instances, redundant services, forgotten development environments, unnecessary data storage, or workloads running in environments that no longer make financial sense.

As cloud environments expand, simply identifying that waste becomes harder.

Flexera reports that managing cloud spend remains a top challenge for 85% of organizations, even as FinOps practices become more mature.

AI makes this challenge even more significant because AI workloads can introduce highly variable compute, storage, and data-transfer requirements.

Cloud optimization is therefore evolving beyond reducing the monthly bill.

For technology leaders, the more useful question is:

Are we placing each workload in the environment that delivers the right combination of performance, resilience, security, and cost?

2. Operational complexity

Every additional environment creates something else IT must monitor, secure, integrate, troubleshoot, and maintain.

Different clouds may have different management interfaces, networking models, identity frameworks, security controls, billing structures, and operational tools.

Over time, organizations can accumulate an increasingly fragmented management layer.

When an application slows down, identifying the root cause may require teams to examine the application, cloud infrastructure, network, APIs, security controls, and external services across multiple platforms.

This increases operational overhead and can lengthen mean time to resolution.

The cost isn't just IT productivity.

When the affected application supports customer service, manufacturing, logistics, financial operations, or another critical function, infrastructure complexity becomes business risk.

3. Security and governance gaps

Cloud fragmentation can also make consistent security more difficult.

Different platforms may have different identity models, security configurations, access policies, monitoring tools, and compliance requirements.

Without centralized visibility and governance, misconfigurations and policy inconsistencies can be difficult to detect.

This becomes even more important as AI applications gain access to data and systems across multiple environments.

A fragmented cloud architecture can quickly become a fragmented security architecture.

For CIOs and CISOs, the objective should be to establish security and governance that follow the workload and data—not controls that stop at the boundary of a particular cloud provider.

4. Data fragmentation

Cloud complexity isn't limited to infrastructure.

It affects data as well.

Information may reside across SaaS platforms, cloud databases, legacy applications, data centers, edge systems, and multiple cloud providers.

When those environments are poorly integrated, organizations can struggle to create a consistent view of their data.

That has always created analytics challenges.

AI makes the problem harder to ignore.

AI systems need access to trusted, relevant, governed information. If data is fragmented across disconnected environments, organizations may have enormous amounts of information without being able to use it effectively.

In that sense, cloud complexity can become an AI-readiness problem.

5. Slower transformation

Perhaps the most consequential cost is also the hardest to see.

Complexity slows change.

When launching a new application requires navigating multiple infrastructure teams, security frameworks, integrations, network configurations, and cloud platforms, innovation becomes harder.

IT teams spend more time managing dependencies.

Projects take longer.

And the organization becomes less agile—the opposite of what cloud adoption was originally intended to achieve.

The cloud conversation is shifting from migration to optimization

For years, enterprise cloud strategies focused heavily on migration.

How many applications have moved?

How much infrastructure has been retired?

What percentage of workloads now operates in the cloud?

Those questions were appropriate during the first phase of cloud transformation.

They are no longer enough.

Many enterprises already have substantial cloud footprints. Their challenge now is determining whether those environments are delivering measurable business value.

That requires a different set of questions:

• Are workloads running in the right environments?
• Are cloud resources being used efficiently?
• Can IT see and manage the environment holistically?
• Can security policies be applied consistently?
• Can applications and data move securely across environments?
• Does the network provide the performance and resilience distributed applications require?
• Can the architecture accommodate AI and future workloads without adding another layer of complexity?

This represents the next phase of cloud maturity.

Cloud strategy is moving from migration to optimization, orchestration, and business value.

And that shift may ultimately require enterprises to rethink what "cloud-first" means.

Cloud-first should not mean cloud-only

Cloud-first strategies helped organizations accelerate adoption and move away from rigid infrastructure models.

But cloud-first can become counterproductive when interpreted as a requirement to place every workload in public cloud infrastructure regardless of business requirements.

The better principle is workload-right.

Each workload should operate in the environment that best meets its performance, latency, security, compliance, resilience, data, and economic requirements.

For one application, that may be public cloud.

For another, private cloud.

For another, an edge environment or existing data center.

And in some cases, organizations may determine that workloads previously moved to the cloud should be rebalanced or repatriated.

That is not necessarily a failure of cloud strategy.

It can be evidence of a more mature one.

The goal isn't maximizing cloud adoption.

The goal is creating an infrastructure environment that maximizes business value.

What should CIOs evaluate in a modern hybrid cloud strategy?

Technology leaders looking to reduce cloud complexity should evaluate the environment across five interconnected areas.

Architecture and workload placement

Understand where applications and workloads currently operate, why they are there, and whether those decisions still make sense based on cost, performance, security, and business requirements.

Connectivity and performance

Evaluate how users, applications, clouds, data centers, and edge environments connect. Hybrid cloud performance ultimately depends on the network connecting the pieces.

Visibility and management

Determine whether IT teams have sufficient visibility across infrastructure, applications, networks, and cloud resources to identify performance, cost, and operational issues quickly.

Security and governance

Establish consistent identity, security, compliance, and governance policies across environments rather than managing risk independently within each platform.

Cost and business value

Move beyond cloud-spend reporting and evaluate whether infrastructure investments are producing the performance, resilience, agility, and business outcomes they were intended to deliver.

Together, these areas help shift hybrid cloud from an accumulation of technologies into an intentional enterprise architecture.

Complexity should be managed—not inherited

Hybrid and multicloud environments are not going away.

AI, edge computing, SaaS adoption, acquisitions, regulatory requirements, and changing workload demands may make enterprise infrastructure even more distributed over time.

That doesn't mean it has to become more fragmented.

The organizations that gain the greatest value from cloud will not necessarily be those with the most cloud services or the largest cloud footprint.

They will be those that can manage complexity without allowing complexity to manage them.

For CIOs, that means treating cloud as part of a broader infrastructure strategy—one that connects networks, applications, security, data, and workloads rather than optimizing each independently.

Because the next phase of digital transformation isn't about moving more technology to the cloud.

It's about making the entire enterprise work better together.

Turn cloud complexity into a connected strategy

As hybrid environments grow, organizations need greater visibility, stronger connectivity, consistent security, and a clearer understanding of where workloads deliver the greatest value.

Claro helps organizations connect and modernize distributed technology environments across cloud, connectivity, cybersecurity, data, and managed infrastructure—helping reduce operational complexity while creating a more resilient foundation for digital transformation.

The objective isn't simply a better cloud environment.

It's a more connected enterprise.

FAQ

What is hybrid cloud complexity?

Hybrid cloud complexity occurs when organizations must manage applications, workloads, data, networks, security, and operations across public cloud, private cloud, on-premises, SaaS, and edge environments without consistent integration or governance.

Why do enterprises use multiple cloud environments?

Enterprises use multiple cloud environments because of workload requirements, acquisitions, SaaS adoption, regulatory considerations, cost, performance, geographic requirements, existing technology investments, and business-unit technology decisions.

What are the hidden costs of multicloud?

Multicloud complexity can increase infrastructure spending, operational overhead, security risk, data fragmentation, troubleshooting time, integration requirements, and management burden while slowing application development and digital transformation.

Is hybrid cloud better than public cloud?

Neither architecture is universally better. The appropriate environment depends on workload performance, cost, security, compliance, latency, data, scalability, and business requirements. Many enterprises use hybrid architectures to balance these needs.

How can organizations reduce cloud complexity?

Organizations can reduce cloud complexity by improving workload placement, connectivity, centralized visibility, cost governance, security consistency, application integration, and management across cloud, on-premises, and edge environments.