Visual studio 2026 professional installation in RDSH

Obtain written confirmation from Microsoft or your licensing reseller for the exact Visual Studio 2026 Professional standalone SKU and purchasing channel before deploying it on shared RDS session hosts, because the published guidance does not explicitly confirm that deployment right.

What can be confirmed

• Visual Studio Professional is licensed per user, not per installation. A standalone perpetual Visual Studio Professional license may be purchased for each engineer, and every person using Visual Studio must hold a valid license. The general guidance also says each licensed user may install and use Visual Studio on any number of devices for development, testing, and demonstration.^1^
• Therefore, one standalone license assigned to the RDS host would not cover multiple engineers. Each engineer accessing Visual Studio would need an individually assigned Visual Studio Professional license.
• A Professional subscription is not inherently required merely to license the Visual Studio IDE: Visual Studio Professional is offered both as an individual product and as part of a subscription.^1^

The unresolved point is whether the license terms delivered with your specific standalone SKU allow those separately licensed users to run one installation in concurrent Windows Server RDS sessions. The public guidance establishes user-based licensing, but it does not expressly state that the standalone product can be installed as a shared RDS application.^2^

Ask the reseller or Microsoft licensing representative to confirm in writing:

1. The exact SKU and channel—retail, CSP, or volume licensing.
2. Whether its license terms permit installation on a Windows Server RD Session Host.
3. Whether multiple separately licensed users may run the same installed copy concurrently.
4. Whether activation is supported independently in each user’s RDS profile.
5. Whether any restriction applies to pooled, cloned, or nonpersistent session hosts.

For volume licensing, the definitive documents are the Microsoft Product Terms and your licensing agreement. For retail purchases, the controlling terms are the Retail Software License Terms supplied with the product.^1^

RDS licensing is separate

Even if the Visual Studio terms are confirmed, Windows Server RDS must be licensed independently. Each user or device connecting to an RD Session Host needs an RDS CAL; this entitlement is not supplied by a standalone Visual Studio license.^3^

For engineers connecting from multiple devices, Per User RDS CALs are generally the relevant model. For shared endpoint devices used by multiple engineers, Per Device RDS CALs may be more appropriate.^4^

Configure the selected mode at:

Server Manager → Remote Desktop Services → Overview → Edit Deployment Properties → RD Licensing

Select Per User or Per Device, then add the activated RD License Server.^5^

If the RDS servers are in a workgroup rather than Active Directory, Per User CALs are not permitted; use Per Device CALs.^5^

Purchasing conclusion

The proposed cost model is potentially:

• one Visual Studio 2026 Professional standalone license per engineer;
• one appropriate RDS CAL per user or device; and
• the properly licensed Windows Server/RDS infrastructure.

Do not purchase on the assumption that per-user licensing automatically grants shared RDS deployment rights. Proceed with the standalone option only after the exact SKU’s governing terms—or written Microsoft/reseller confirmation—explicitly cover shared RD Session Host installation and concurrent use by separately licensed engineers.

References

1. Visual Studio Licensing Guidance - microsoft.com
2. Visual Studio 2026 Professional standalone license can be installed on ...
3. License Remote Desktop Services with Client Access Licenses (CALs)
4. Remote Desktop Services - Choose how you pay
5. License Remote Desktop session hosts | Microsoft Learn