The short answer
LDelight migrates Toronto and Canadian businesses to Azure, using Canada Central in Toronto as the primary region and designing recovery deliberately, because its paired region in Québec City has no availability zones. We plan around Windows Server 2016 reaching end of extended support in January 2027, reuse your Microsoft licences where they apply, and document the work for OSFI and Law 25.
Key takeaways
-
Canada Central as primary, with a recovery design chosen on purpose rather than by default
-
Windows Server 2016 systems prioritised before support ends on 12 January 2027
-
Existing Microsoft licences assessed for Azure Hybrid Benefit
-
Overnight cutovers carried out during our working day
Canada Central, and the recovery question
Azure's Canada Central region sits in Toronto and has availability zones, so a well-built application can survive the loss of a data centre within the region. Its paired region, Canada East in Québec City, has no availability zones. That combination shapes recovery design more than most Canadian teams realise. Some workloads need zone-redundant deployment in Canada Central and nothing more; some need backups or replicas in Canada East to survive a regional event; a few need a warm standby. The default — whatever the first engineer set up — is rarely the right answer for all of them.
We classify each workload by how long it can be down and how much data it can lose, then choose the recovery pattern that meets it at the lowest cost, while keeping everything inside Canada where contracts or privacy assessments require it.
Windows Server 2016 and the 2027 deadline
Windows Server 2016 reaches the end of extended support on 12 January 2027. After that date, systems still running it no longer receive security updates unless an extended support arrangement is in place. For many Canadian organisations those servers host line-of-business applications nobody wants to touch. A migration is the natural point to deal with them: upgrade in place, rebuild on a supported version during the move, or replatform the application onto managed services such as Azure SQL or App Service. We identify them in discovery and schedule them into the earliest waves.
Start from the licences you own
If you hold Windows Server or SQL Server licences with Software Assurance, Azure Hybrid Benefit can reduce the cost of running those workloads in Azure substantially. We inventory what you own and apply it in the cost model, so the business case reflects what you will actually pay rather than list prices.
Working with Toronto
We do not overlap Toronto business hours, so delivery is asynchronous: written hand-offs, a decision log and a fixed 08:00 Eastern call for anything that needs a conversation. Overnight change windows fall inside our working day, so cutovers, data synchronisation and rollback rehearsals are carried out by a team at work rather than on call.
Engagements begin with fixed-fee discovery: an inventory of servers, applications and dependencies, the recovery classification for each workload, the end-of-support list, and a costed wave plan with licensing applied. You keep the document whether or not we go on to run the migration.
Page reviewed Nov 14, 2026. Region and regulatory facts for Canada checked Nov 14, 2026. Rules change — confirm current obligations with your adviser.