In the first blog in our three-part series, we explored why infrastructure strategy should begin with workloads rather than technology.
Once organisations understand their workload requirements, the next challenge is determining which infrastructure approach will best support their business, operational and regulatory objectives.
For many organisations, infrastructure decisions were once relatively straightforward. Hardware reached the end of its lifecycle, software platforms were refreshed, and applications continued to run much as they always had. While every technology refresh required planning, the path forward was often clear.
Today, the infrastructure landscape is considerably more complex. Organisations are balancing cloud adoption, changing licensing models, emerging AI initiatives and evolving business priorities, all while responding to an increasingly demanding regulatory environment. Rather than simply replacing ageing infrastructure, many are taking the opportunity to assess whether their current environment remains aligned to both immediate needs and long-term business objectives.
One of the biggest changes I’ve seen over the past few years is that infrastructure decisions are no longer being driven by technology alone. Organisations are simultaneously weighing licensing changes, AI adoption, evolving regulatory obligations and future business priorities which has led to infrastructure strategy becoming a broader business discussion rather than simply a technology refresh.
Instead of focusing solely on what platform comes next, organisations are now evaluating how today’s infrastructure decisions will support future business objectives, compliance requirements and operational flexibility.
While there is no universal blueprint for hybrid infrastructure, there are several principles I encourage organisations to consider when evaluating their options.
Infrastructure projects are often triggered by a specific event. Hardware reaches end of support, software licensing changes, cloud expenditure comes under review, or a major application requires modernisation. Increasingly, organisations are also responding to broader business and regulatory drivers that influence where applications can operate and how data should be managed.
In Australia, reforms to the Privacy Act, APRA CPS 230, the Security of Critical Infrastructure (SOCI) Act and industry-specific obligations around sensitive information are encouraging organisations to take a fresh look at their infrastructure strategy. Decisions about where workloads run are no longer based solely on performance or cost. Data sovereignty, governance, operational and data resilience and compliance are becoming equally important considerations.
I encourage organisations to view these events as an opportunity to step back and reassess the broader technology landscape rather than simply replacing existing platforms with like-for-like alternatives. Recent changes in the virtualisation market have prompted many organisations to do exactly that, using infrastructure refreshes as a catalyst to evaluate new operating models and long-term architectural direction over simply renewing existing investments.
Infrastructure decisions should support where the organisation is heading, not simply where it is today.
Applications continue to evolve throughout their lifecycle. Some will transition to SaaS platforms, others will be modernised using containers, while new digital services and AI initiatives may introduce entirely new requirements. Evaluating infrastructure without considering these changes can result in environments that satisfy immediate needs but limit future flexibility.
One of the questions I often ask customers is not just what workloads they’re running today, but where those workloads are heading in the future.
“It really comes down to understanding what you’re trying to achieve, what workloads you’re running today, and where those workloads are heading tomorrow.”
Taking the time to understand the broader application roadmap helps organisations make decisions that remain relevant well beyond the next refresh cycle, avoiding unnecessary redesign as business priorities evolve.
Selecting the right infrastructure platform is only one part of the decision. Organisations also need to consider how that infrastructure will be consumed, scaled and supported throughout its lifecycle.
Traditional procurement models often require organisations to purchase infrastructure based on projected growth several years into the future. Consumption-based operating models provide a different approach, allowing infrastructure to grow in line with business demand while reducing the need to overprovision capacity from day one.
I’m seeing increasing interest in models that allow organisations to size infrastructure for current requirements while retaining the flexibility to expand as demand grows. This approach can help avoid significant upfront investment in capacity that may not be needed for years.
For organisations extending Microsoft Azure into on-premises environments, Azure Local, supported by HPE GreenLake, is one example of how infrastructure and operating models can work together to provide greater flexibility while supporting evolving business and regulatory requirements.
No two organisations have the same application landscape, regulatory obligations or operational priorities. As a result, successful hybrid infrastructure strategies are rarely built from a standard template.
The goal is not to identify a single “best” platform. Instead, it’s understanding which combination of infrastructure, operating model and governance approach best supports the organisation’s objectives today while maintaining the flexibility to adapt tomorrow.
That’s why I believe infrastructure strategy should begin with discovery rather than assumption. By evaluating technology decisions within the broader context of business goals, organisations are better positioned to build environments that remain resilient, adaptable and fit for purpose as requirements continue to evolve.
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 aligned to 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.
Once infrastructure decisions have been made, the focus shifts to operations. In the final blog of this series, we’ll examine the governance, management and operating model practices that help organisations simplify hybrid environments.
Contact our team today.
Information provided within this form will be handled in accordance with our privacy statement.