Cloud and infrastructure that improve platform decisions, strengthen resilience and optimise workload placement
Not every workload belongs in the cloud, and not every server belongs on-premises. We help organisations make platform, refresh and migration decisions properly across Microsoft Azure, Azure Local, hybrid and on-premises infrastructure, servers, storage, backup, virtualisation, VMware exit and managed cloud, then place each workload where it serves the business best.
Architecture before migration.
Practical support across cloud migration, infrastructure refresh and workload placement
The right starting point depends on the pressure in the current environment: ageing infrastructure, VMware exit, migration uncertainty, Microsoft 365 growth, recovery assumptions, cost drift or uncertainty about what should stay local.
Infrastructure Refresh is for organisations with ageing servers, VMware exit, unsupported hardware, backup uncertainty or HCI decisions.
It is not only about replacing hardware. It is about deciding which workloads still need local infrastructure, which should move to cloud, and what can be retired. The work can include:
Local infrastructure is not automatically legacy; it can be the right answer where the business needs performance, predictable access or recovery control.
Managed Cloud and Migration is for organisations moving workloads, users, data or access into a better cloud or hybrid model. The real question is not what can move, but what should move, in what order, under which identity model, and with what backup and recovery design.
The work can include:
A migration is not complete when workloads are online. The environment still needs to be operated after cutover.
Workload Placement is for organisations that need to make better decisions before committing to cloud migration, hardware refresh, VMware exit or another platform direction.
It starts with workload behaviour:
Some workloads suit Azure or Microsoft 365, some should stay local, and some should be retired rather than migrated. This step prevents refreshing hardware for workloads that should move, or moving workloads that should have stayed local.
Cloud, infrastructure and recovery now need to be designed together
Older infrastructure decisions were often made around hardware cycles: servers, storage, virtualisation, backup and support contracts. Cloud decisions were treated separately. That separation no longer reflects how organisations operate.
Users work across Microsoft 365, SaaS, cloud applications and local systems. Identity controls access across both. Backup and recovery depend on understanding dependencies across platforms. Cost can drift in cloud while local infrastructure still carries critical workloads. A VMware exit can reshape the cloud and infrastructure path. A cloud migration can expose weak identity, backup and governance.
Cloud
Azure, Microsoft 365, Entra ID, cloud migration, managed cloud, governance, monitoring and cost visibility need a clear operating model after workloads move.
Explore Managed Cloud and Migration →Local infrastructure
Servers, VMware, Azure Local, Nutanix, storage, local applications and site-dependent workloads need to be assessed on performance, supportability, recovery and cost.
Explore Infrastructure Refresh →Recovery
Backup, restore evidence, application dependencies, Microsoft 365 data, Azure workloads, identity and local systems need to be recoverable as one operating environment.
See the recovery dependency →Backup and recovery affect every cloud and infrastructure decision. Microsoft 365 data, Azure workloads, identity, local systems, applications and file platforms need to be understood before workloads move, infrastructure is refreshed or a hybrid model is finalised.
A dependency to design around rather than a standalone offering. For dedicated backup and disaster recovery, see Cybersecurity / Backup and Disaster Recovery.
Cloud and infrastructure with hybrid depth and clear workload placement
Move to cloud, keep local, retire or replace, based on workload behaviour, latency, data size, dependency, recovery, licensing, cost and supportability.
Recovery dependencies considered before migration, refresh or hybrid design is finalised.
Cloud spend, identity, access, monitoring, ownership and operating model considered before and after change.
Azure, Microsoft 365, identity, backup, monitoring, documentation and support responsibilities operated after cutover.
Where cloud and infrastructure work usually starts
Most cloud and infrastructure work begins with one visible pressure point. The useful work is understanding what else is connected before the workload direction is locked in.
01Ageing servers and infrastructure lifecycleInfrastructure Refresh or Workload Placement
Hosts age, firmware falls behind, supportability becomes harder, backup assumptions become older, and recovery confidence weakens. A refresh should clarify which workloads still need local infrastructure, which should move to cloud, what can be retired and what recovery position the business needs.
Best fit: Infrastructure Refresh or Workload Placement →02VMware exit and platform pressureInfrastructure Refresh
A VMware exit can quickly reshape the hybrid model. The question is what the workloads need, what the business can operate, what the support model requires and whether alternatives such as Azure Local, Nutanix or cloud migration are appropriate.
Best fit: Infrastructure Refresh →03Cloud migration uncertaintyManaged Cloud and Migration or Workload Placement
Migration often stalls when the organisation treats "move to cloud" as the decision. The real decision is more specific: which workloads move, in what order, under which identity model, with what backup and recovery design, and under which cost governance.
Best fit: Managed Cloud and Migration or Workload Placement →04Microsoft 365 growth without governanceManaged Cloud and Migration
Teams, SharePoint, OneDrive, Exchange Online, Entra ID, external sharing, permissions and retention can become the business operating layer before ownership is clear. The environment needs stronger structure around identity, access, data, backup, administration and lifecycle.
Best fit: Managed Cloud and Migration →05Hybrid workload placementWorkload Placement
Most organisations run hybrid environments shaped by application behaviour, user access, latency, data size, finance systems, design files, operational platforms, recovery requirements and cost. The right answer is workload by workload.
Best fit: Workload Placement →06Backup and recovery confidenceCybersecurity / Backup and Disaster Recovery
Recovery assumptions shape cloud, migration and infrastructure decisions. Local systems, Azure workloads, Microsoft 365 data, identity and applications need to be understood before workloads move or infrastructure is refreshed, while dedicated backup and disaster recovery is delivered through Cybersecurity.
Best fit: Cybersecurity / Backup and Disaster Recovery →07Cloud cost driftManaged Cloud and Migration
Cost drifts when services are created without ownership, workloads are oversized, reserved capacity is not planned, or the business lacks clear reporting. Cost governance should sit inside the managed cloud operating model, with rightsizing, ownership, review cadence and visibility built in.
Best fit: Managed Cloud and Migration →08Identity, access and security foundation gapsManaged Cloud and Migration
Entra ID, Conditional Access, MFA, administrator roles, device compliance, privileged access, backup access and monitoring all affect how safely the environment can be moved, refreshed and operated. Every future decision depends on this foundation.
Best fit: Managed Cloud and Migration →The platform follows the workload
Not everything belongs in cloud. Not every local workload is legacy. Not every VMware exit should become a full platform replacement. Not every cloud migration should proceed before identity, backup and cost governance are ready. The correct decision depends on the workload and the operating environment around it.
Architecture before migration. Every workload where it serves the business best.
Cloud and infrastructure work that leaves the environment easier to operate
We approach cloud and infrastructure through the operating environment: how users access systems, how workloads behave, how Microsoft 365 and Azure are governed, how local infrastructure is supported, how backup and recovery work, and how costs, documentation and ownership are managed after change.
Engineering-led workload placement and platform direction that stay connected to operations
Cloud and infrastructure work goes wrong when it is treated only as a platform move. A migration finishes but cannot be governed. A refresh replaces hardware without improving recovery. A VMware exit reduces licensing cost but creates a new support problem. Inlight IT connects assessment, design, migration, refresh and support so the environment can be operated after the change.
01We recommend less change when that is right
Sometimes the right recommendation is to do less than expected. We will tell you when the platform should stay simpler, or when a workload should stay exactly where it is. We are looking for the project the environment actually needs, not the biggest one.
02Assessment, design, migration and support are connected
They are connected through documentation, handover and operating context. The recommendation should not sit separately from the reality of operating the environment.
03We connect the platform to everything around it
platform decisions sit beside Entra ID, Conditional Access, device compliance, backup, recovery, endpoint protection, monitoring and vendor escalation. The cloud and infrastructure path is never decided in isolation.
04Local infrastructure still has a role
Local infrastructure is not automatically legacy. Azure Local, Nutanix, refreshed servers and hybrid infrastructure can be the right answer when workloads need local performance, predictable access, recovery control or site-dependent operations.
05We support the operating model after change
The environment needs to be monitored, patched, documented, recovered and improved after the change. That operating context should shape the design, not only the aftermath.
06Clear visibility for decision-makers
Leaders need to understand what should move, what should stay, what needs refresh, where cost is drifting, where recovery is weak and what decision needs to happen next. The goal is practical visibility, not reporting overhead.
Cloud and infrastructure work where the right answer was not one-size-fits-all
Questions businesses ask about cloud and infrastructure decisions
What is included in Cloud and Infrastructure services?
Cloud and Infrastructure services can include cloud migration, infrastructure refresh, workload placement, Azure and Microsoft 365 administration, hybrid cloud design, backup and recovery planning, identity integration, monitoring, documentation and ongoing operational support.
The work is not only about moving systems to cloud. It is about deciding where each workload should sit, what needs to change first, how the environment will be secured, how recovery will work, and who will operate the platform after the change.
How do we decide between Azure, Azure Local, Nutanix and refreshed local infrastructure?
The right platform depends on the workload, not the trend. Some systems suit Azure because they need cloud scale, remote access, integration with Microsoft 365 or reduced dependency on ageing hardware. Other workloads may need Azure Local, Nutanix or refreshed local infrastructure because of performance, latency, data size, licensing, application dependencies, recovery requirements or operational control.
A good platform decision should compare workload behaviour, identity, storage, backup, supportability, licensing, network access, recovery time, recovery point, cost and the practical skills needed to operate the environment. The answer may be public cloud, private cloud, hybrid infrastructure or a staged transition rather than a single platform decision.
What should be reviewed before a cloud migration?
Before a cloud migration, the current environment should be reviewed across users, workloads, applications, identity, data, integrations, security controls, backup, recovery, licensing, network paths and operational ownership.
This helps avoid moving existing problems into a new platform. It also clarifies what should migrate, what should remain local, what should be replaced, what should be retired and what needs remediation before cutover. Migration planning should include Microsoft 365, Entra ID, Azure, backup, endpoint management, security controls, documentation and the support model after go-live.
How do backup and recovery dependencies affect platform decisions?
Backup and recovery can materially change the right platform decision. A workload may be technically suitable for cloud, but recovery time, recovery point, data volume, identity dependency, application dependency or restore complexity may make a different architecture more appropriate.
Recovery planning should consider Microsoft 365 backup, Azure Backup, immutable backup, local infrastructure recovery, identity recovery, administrator access, restore testing, RTO, RPO and the sequence required to bring systems back online. Platform decisions should not be finalised until recovery dependencies are understood.
Where does VMware transition fit into Cloud and Infrastructure planning?
VMware transition usually sits inside a broader infrastructure and workload placement review. It is not only a renewal or replacement question. It should be assessed alongside hardware age, licensing, support contracts, host capacity, storage, backup, recovery, application dependencies and the future operating model.
The outcome may be a VMware refresh, migration to Azure, use of Azure Local, movement to Nutanix, replacement of specific workloads, or a staged hybrid approach. The important point is to avoid treating VMware transition as a product swap when it may be an opportunity to simplify, retire or re-platform parts of the environment.
Is cloud always better than on-premises infrastructure?
No. Cloud can be the right answer for many workloads, especially where remote access, scalability, Microsoft integration, resilience or reduced hardware dependency matter. But some workloads are better kept on local infrastructure or private cloud because of performance, latency, data size, specialised systems, cost, licensing or recovery requirements.
A stronger decision is workload-by-workload. The aim is not to be cloud-only or infrastructure-only. The aim is to create a platform position that is secure, recoverable, cost-aware and practical to operate.
What is the difference between cloud migration and infrastructure refresh?
Cloud migration moves selected workloads, data or services into a cloud platform such as Azure or Microsoft 365. Infrastructure refresh updates or replaces local platforms such as servers, storage, virtualisation, backup, switching or private cloud.
In practice, the two decisions often overlap. A refresh may reveal that some workloads should move to cloud, while others should remain local. A cloud migration may reveal that identity, backup, networking or retained local systems still need attention. The right approach should consider the whole operating environment rather than treating migration and refresh as separate projects.
What happens after the cloud or infrastructure project is complete?
After migration or refresh, the environment still needs to be operated. That includes monitoring, patching, backup checks, restore testing, identity administration, access control, documentation, vendor coordination, cost review, security review and support escalation.
A successful project should leave the business with clearer ownership, better documentation, known recovery paths and an operating model that can support the platform after cutover. Cloud and infrastructure work should not end with deployment. It should leave the environment easier to manage, support and improve.
Build the right cloud and infrastructure position
Tell us what is driving the change — server refresh, VMware exit, Azure migration or cost drift.
Prefer email? contact@inlightit.com.au