Organisations have more infrastructure choices than ever before. Public cloud, private cloud, hybrid environments and modern application platforms all offer compelling benefits, but they also make technology decisions more complex.
In my conversations with customers, I find the challenge is rarely deciding whether workloads belong in the cloud or on-premises. More often, it’s understanding which environment is best suited to each application and how those environments can be managed consistently over time.
Many infrastructure projects still begin with technology. A virtualisation platform reaches end of life, hardware needs refreshing, or rising cloud costs trigger a review of the existing environment. While these events often start the conversation, I don’t believe they should define it.
The organisations that achieve the best long-term outcomes are the ones that begin by understanding their applications, business objectives and technology roadmap before evaluating platforms.
This is the first blog in a three-part series exploring the decisions that shape successful hybrid infrastructure strategies. We’ll start with what I believe is the most important question: should infrastructure decisions begin with technology, or with the workloads and business outcomes they’re intended to support?
As I often explain to customers:
“Azure Local can absolutely run virtual machines, but it’s also a platform that can be leveraged for containers and other native Azure services. It’s much more than a virtualisation platform.”
That distinction is becoming increasingly important as organisations reassess their infrastructure strategy. Evaluating Azure Local purely as a replacement for an existing virtualisation stack risks overlooking the broader opportunity to modernise applications, simplify operations and create a more consistent hybrid cloud experience.
Rather than starting with products, I encourage organisations to start with workloads.
Every application has different requirements when it comes to performance, latency, data sovereignty, resilience, integration and future business priorities. Some workloads are well suited to public cloud, others are better retained within an organisation’s own data centre, and many organisations will continue to operate a combination of both for the foreseeable future.
Application roadmaps are equally important. Organisations need to understand whether critical systems are expected to remain in their current form, transition to SaaS, adopt container-based architectures and support emerging AI initiatives over the coming years. Decisions made today should support those future outcomes rather than simply addressing an immediate infrastructure requirement.
Here’s an example that illustrates this approach. An IT services provider focused heavily on the financial services industry, where data security and sovereignty concerns can often slow or even prevent cloud adoption. Their customers wanted the innovation and agility associated with cloud services but weren’t prepared to move sensitive workloads away from infrastructure they controlled.
By adopting a hybrid cloud approach with Azure Local, they were able to extend Azure-consistent tools and services into on-premises environments. This allowed their customers to benefit from cloud innovation while maintaining control over sensitive data and meeting regulatory requirements.
The outcome was faster customer acquisition driven by higher levels of trust, improved scalability to meet changing demand and a security posture that compliance teams could confidently support.
For organisations operating in regulated industries, it demonstrates an important point: it doesn’t have to be a choice between innovation and control. A well-designed hybrid strategy can deliver both.
For organisations already invested in Microsoft Azure, Azure Local extends familiar Azure capabilities into the data centre while maintaining consistent management, governance and security. However, infrastructure is only one part of a successful hybrid strategy.
An equally important consideration is how that infrastructure will be consumed, managed and maintained throughout its lifecycle.
Unlike workloads running entirely in the public cloud, Azure Local still relies on physical infrastructure. Hardware requires monitoring, firmware updates, lifecycle management and ongoing operational oversight. These responsibilities remain important considerations when evaluating the long-term cost, operational effort and flexibility of a hybrid environment.
This is where HPE GreenLake can play an important role.
HPE GreenLake provides a cloud operating experience for on-premises infrastructure, allowing organisations to consume infrastructure more flexibly while simplifying many of the operational tasks associated with managing the underlying platform. Rather than treating infrastructure refreshes as isolated capital investments, organisations can adopt a more agile consumption model that aligns more closely with modern cloud operating practices.
Combined with Azure Local, HPE GreenLake can help organisations modernise workloads while maintaining the governance, visibility and operational consistency increasingly required across hybrid environments.
What I find most interesting is how infrastructure conversations are changing.
Rather than asking whether cloud or on-premises is the better option, organisations are increasingly asking where individual workloads create the greatest business value, how those workloads should be governed, and which operating model best supports long-term growth.
That’s a far more strategic discussion, and ultimately a more valuable one.
As hybrid environments continue to evolve, successful infrastructure strategies will be defined less by the technologies organisations choose and more by the decisions that shape how those technologies work together.
By taking a workload-first approach and considering both the platform and the operating model from the outset, organisations can build hybrid environments that not only meet today’s requirements but are flexible enough to adapt to whatever comes next.
Whether you’re reviewing your current infrastructure, evaluating Azure Local, responding to changing licensing requirements or planning your next modernisation initiative, taking the time to understand your workloads, business priorities and future roadmap can lead to better long-term outcomes.
Data#3‘s specialists can help you assess your current environment, identify opportunities for improvement and develop a strategy that aligns technology decisions with your operational, governance and business objectives.
Contact our team to start the conversation and build a roadmap that supports both today’s requirements and tomorrow’s opportunities.
In the next blog, we’ll explore the questions organisations should ask when evaluating infrastructure options and planning for future requirements.
Contact our team today.
Information provided within this form will be handled in accordance with our privacy statement.