Share via

Migration feasibility for SUSE Linux Enterprise 11 SP4 (VMware) to Azure

Youthanun Lertrat (UTL) 0 Reputation points
2026-05-22T08:35:52.51+00:00

I would like to seek guidance regarding the feasibility of migrating an on-premises workload to Microsoft Azure.

Current Environment:

  • OS: SUSE Linux Enterprise Server (SLES) 11 SP4
  • Platform: VMware (on-premises)
  • Workload type: SAP

Requirement:
We are planning to migrate this VM to Azure using a lift-and-shift approach (e.g., Azure Migrate or similar tools). However, due to application dependency constraints, we prefer not to upgrade the OS version prior to migration.

Questions

  1. Is SLES 11 SP4 supported for migration to Azure as-is (without upgrading the OS)?
  2. If migration is technically possible:
    • Will the VM be supported by Azure (including Azure VM agent, extensions, and updates)?
      • Are there any limitations or risks (e.g., security, compatibility, lack of support)?
  3. If direct migration is not supported, what is the recommended approach?
    • Upgrade OS before migration?
      • Migrate first, then upgrade on Azure?
        • Any alternative strategies?

Additional considerations:

  • We are mindful that SLES 11 SP4 is an older OS version and may be in extended or unsupported lifecycle.
Azure Migrate
Azure Migrate

A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.


1 answer

Sort by: Most helpful
  1. AI answer

    2026-05-22T08:36:13.02+00:00
    1. Migration support for SLES 11 SP4 on VMware

    SUSE Linux Enterprise Server 11 SP4 on VMware is within the operating systems that Azure Migrate supports for agentless VMware migration and for automatic configuration (“hydration”):

    • The agentless VMware migration support matrix lists SUSE Linux Enterprise Server 11 SP4 as a supported Linux OS for migration to Azure.
    • The preparation guidance explicitly includes SUSE Linux Enterprise Server 11 SP4 in the list of Linux versions for which Azure Migrate automatically performs required changes for Azure (kernel/LIS, fstab, udev, network, Azure Linux agent, etc.).

    Therefore, SLES 11 SP4 on VMware can be migrated “as-is” (lift-and-shift) to Azure using Azure Migrate.

    1. Post‑migration support, agent, and limitations

    From the provided content:

    • Azure VM requirements for migrated VMs include:
      • 64‑bit guest OS
      • OS disk ≤ 2,048 GB
      • 1 OS disk, up to 64 data disks (≤ 32 TB each)
      • No shared VHD or FC disks
      • BitLocker not supported
    • For Linux connectivity after migration, SSH must be enabled on the source VM and allowed through firewalls and NSG rules.

    For supported Linux versions (including SLES 11 SP4 in the list):

    • Azure Migrate automatically:
      • Updates kernel image with Hyper‑V Linux Integration Services.
      • Updates fstab entries.
      • Removes problematic udev rules.
      • Updates network interfaces.
      • Installs the Azure Linux VM agent during migration for supported versions.

    Implications for SLES 11 SP4:

    • Technically supported for migration and for running as an Azure VM.
    • Azure Linux VM agent is installed automatically during agentless migration for the listed SLES versions, so VM extensions and Azure platform integration are available according to that agent’s capabilities.
    • Because SLES 11 SP4 is an older OS, there are inherent risks and limitations:
      • Lifecycle/patching: older OS versions may be in extended or end‑of‑support state from the OS vendor, which implies reduced or no security updates.
      • Security posture: running an EOS/EOL OS in production increases security risk.
      • Future compatibility: newer Azure features, extensions, or tooling may not be validated or supported on legacy OS releases.
    1. Recommended approach if staying on SLES 11 SP4

    From the migration planning guidance:

    • Azure Migrate supports lift‑and‑shift first, then performing OS upgrades in Azure.
    • There is explicit support for Windows OS in‑place upgrade during/after migration; for Linux, the guidance is to ensure the OS is in the list of supported distributions and versions and to apply required changes.

    Given that SLES 11 SP4 is supported for migration but is an old release, recommended strategies are:

    1. Lift‑and‑shift first, then modernize on Azure
      • Use Azure Migrate (agentless VMware migration) to replicate and migrate the SLES 11 SP4 SAP VM to Azure.
      • Validate SAP workload functionality after test migration.
      • Plan an OS upgrade path on Azure to a supported SLES version (or another supported SAP‑certified Linux) once the workload is stable.
    2. Upgrade before migration (if change windows and testing capacity allow)
      • Upgrade SLES 11 SP4 to a currently supported SLES version on‑premises.
      • Then migrate with Azure Migrate, benefiting from a longer support horizon and better security posture from day one in Azure.
    3. General guidance regardless of sequence
      • Ensure the VM meets all Azure VM requirements (disk sizes/count, 64‑bit OS, no unsupported storage types).
      • For Linux, verify SSH is enabled and firewall rules allow SSH before migration.
      • Run a test migration first to validate boot, networking, SAP application behavior, and agent/extension operation.

    In summary, SLES 11 SP4 on VMware can be migrated as‑is to Azure with Azure Migrate, and Azure Migrate will automatically perform the necessary OS‑level changes and install the Azure Linux agent for this version. However, due to its age and lifecycle status, it should be treated as a transitional state, with a clear plan to upgrade to a newer, fully supported SLES (or other supported Linux) version after or around the migration.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.