switching software/cloud infrastructure

Linode to Azure: Budget Cloud Migration for UK SMEs

Move from Linode to Azure while managing cost increases strategically.

1. Executive Summary

This guide outlines the strategic migration of infrastructure from Linode (Akamai) to Microsoft Azure (UK South/West regions). Unlike Linode’s simplified, flat-network architecture, Azure operates on a Software-Defined Networking (SDN) model with complex Virtual Networks (VNets), Network Security Groups (NSGs), and Entra ID (formerly Azure AD) integration. This migration requires shifting from manual, instance-based management to an automated, policy-driven Azure Resource Manager (ARM) paradigm.

2. Why Businesses Migrate: Drivers and Anti-patterns

  • Drivers: Scaling beyond single-region constraints, integration with the Microsoft ecosystem (Office 365, SQL Server), and access to PaaS/SaaS offerings (AKS, Azure SQL, CosmosDB).
  • Anti-patterns: "Lift-and-Shift" without adjusting for Azure’s I/O throughput limits; ignoring Azure’s shared responsibility model; failing to implement Infrastructure as Code (IaC), leading to "Click-Ops" configuration drift.

3. The 6 Rs of Migration (Linode to Azure Context)

  • Rehost (Lift & Shift): Using Azure Migrate to move Linode VMs to Azure VMs. Low effort, but fails to leverage cloud-native benefits.
  • Replatform (Lift & Reshape): Moving a self-managed MySQL on Linode to Azure Database for MySQL. Reduces operational overhead.
  • Refactor (Re-architect): Moving a monolith on Linode to Azure App Service or Azure Kubernetes Service (AKS). Highest ROI, highest complexity.
  • Repurchase: Switching to Azure-native SaaS (e.g., swapping self-hosted mail servers for Microsoft 365).
  • Retire: Decommissioning legacy Linode instances no longer serving business value.
  • Retain: Keeping specialized workloads on Linode if they require specific hardware configurations unavailable in Azure.

4. Pre-Migration Assessment

  • Inventory: Use Azure Migrate appliance to discover Linode workloads. Map dependencies (e.g., hardcoded IP addresses, shared file systems).
  • Network Mapping: Linode’s private networking is simple. Azure requires designing VNet peering, Subnets, and Hub-and-Spoke topologies.
  • IAM: Map Linode’s root/user access to Azure RBAC and Entra ID. Implement the Principle of Least Privilege.
  • Data Transfer Calc: Assess egress costs from Linode. Use Azure Data Box or Site-to-Site VPN for large datasets. Evaluate bandwidth constraints for the initial seed.

5. Step-by-Step Execution Plan

  1. Pilot: Select a low-risk, non-production workload to validate the Landing Zone.
  2. Foundation: Deploy the Azure Landing Zone (Hub-and-Spoke) using Terraform. Configure NSGs, Azure Firewall, and VPN/ExpressRoute.
  3. Data Migration: Use Azure Database Migration Service (DMS) for SQL workloads; use AzCopy or rsync for file-based data migration.
  4. Cutover: Perform a dry run. Update DNS/Load Balancer pointers to the Azure front end. Execute final delta sync and verify application smoke tests.

6. Troubleshooting Common Issues

  • MTU Mismatch: Azure’s VNet MTU is 1500 bytes. Ensure your Linode images don't have custom MTU settings that cause packet drops.
  • Instance Metadata: Applications querying Linode metadata services will fail; update code to query the Azure Instance Metadata Service (IMDS) at 169.254.169.254.
  • Disk Latency: Linode’s SSDs perform differently than Azure Managed Disks. Ensure appropriate disk tiers (Premium vs. Standard SSD) are selected based on IOPS requirements.

7. UK-Specific Compliance

  • GDPR: Ensure all Azure resources are pinned to UK South (London) or UK West (Cardiff).
  • Data Residency: Leverage Azure Policy to prevent the deployment of resources in non-UK regions.
  • Sovereignty: Use Azure Key Vault with Managed HSMs to maintain control over encryption keys, meeting UK financial/public sector security standards.

8. Cost Modeling

  • Direct Costs: Azure VM compute, Managed Disks, and egress bandwidth.
  • Hidden Costs: Azure Firewall, VPN Gateway, and log storage (Azure Monitor/Log Analytics).
  • Optimization: Utilize Azure Hybrid Benefit (if you hold existing Windows Server licenses) and Reserved Instances (RI) to reduce costs by up to 72% compared to Pay-As-You-Go.

9. Conclusion

Migrating from Linode to Azure is a transition from a simplified hosting environment to an enterprise-grade ecosystem. Success hinges on robust planning of the networking foundation and a clear decision between Rehosting and Refactoring. Focus on automation through IaC to ensure your new Azure environment is scalable, secure, and compliant with UK data regulations.