https://catalogartifact.azureedge.net/publicartifacts/dcassociatesgroupinc.slesservervmgen2-9cdb8b03-bce7-4d4e-acf2-caca546a2db7/image3_dcacdiamond216.png
SUSE Linux Enterprise Server
por Derek Coleman & Associates Corporation
Just a moment, logging you in...
Hardened SUSE Linux Enterprise Server 15 SP7 or 16 VM for Azure: SUSE updates, SSH-key sign-in.
You get SUSE Linux Enterprise Server (SLES) 15 SP7 or SLES 16.0 on an Azure Generation 2 VM, built from SUSE's own image for that release and fully patched when the image was built. Each plan is one release. At first boot your VM registers itself with SUSE's public-cloud update servers, so zypper (SUSE's package manager) can install updates right away.
Who it's for
- Teams that already run SLES and want the same releases on Azure
- Platform teams that need SLES 15 and SLES 16 side by side, one plan per release
- Administrators who want a clean base OS for their own configuration tools
What's included
- SLES 15 SP7 with SUSE's kernel build for Azure, version 6.4.0-150700.53.81
- SLES 16.0 with SUSE's kernel build for Azure, version 6.12.0-160000.38. Networking is managed by NetworkManager, and Cockpit (SUSE's browser-based server console) listens on port 9090.
- Azure Linux Agent (the service Azure uses to set up and manage the VM) and cloud-init (the tool that applies your first-boot settings)
After deployment
- Sign in over SSH (port 22) as the admin user with the key you set when you deploy. When you deploy with a key, password sign-in over SSH is refused.
- Nothing shared ships in the image: root has no usable password, the build account and the build's SUSE registration are removed, and SSH host keys and the machine ID are created fresh on your VM.
- On SLES 15 SP7, SSH is the only port listening publicly. On SLES 16, keep port 9090 closed in your network security group (NSG, the firewall rules Azure applies to the VM) unless you use Cockpit.
- The image does not install updates automatically, so schedule your own patching with zypper.
Why this image
- Patched at build: on 12 October 2026 every available SUSE update was applied in two passes with a reboot between them, and the build fails if any security update is still pending at capture.
- Your own registration: the build removes its own SUSE registration before capture and checks that none is left, so each VM registers as itself.
- Tested on a real VM: a weekly test deploys each release as a Trusted Launch VM (Secure Boot plus a virtual TPM, Azure's boot-integrity protections) and checks SSH, provisioning, first-boot cleanup and open ports. In tests on 7 October 2026 both releases finished booting in under 60 seconds on a 2-vCPU Standard_D2s_v3.
- Support: email support@dcassociatesgroup.com, with a response within 1 business day.
How it runs on Azure
The VM runs in your own Azure subscription and virtual network, on any VM size that supports Generation 2, and its usage is billed on your Azure invoice; the Plans + Pricing tab shows each plan's terms. This offer is provided by Derek Coleman & Associates Inc, not by SUSE.