MICROSOFT LICENSING · MODULE 8 · VISUAL STUDIO & DEV/TEST
Visual Studio and Dev/Test:
How does licensing work?
A company developing an application may need Visual Studio, Windows Server, SQL Server, and an Azure test environment. Which individuals need licences, and where does production use begin?
The short answer
A Visual Studio licence is assigned to one specific person.
The assigned individual may exercise the permitted rights for development and testing. The exact benefits depend on the subscription. Production environments require their own appropriate licences.
- 01The licence is assigned to one specific person rather than an entire team.
- 02Standard and monthly subscriptions provide different benefits.
- 03Development, testing, and production must be clearly separated.
- 04Monthly Azure credits are included only with selected standard subscriptions.
- 05Visual Studio Community is free, but its organisation eligibility is restricted.
Explained simply · The essential terms
Three terms that make Visual Studio licensing easier
Visual Studio licensing starts with the person assigned the licence and the purpose of the activity, not simply the computer being used.
Named user
A Visual Studio licence is assigned to one specific person and must not be shared across an entire team.
Dev/Test
Software is used for development, testing, evaluation, or demonstrations rather than day-to-day business operations.
Azure credits
A personal monthly Azure allowance available with selected standard subscriptions for development and testing.
A practical example: Three developers take turns working on the same test server. The relevant count is three individuals, not one server: each needs an appropriate Visual Studio licence.
Understand the product first
What is Visual Studio, and which offerings exist?
Visual Studio is an integrated development environment used to build, test, and improve software. Visual Studio Code is a separate product and does not automatically provide the same licensing rights.
Visual Studio Community
A free development environment for eligible individuals and organisations, with important restrictions for enterprise organisations.
Visual Studio Professional
A commercial developer offering available as a subscription and, depending on procurement channel, potentially as a standalone licence.
Visual Studio Enterprise
A broader developer subscription with enhanced development and testing capabilities. Benefits depend on the actual subscription type.
Visual Studio Test Professional
An offering for eligible testing and quality-assurance scenarios with rights and Azure benefits determined by the specific subscription.
MSDN Platforms
An additional named-user development and testing offering with its own software rights and Azure benefits. Availability depends on the purchasing programme.
Always check the specific subscription for software downloads, test rights, Azure credits, and additional benefits.
The first important distinction
Standard subscription or monthly subscription?
Both options can provide access to the Visual Studio IDE. However, a monthly subscription does not automatically include all standard-subscription benefits.
| Offering | Simply explained | Personal Azure credits |
|---|---|---|
| Professional Standard | Developer subscription with additional benefits depending on the offering and agreement. | USD 50 per month |
| Enterprise Standard | Broader developer subscription with additional development and testing benefits. | USD 150 per month |
| Professional Monthly | Monthly cloud subscription, not equivalent to Professional Standard. | No personal Azure credits |
| Enterprise Monthly | Monthly cloud subscription, not equivalent to Enterprise Standard. | No personal Azure credits |
Downloads, Azure benefits, training, support, and other rights can differ. The actual SKU, benefit comparison, and applicable Microsoft Product Terms determine eligibility.
Named-user licensing
Who needs their own Visual Studio licence?
A Visual Studio licence is assigned to one specific person. That person can exercise permitted rights across multiple devices, but a shared team account does not replace individual licence assignments.
Software developers
Anyone using Visual Studio or subscription-provided software for development needs appropriate rights assigned to them individually.
Professional testers and quality assurance
People regularly involved in development and testing require suitable individual entitlements. Their actual activity matters more than their job title.
Administrators who access the software
Anyone installing, configuring, or using software provided through the subscription generally requires appropriate rights of their own.
External developers and service providers
External participants also need an eligible personal subscription or a properly assigned licence. A shared account is insufficient.
An administrator with no access to subscriber-licensed software does not automatically need a subscription. Someone who installs, configures, or uses it must be assessed individually.
Define the permitted environment
What counts as Dev/Test, and what is production?
Dev/Test covers development, testing, evaluation, and demonstrations. An environment supporting ongoing business operations is not automatically covered by non-production rights.
Development and technical testing
An application is developed, tested, or improved in a separate environment without supporting everyday business operations.
Ongoing business operations
An application processes real business activities or forms part of the operational production estate. Appropriate production licences are required.
Backup, disaster recovery, and overflow
Production backups, disaster recovery, failover, and handling production peak loads are not automatically covered by general Dev/Test rights.
When an application is deployed for business use, Windows Server, SQL Server, and other production components need their own valid licensing.
The important UAT exception
Do business users need a subscription for acceptance testing?
Not necessarily. A business end user may perform eligible user acceptance testing or provide feedback without automatically requiring their own Visual Studio subscription.
A business department validates a new application
An employee checks whether a new business form works correctly before deployment and does not act as a developer or professional tester.
Ongoing professional testing
Developers, quality-assurance staff, and others performing regular development and testing do not automatically qualify for the business-user exception.
No live production data
UAT must not simply use live production data. If production data is copied for testing, it must be discarded afterwards and must not be reimported into production.
The exception covers legitimate acceptance testing and feedback, not ongoing business operations or avoidance of named-user assignment rules.
Included software and practical boundaries
What about Windows, Windows Server, and SQL Server?
Depending on the subscription, development and testing rights may cover different Microsoft products. These rights do not automatically replace ordinary production licences.
The developer PC still needs normal desktop rights
If a device is also used for email, Office, Teams, or other productive work, it still requires its own appropriate Windows licence.
Windows Server in a test environment
An eligible subscription can provide development and test rights for Windows Server. A production server must be licensed under the applicable server rules.
Standard Developer and Enterprise Developer
SQL Server Standard Developer and SQL Server Enterprise Developer are free for non-production development and testing. Neither includes production use.
Free software does not mean free cloud infrastructure
A free Developer edition does not remove charges for an Azure VM, storage, networking, or other infrastructure services.
Once the database supports ongoing business operations, the correct production licensing model must be assessed separately.
Azure credits, clearly explained
Which Visual Studio subscriptions include monthly Azure credits?
Selected standard subscriptions include personal monthly Azure credits for development and testing. Monthly cloud subscriptions do not include these personal credits.
| Subscription | Monthly personal Azure credits | Permitted purpose |
|---|---|---|
| Visual Studio Enterprise Standard | USD 150 | Development and testing |
| Visual Studio Professional Standard | USD 50 | Development and testing |
| Visual Studio Test Professional | USD 50 | Development and testing |
| MSDN Platforms | USD 100 | Development and testing |
| Visual Studio Enterprise Monthly | No personal credits | No automatic Azure-credit entitlement |
| Visual Studio Professional Monthly | No personal credits | No automatic Azure-credit entitlement |
Credits are assigned to an eligible individual and are intended for development and testing. Without another payment method, services generally stop once the available allowance is exhausted. Partner and special programmes may differ.
Azure Dev/Test for individuals and teams
Are personal credits and Enterprise Dev/Test the same?
No. Personal Azure credits and organisational Dev/Test offerings are different arrangements and should not be treated as interchangeable.
Individual Azure credits
An eligible Visual Studio subscriber receives a personal monthly amount for permitted development and testing activities.
Enterprise Dev/Test
An eligible organisation can use a dedicated Azure Dev/Test arrangement for teams. Pricing benefits can apply to eligible VMs, App Service, or selected database services.
Check agreements and individual entitlements
Participating individuals need the appropriate personal rights. Enterprise Agreement instructions do not automatically apply unchanged to MCA or CSP arrangements.
Availability and eligible users depend on the actual agreement, subscription, and applicable Microsoft terms.
Free does not mean unrestricted
When may Visual Studio Community be used?
Visual Studio Community is free, but the rules differ for individuals, smaller organisations, and enterprise organisations.
Developing your own applications
Individuals may use Visual Studio Community for eligible personal application development, subject to the applicable Microsoft licence terms.
Up to five eligible users
In organisations that do not meet Microsoft's enterprise definition, up to five people can use Visual Studio Community for eligible general scenarios.
More than 250 PCs or over USD 1 million in revenue
General commercial use is not permitted in enterprise organisations. Microsoft defines the relevant thresholds as more than 250 PCs or annual revenue exceeding USD 1 million.
Classroom learning, research, and open source
Certain classroom, academic-research, and open-source contribution scenarios can remain eligible even within an enterprise organisation.
Contractors cannot avoid enterprise restrictions solely because their own agency is smaller than the customer for which the software is developed.
Procurement and administration
Which additional rules should you check?
Beyond the edition, assess the purchasing channel, exact subscription, external participants, and any reassignment restrictions.
Volume licensing or Microsoft Store
Standard subscriptions are available through suitable volume-licensing programmes or the Microsoft Store, depending on the offering. They are not simply standard direct or indirect CSP products.
Marketplace and eligible partner channels
Monthly subscriptions are acquired through Visual Studio Marketplace and, depending on the offer, through Azure or eligible CSP partner channels.
Check contractors and partner subscriptions
External people need eligible personal or correctly assigned rights. Some partner subscriptions do not automatically permit revenue-generating development for customers.
Observe the 90-day restriction
Retail and volume-licensing scenarios are generally subject to a 90-day reassignment restriction. Do not assume the same rule applies unchanged to every monthly subscription.
The applicable Microsoft agreement, purchased offering, and relevant Product Terms determine the binding requirements.
A straightforward practical example
Six suitable licences, not seven and not one
An organisation develops an internal application and operates a separate testing environment.
| Person or role | Number | Licensing logic |
|---|---|---|
| Developers | 3 | Three individually assigned suitable licences |
| Professional testers | 2 | Two individually assigned suitable licences |
| Administrator who accesses the software | 1 | One individually assigned suitable licence |
| Business user performing eligible acceptance testing | 1 | May qualify for the UAT exception |
A business user performing genuine acceptance testing does not automatically need an additional subscription. If their activities extend beyond the exception, reassess their licensing.
Check before purchase and use
Eight questions for a reliable licensing decision
- 01To which specific person is the licence assigned?
- 02Is the purchased offering Standard, Monthly, standalone, or a special partner subscription?
- 03Who develops, tests, installs, or configures software provided through the subscription?
- 04Is the environment genuinely Dev/Test, or does it already support production business activity?
- 05Does the business-user exception apply only to legitimate acceptance testing?
- 06Are Azure credits or Enterprise Dev/Test benefits actually included in this specific offer?
- 07Do developer PCs and production Windows or SQL environments have suitable separate licences?
- 08Have contractors, Community limits, purchasing channels, and reassignment rules been checked?
The key takeaway
Assign the person. Separate Dev/Test. License production independently.
A Visual Studio licence is assigned to one specific person. Dev/Test rights cover development and testing. Production environments require their own appropriate licensing.
Current and verifiable
Official Microsoft sources used for this article
Visual Studio benefits, purchase channels, Azure credits, and usage rights depend on the subscription, agreement, programme, and acquisition date. Always consult the current Product Terms and contract documents before purchasing.
- 01Microsoft Licensing: Visual Studio licensing guidance↗ (opens in a new tab)
- 02Visual Studio: Subscription comparison and purchasing options↗ (opens in a new tab)
- 03Microsoft Learn: Azure benefit eligibility for Visual Studio subscriptions↗ (opens in a new tab)
- 04Microsoft Learn: Visual Studio subscription administrator responsibilities↗ (opens in a new tab)
- 05Microsoft Learn: Assign a Visual Studio subscription↗ (opens in a new tab)
- 06Visual Studio: Community edition licensing↗ (opens in a new tab)
- 07Microsoft Learn: Azure Dev/Test offers for Visual Studio subscribers↗ (opens in a new tab)
- 08Microsoft Learn: Enterprise Dev/Test subscriptions↗ (opens in a new tab)
- 09Microsoft Learn: Visual Studio subscriber Azure FAQ↗ (opens in a new tab)
- 10Microsoft Learn: SQL Server 2025 editions and supported features↗ (opens in a new tab)
Note: This article provides clear general guidance and does not replace individual agreement, licensing, or legal review.