The short answer
LDelight migrates Sydney and Australian businesses to Azure, typically using Australia East as the primary region and choosing recovery in Australia Southeast or Australia Central on purpose. For VMware estates we use Azure VMware Solution where a fast exit matters, then modernise in later waves, and for APRA-regulated firms we deliver the exit plan CPS 230 expects.
Key takeaways
-
Australia East as primary, recovery region chosen per workload
-
VMware estates can move quickly to Azure VMware Solution, then modernise
-
Exit plans and access documentation delivered for CPS 230 and CPS 234
-
Evening change windows fall inside our working day
Three Australian region choices
Azure gives Australian businesses more regional options than most markets. Australia East in New South Wales is the primary region, with availability zones. Australia Southeast in Victoria is its pair, without zones. Australia Central in Canberra is intended for government and critical-infrastructure workloads. Many Australian tenants ended up spread across them by accident — a resource group created here, a backup vault there — which makes recovery behaviour hard to predict.
We start by classifying each workload by how long it can be unavailable and how much data it can afford to lose, then pick the pattern: zone-redundant within Australia East, backup or replication to Southeast, or a design in Central where the customer or regulator requires it. The result is a recovery map you can explain to a board, rather than a set of defaults.
Leaving VMware without rewriting everything
For organisations running VMware in their own data centre, licensing changes have pushed migration up the agenda faster than application teams can modernise. Azure VMware Solution offers a bridge: the same VMware environment, running on dedicated hosts in Azure, moved with familiar tools and minimal change to the applications. It is not the cheapest long-term home for most workloads, so we treat it as a first wave — exit the data centre on schedule — followed by planned waves that move applications to native Azure services where the business case supports it.
Exit is part of the design
Since July 2025, APRA-regulated entities have had to register arrangements with material service providers and test exit plans. That applies to the cloud provider and, depending on what we operate, potentially to us. Everything we build — landing zone, infrastructure code, runbooks — is delivered into your tenant and repositories, and the handover includes a written exit plan. For non-regulated businesses this is simply good practice: you should never need a supplier's cooperation to change suppliers.
Working with Sydney
We share two and a half to three and a half hours with Sydney each afternoon for workshops and reviews. Our day continues into your evening, which is when most Australian change windows sit, so cutovers and rollback rehearsals are carried out by a team at work. Our engineers do not need production personal information to build the platform, and any access during cutover is time-limited and logged.
Page reviewed Nov 14, 2026. Region and regulatory facts for Australia checked Nov 14, 2026. Rules change — confirm current obligations with your adviser.