Skip to main content
Version: Developer

Windows support overview

Kasm Workspaces delivers Windows desktops and applications to users through isolated, browser-accessible sessions. The Connection Proxy converts RDP connections into authenticated, browser-native sessions, so the target server is not exposed to unauthenticated traffic. Windows support spans several architectures and carries Microsoft licensing considerations that shape which approach fits a deployment. Supporting Windows is a complex topic, because it combines technical implementation choices with licensing restrictions in the Microsoft ecosystem.

Supported architectures​

Kasm Workspaces supports the following Windows architectures:

  • Fixed Windows servers. Kasm provides access to static individual servers over RDP.
  • AutoScaled Windows servers. Kasm AutoScales servers in supported cloud providers and manages user sessions to the VMs.
  • Microsoft RDS. Kasm sits in front of a Microsoft RDS deployment and provides access to desktops and applications that RDS manages.
  • Azure Virtual Desktop (AVD). Kasm manages access to AVD deployments.
  • Microsoft Windows 365. Kasm sits in front of Windows 365 deployments to apply data loss prevention (DLP) and isolation.

Microsoft licensing​

caution

Any licensing restrictions stated or implied for Microsoft products are provided in good faith. They may not reflect the current rules or fully summarize complex Microsoft licensing. Consult Microsoft to confirm your rights as a licensee. Kasm does not provide support for licensing Microsoft products.

Microsoft has specific licensing requirements for access to software through Remote Desktop Services (RDS) and virtual desktop infrastructure (VDI). These requirements can be complex and vary by scenario and product.

When you use Kasm Workspaces as an RDP connection to an RDP application or RDS Session host, confirm that you have the appropriate Microsoft licenses for the software being accessed. These may include Windows Server, RDS Client Access Licenses (CALs), and Microsoft Office.

For Windows VMs in the cloud, you can use pay-as-you-go (PAYG) licensing or bring-your-own-license (BYOL). With PAYG, Windows licensing is built into cloud costs, though some providers bill the Microsoft fee separately. Check your cloud provider for details. With BYOL, you license the servers yourself, either manually or through automation.

Evaluate the following Microsoft licensing restrictions when you select an architecture or cloud provider:

  • Microsoft disallows Office versions later than 2019 on a VM in any cloud provider other than Microsoft Azure.
  • Microsoft does not support Windows 10 or Windows 11 multi-session images in any cloud provider other than Microsoft Azure. Running these editions elsewhere requires one VM per user, which raises licensing cost significantly.
  • Cloud marketplaces do not provide Windows 10 or Windows 11 images outside Azure. You can create custom images and license the operating system yourself.