Visual Studio Licensing in SPLA

For Service Providers, licensing infrastructure (Windows Server) and databases (SQL Server) is "business as usual." But when a customer asks to host a development environment - specifically Microsoft Visual Studio - the rules of the Services Provider License Agreement (SPLA) change drastically.

Unlike SQL Server or Remote Desktop Services, Visual Studio is not a standard commodity you can simply "rent" to a customer on a monthly basis. Here is your guide to navigating the restrictions and the new opportunities for hosting developer tools.

1. The Hard Truth: You Cannot "SPLA" Visual Studio

The most important rule regarding Visual Studio in the SPLA program is that it is essentially not an SPLA product.

While you are accustomed to reporting Subscriber Access Licenses (SALs) for products like Exchange or SharePoint, you generally cannot do this for Visual Studio.

The "Non-SPLA" Rule: Microsoft training materials explicitly list installing "non-SPLA products," such as MSDN (the legacy term for Visual Studio Subscriptions), as a top compliance mistake.
The Implication: You cannot act as a reseller of Visual Studio licenses on a month-to-month basis. If a customer wants to develop software on your servers, they generally cannot rent the development tools from you.

2. Service Provider Internal Use

While you cannot rent Visual Studio to customers, you (the Service Provider) likely need it for your own administrators and developers to maintain the environment.

Testing & Evaluation: SPLA grants a right for internal testing and evaluation of software for up to 90 days.
Administration: You are allowed up to 20 administrators per datacenter for maintenance purposes.
Commercial Subscriptions: For long-term internal development that goes beyond basic administration or 90-day testing, Service Providers typically must acquire their own internal Visual Studio Subscriptions through standard Volume Licensing channels, rather than reporting them through SPLA.

3. The Solution: Flexible Virtualization Benefit (FVB)

Since you cannot rent Visual Studio to your customers, the only compliant way to host it for them was previously very difficult (requiring dedicated hardware). However, the Flexible Virtualization Benefit (FVB) has opened the door for "Bring Your Own License" (BYOL) developer scenarios.

The Scenario: Your customer, DevHouse, has a team of developers. Each developer has a Visual Studio Subscription (formerly MSDN) with active Software Assurance or a subscription term. They want to move their development workstations to your cloud to enable remote work and collaboration.

The New Rules (FVB):

Eligibility: You must be an Authorized Outsourcer (any provider who is not a "Listed Provider" like AWS, Google, Microsoft, or Alibaba).
Developer Tools Included: The FVB explicitly applies to "developer tools" and software available under subscription licenses, which covers Visual Studio.
Shared Hardware: Under FVB, DevHouse can run their Visual Studio instances on your shared multi-tenant servers. You do not need to isolate them on dedicated hardware anymore.
Licensing:

The Customer provides the Visual Studio licenses.
You do not report Visual Studio on your SPLA.
Windows 10/11: If the developers are developing on Windows 10/11 VMs (common for Visual Studio), FVB allows this on shared hardware as well, provided the users have Windows/Microsoft 365 Enterprise licenses.

4. Common Compliance Pitfalls

1. The "Community Edition" Trap

A dangerous misconception is that you can host Visual Studio Community Edition for customers because it is "free."

The Reality: The Community Edition has strict commercial use limitations. Installing it on a shared SPLA environment for a commercial customer is a significant compliance risk often flagged as installing a "non-SPLA product".

2. Mixing SPLA and Internal Dev/Test

Service Providers sometimes try to use their own internal Visual Studio partner keys to license a customer's environment.

The Rule: Partner licenses (Silver/Gold/Action Pack) are for your internal use only. They have no hosting rights and cannot be used to provide services to third parties.

Bring Your Own Visual Studio with Octopus Cloud

Octopus Cloud helps service providers host development workloads safely and compliantly.

By supporting the Flexible Virtualization Benefit, you can enable customers to bring their own Visual Studio subscriptions to shared infrastructure while ensuring SPLA reporting is accurate, audits run smoothly, and your cloud services remain secure and cost-effective.

To learn more about it, visit this page.