Leostream has equipped its Azure Marketplace remote desktop platform with three major enhancements, the company confirmed on May 19, 2026. The updated Remote Desktop Access Platform now supports Azure NCv6 GPU virtual machines, delivers automated Linux desktop deployment, and integrates with Azure Managed Identity to streamline authentication across cloud resources. The release targets organizations running graphics-intensive workloads and mixed-OS environments that demand simpler, more secure remote access.

What Leostream’s platform does

Leostream acts as a connection broker and management layer for virtual desktops and applications. It authenticates users, assigns the appropriate desktop or app based on policies, and brokers the connection using protocols such as RDP, PCoIP, or third-party alternatives. Unlike single-vendor solutions, the platform abstracts the underlying hypervisor or cloud, letting IT teams mix VMware, Hyper-V, AWS, Azure, and other providers from a single console.

The Azure Marketplace edition packages that capability into a ready-to-deploy offering. Organizations can provision the broker, gateway, and web access components directly from the Azure portal, then connect to existing or newly created virtual desktops. With this update, Leostream extends that model to cover GPU-accelerated Windows and Linux hosts while tightening security through identity-based access.

NCv6 GPU virtual machines bring graphics acceleration to remote sessions

The most visible addition is support for Azure NCv6 GPU virtual machines. NCv6-series VMs pair AMD EPYC processors with NVIDIA Tesla M60 GPUs, delivering two physical GPU cores per instance. This hardware is designed for visualization workloads such as CAD, 3D modeling, medical imaging, and video rendering. Until now, organizations that wanted to host such applications in Azure and deliver them through Leostream had to rely on manual configurations or workarounds. The official listing now bakes in discovery, assignment, and protocol handling for NCv6 instances.

When an administrator registers an Azure subscription, the platform automatically detects eligible NCv6 VMs and can present them in desktop pools alongside standard CPU-only machines. Users assigned to a pool can launch a session that taps the GPU directly, with no additional profile customization needed. Leostream has validated the configuration with NVIDIA GRID drivers, ensuring GPU sharing and licensing alignment so multiple users can share a single physical GPU through virtualized profiles. This matters for cost control: instead of dedicating a full GPU to one user, organizations can partition a single NCv6 node among several concurrent sessions.

Performance is not limited to Windows. The same GPU-accelerated desktops can serve Linux users via protocols that support hardware rendering, such as NoMachine NX or X2Go, both of which Leostream has qualified. For firms running engineering software on RHEL or Ubuntu workstations, the combination of NCv6 and Leostream’s protocol bridging means remote Linux desktops finally deliver the same visual fidelity as their on-premises counterparts.

Automated Linux desktop deployment erases manual scripting

Linux desktop deployment has long been a pain point in VDI. While Windows integration is mature – often just a matter of joining a domain and installing an agent – bringing Linux hosts into a remote desktop pool typically requires hand-crafted scripts to install desktop environments, configure display managers, and set up the appropriate remote protocol servers. Leostream’s update introduces an automation engine that handles the entire chain.

Once an administrator selects a Linux VM template from the Azure gallery – be it Ubuntu, RHEL, CentOS, or SUSE – the platform orchestrates the provisioning sequence. It installs the chosen remote protocol server (X2Go, FreeRDP, or NoMachine), configures a lightweight desktop environment (Xfce or GNOME depending on user preference), sets up SSH keys for secure authentication, and registers the host with the Leostream broker. The result is a “push-button” Linux desktop that appears in the user portal alongside Windows machines, ready for assignment.

Under the hood, the automation leverages cloud-init scripts and Azure’s Custom Script Extension for Linux. Leostream’s marketplace image includes pre-built configuration templates that adapt to the detected Linux distribution. For fleets that need customization – say a specific CUDA version for machine learning desktops – administrators can still inject post-deployment scripts, but the default path works without touching a terminal. The feature slashes deployment time from hours to minutes and removes the most common source of configuration drift.

Because the automation is baked into the Azure Marketplace listing, it also respects Azure’s networking and security constructs. Linux desktops can sit in private subnets, use network security groups, and report back to the broker through a secure tunnel without exposing ports publicly. This design aligns with zero-trust principles, a theme reinforced by the third pillar of the update.

Managed identity tightens security and eliminates secrets

Azure Managed Identity enables the Leostream platform to authenticate to Azure services without storing credentials. Instead of embedding service principal secrets in configuration files – a practice that carries rotation and leakage risks – the platform relies on the managed identity assigned to its own Azure VM or function. When the broker needs to query virtual machine inventory, spin up a desktop on demand, or access a key vault, it presents a token obtained through the Azure Instance Metadata Service. The token is short-lived and scoped to the resources the administrator grants via RBAC.

The impact is twofold. First, the attack surface shrinks: there are no long-lived passwords to steal, and no risk of a compromised config file giving an attacker the keys to the entire Azure subscription. Second, compliance becomes easier. Auditors can trace every action back to the specific managed identity, and RBAC roles allow granular control over which resources the platform can touch. For regulated industries that run remote desktops for PII or IP-heavy workloads, this is table stakes.

Leostream has integrated managed identity at the broker and gateway levels. When the broker launches a new desktop, it uses its managed identity to call the Azure Compute API and start the VM. If the desktop needs access to a shared storage account, the administrator assigns the appropriate role to the VM’s own managed identity – a pattern that Leostream now encourages in its deployment guides. The gateway component can also leverage managed identity to pull TLS certificates from Key Vault, ensuring that encryption materials are always fresh.

For organizations that have already invested in Azure AD as their identity provider, this update closes the loop. Users authenticate once through Azure AD (or Azure AD Domain Services), Leostream maps those identities to desktop assignments, and the infrastructure servers themselves operate with managed identities. The entire chain – user, broker, desktop – runs without a single hard-coded credential.

How the pieces fit together in a typical deployment

A common scenario illustrates the value. An engineering firm wants to give remote workers access to CAD software on Windows and simulation tools on Linux, both needing GPU power. The IT team deploys the Leostream platform from the Azure Marketplace, assigning a managed identity during setup. They select a pool of NCv6 Windows VMs pre-loaded with the CAD suite and, via the new automation, spin up a matching pool of Linux VMs for the simulation environment. Both pools use the same broker and gateway.

An engineer logs in through the Leostream web portal, authenticating with their Azure AD credentials. The broker checks policy: this user is entitled to a Windows CAD desktop and a Linux simulation desktop. It picks an available NCv6 Windows VM and connects via RDP. When the user switches context, the broker hands over a Linux desktop via NoMachine, with GPU passthrough enabled for rendering. Behind the scenes, every API call – from VM start to license check – is authorized by the broker’s managed identity, with no service principal key ever in play.

Because the platform is still a connection broker at its core, it can also fold in on-premises resources for hybrid deployments. The same portal that serves Azure desktops can display VMware Horizons or Hyper-V hosts sitting in a local data center. The managed identity feature, of course, only applies to Azure operations, but the unified user experience remains intact.

Market context and what it means for IT teams

Remote desktop infrastructure has undergone a shift since the post-pandemic normalization. Organizations are no longer in emergency pivot mode; they’re refining architectures for cost efficiency, security, and user experience. GPU-accelerated desktops were once a niche reserved for specialty workstations, but the expansion of cloud-native engineering workflows has made them mainstream. Azure’s NCv6 instances, with their NVIDIA M60 GPUs, sit at an attractive price-performance intersection for mid-range visualization jobs. By certifying these VMs, Leostream taps into a growing customer base that might otherwise default to competing solutions like Windows 365 or Citrix DaaS.

Linux desktop support in the cloud has been equally underserved. Many VDI platforms treat Linux as a second-class citizen, offering basic connectivity but no lifecycle management. Leostream’s automation move signals that the company sees Linux desktops as a first-class workload – not just for developers, but for any professional using GPU-backed Linux applications. The combination of automated provisioning and managed identity also makes it easier for operations teams to treat Linux desktops like cattle, not pets, rebuilding them on the fly as needs change.

Security-conscious enterprises will gravitate toward the managed identity integration. Credential rotation is a frequent cause of operational pain in dynamic cloud environments, and the push toward identity-based access is universal. By aligning with Azure’s native approach, Leostream reduces the operational burden on platform engineers and aligns with Microsoft’s broader zero-trust framework.

Availability and how to get started

The updated Remote Desktop Access Platform is available immediately in the Azure Marketplace. Existing customers can update their deployments through the marketplace’s lifecycle management, while new customers can launch a trial directly. Leostream offers a 14-day free evaluation for any deployment size, with pricing based on concurrent users rather than servers. The company maintains detailed deployment guides on its support portal, including step-by-step videos for the new Linux automation and managed identity configuration.

As the remote desktop landscape continues to evolve, Leostream’s latest move positions the platform as a multi-cloud, multi-protocol broker that can handle the most demanding graphics workloads and the most diverse operating systems. The bet is that IT teams value flexibility over vendor lock-in, and with NCv6 GPUs, Linux automation, and identity-first security now in the box, that bet just got stronger.