فا
MSLicenseHub
developer · reference
🧑‍💻

Visual Studio 2022

Visual Studio 2022 — Community, Professional, Enterprise; subscription vs perpetual; Azure DevOps and GitHub benefits.

VISUAL STUDIO 2022
On this page

Editions · channels · activation · audit notes · FAQs

Editions covered
3
Edition matrix with feature differences and the right audience.
In-depth sections
7
Channels, activation, audit, modern management & more.
FAQs answered
5
Common questions buyers and IT admins ask before purchase.
Words of reference
0.8k
Plain-English, no vendor agenda, updated to current Product Terms.
Edition matrix

Pick the right edition

Each edition targets a specific scale and feature set. Match the workload, not the price tag.

Edition 1
Community

Free for individuals, OSS, education and small teams (<5 devs, <$1M revenue). Same core IDE features.

Edition 2
Professional

Per user. Full IDE, Azure DevOps Basic for 5, $50/month Azure credit on subscriptions, training.

Edition 3
Enterprise

Per user. Adds IntelliTrace, Live Unit Testing, advanced profilers, $150/month Azure credit, larger training catalogue.

Side-by-side

Edition comparison

Heuristic capability matrix derived from each edition's intended use. For binding commitments, always confirm against the current Product Terms.

CapabilityCommunityProfessionalEnterprise
Target audienceEducationProfessionalEnterprise
Domain / Entra join
Virtualisation rights
Advanced security
Centralised management
Volume Licensing path
Deep dive

Visual Studio 2022 — what to actually know

Visual Studio 2022 is Microsoft's flagship IDE for .NET, C++, Python, Node.js, Unity and cross-platform mobile development. It is the first fully 64-bit version of the IDE — which matters when working with very large solutions and large data sets in the test runner. It ships in three editions: Community (free, with usage restrictions), Professional, and Enterprise. The paid editions are sold either as a perpetual licence through Volume Licensing or as a subscription that bundles Azure credits, training resources and additional tooling. Visual Studio 2022 has long-term servicing through to 2032 with the LTSC channel and remains the current release for traditional .NET / C++ desktop and server workloads.

01

Community Edition — and when it is not enough

Community is free for individual developers, open-source contributors, academic research and classroom use, and for small teams of up to five developers inside enterprises whose annual revenue is below US$1 million. The moment a larger company uses it for commercial development, or a sixth developer inside a small company starts using it, you must move every developer to Professional or Enterprise. Read the Community EULA carefully before standardising on it — many organisations assume 'free' means unrestricted and are surprised by the revenue and headcount thresholds at audit time. Community is feature-rich and a perfectly fine IDE; the only reason to avoid it is licence compliance.

02

Professional vs Enterprise

Professional gives you the full IDE, CodeLens basic, the integrated debugger and profilers, and the Professional subscription benefits (Azure DevOps Basic for five users, a US$50/month Azure credit on subscriptions, and a library of e-learning resources). Enterprise adds IntelliTrace and historical debugging, Live Unit Testing across the whole solution, Architecture and dependency diagrams, the advanced CPU / memory profilers, Microsoft Fakes for unit-test isolation, the load test functionality, code clone analysis, and far higher Azure credits (US$150/month). For most teams, the deciding factor is IntelliTrace and Live Unit Testing — if you regularly debug intermittent production issues or do test-driven development at scale, Enterprise pays for itself.

03

Subscription vs perpetual licence

Subscriptions (annual or monthly) include benefits that perpetual licences do not — Azure credits for development and test workloads, training entitlements on Pluralsight or LinkedIn Learning depending on tier, software for development and test (the old MSDN benefit, now Visual Studio Dev Essentials extended), and GitHub Enterprise included with Enterprise subscriptions at certain volumes. Perpetual licences purchased through Volume Licensing entitle you only to the IDE itself, plus version-upgrade rights if you also bought Software Assurance. For most teams the subscription is a better deal: the Azure credit alone covers a lot of dev / test infrastructure, and the GitHub Enterprise inclusion is increasingly the deciding factor.

04

GitHub Copilot and AI integration

GitHub Copilot is a separate per-user subscription that integrates into Visual Studio 2022 for code completion, chat-based code generation, test scaffolding and refactor suggestions. Visual Studio Enterprise subscribers receive Copilot Business as part of their Visual Studio Enterprise subscription at certain GitHub Enterprise tiers — check your specific entitlements with your reseller. The IntelliCode features that ship in the box (whole-line completions trained on your codebase) are free and require no Copilot subscription.

05

Visual Studio Code is not the same product

Visual Studio Code is free, open-source under the MIT licence (with Microsoft's downloaded builds carrying a permissive but proprietary telemetry-enabled EULA) and unrestricted commercially. It is a different product — a lighter editor without the full Visual Studio IDE features (live debugging across multi-project solutions, integrated profilers, designer tools for WinForms / WPF / XAML, the test orchestrator, IntelliTrace, the rich C++ tooling for game and embedded development). Pick whichever fits the workload; many .NET teams use VS Code for everyday editing and the full Visual Studio for debugging, profiling and designer work.

06

Mac, mobile and the long-term picture

Visual Studio for Mac was retired in August 2024. The supported path for Mac-based .NET development is now Visual Studio Code with the C# Dev Kit extension. For cross-platform mobile (formerly Xamarin), .NET MAUI is the current toolkit and is fully supported in Visual Studio 2022 on Windows. iOS development still requires a Mac at build time, but the editing and most of the debug loop can stay in Visual Studio 2022 with pair-to-Mac.

07

Volume Licensing and the MSDN successor benefits

Through Volume Licensing, Visual Studio is sold per user as either a perpetual licence with optional Software Assurance, or as a subscription (cloud or standard). The subscription bundles what used to be called MSDN: rights to install Windows Server, SQL Server, Office and other Microsoft software in dev / test environments at no additional licence cost, as long as those installs are used exclusively for development and test purposes and the developer has an active subscription. This benefit alone is often the practical reason large engineering organisations standardise on Visual Studio subscriptions across the team.

By channel

Where to buy this product

Relative fit of each licensing channel for typical buyers of this product. Calibrate against your own scale and renewal strategy.

Channel fit (typical buyer)
Retail6
Volume Licensing9
Subscription10
Retail / FPPIndividuals & small teams

Boxed or ESD keys, transferable, registered to a Microsoft account.

Volume LicensingMid-market & enterprise

MAK / KMS activation, centralized VLSC, optional Software Assurance.

CSP / Microsoft 365Subscription, per user

Monthly / annual seats, managed through partner or admin center.

OEM is not a buying channel for end users. OEM keys are supplied pre-installed by hardware manufacturers and are not sold standalone — choose Retail, Volume or CSP instead.
Support timeline

Lifecycle phases to plan against

Visual Studio is licensed per developer (subscription), and the included Azure credits, dev/test rights and software downloads are usually worth more than the IDE itself. Treat it as a developer benefit package, not a single product.

Phase 1
Major release
Every ~3 years

Visual Studio 2017 / 2019 / 2022 / 2026 each ship LTSC channels with 10 years of fixes for subscription customers.

Phase 2
Subscription updates
Continuous

Monthly Preview, quarterly stable releases. Cloud services (Azure DevOps, GitHub) iterate independently of the IDE.

Phase 3
End of life
Year 10

Extended support ends; the IDE keeps running but stops receiving security fixes. Build agents on EoL IDEs become an audit and supply-chain risk.

Procurement checklist

Do this, not that

The small set of decisions that determine whether you overpay, fail an audit, or land in the right place.

DO

Use Community Edition for genuinely independent open-source and individual learning — it is free and feature-equivalent to Professional for small teams.

DON'T

Use Community in any organisation over 250 PCs or above $1M USD revenue — the licence terms forbid it.

DO

Buy Visual Studio Subscriptions per developer; each seat includes dev/test rights for almost every Microsoft product.

DON'T

Re-use a single subscription across multiple developers — entitlement is per named user.

DO

Burn the included Azure credits — they reset monthly and disappear if unused.

DON'T

Forget GitHub Enterprise is included with VS Enterprise subscriptions in many programmes — check the benefits portal before buying separately.

Typical deployments

How buyers actually use Visual Studio 2022

Three reference deployments — find the closest match and adapt rather than starting from zero.

Scenario 1
Indie / OSS developer

Community Edition + a free GitHub account. Move to a paid subscription only when revenue or team size crosses the licence threshold.

Scenario 2
Enterprise .NET shop

Visual Studio Professional or Enterprise subscriptions per developer, Azure DevOps or GitHub Enterprise for source and pipelines, Azure dev/test subscriptions for non-prod environments.

Scenario 3
Cross-platform / mobile

Visual Studio + .NET MAUI, or VS Code + the relevant extensions. Subscriptions still pay for themselves through Azure credits and the included tooling.

Cost optimisation

Where the savings actually live

None of these are tricks — they are the same levers Microsoft's own licensing specialists pull on every renewal.

💰
Subscriptions > perpetual for most teams

The dev/test rights, Azure credits and bundled GitHub/Office benefits in a VS Subscription pay back the cost long before the IDE itself does.

📊
MSDN / Visual Studio dev-test pricing on Azure

All Azure VMs spun up by a subscriber for dev/test get heavily discounted base rates — never run dev workloads at pay-as-you-go rates if the developer has a subscription.

🎯
Right-size Enterprise vs Professional

IntelliTrace, Live Share advanced features, architectural validation and Test Professional only exist in Enterprise. If your team will not use them, Professional is dramatically cheaper.

Counterfeit & risk

Red flags when buying second-hand

These four signals show up in every counterfeit-licence case we have seen. If any of them is present, walk away — no discount makes it worthwhile.

01
Standalone OEM key sold below market

OEM keys are distributed only pre-installed on hardware and stay bound to that device for life. A separately sold OEM key is almost certainly leaked, harvested from scrapped hardware, or fully counterfeit.

02
Lifetime key with no invoice or VLSC record

Microsoft entitlement always leaves a paper trail — a Volume Licensing Service Center record, a CSP invoice, a sealed Retail box with a COA, or a Microsoft Store order. No proof = no defence in an audit.

03
Key works once, then 'not genuine' after the next cumulative update

Classic symptom of a MAK key that has exceeded its activation pool, or a KMS key being abused outside its volume programme. Microsoft revokes these centrally; the activation grace period is short.

04
Seller refuses to put the entitlement in your tenant

Legitimate CSPs and LARs transfer the licence into your Microsoft 365 / Azure / VLSC tenant under your domain. If the seller insists on activating 'for you' on their account, you do not own anything.

Acronyms

Licensing terms used on this page

Quick definitions — the full glossary lives at /en/glossary if you need to dig deeper.

CSP

Cloud Solution Provider — Microsoft's primary indirect channel for subscriptions and cloud services.

VLSC

Volume Licensing Service Center — the portal where Volume Licensing keys, agreements and downloads live.

MAK

Multiple Activation Key — a Volume Licensing key with a finite activation count, used for isolated machines.

KMS

Key Management Service — an on-premises activation host that activates clients on a 180-day re-check cycle.

EA

Enterprise Agreement — Microsoft's largest commitment-based volume contract, typically a 3-year term with annual true-ups.

SA

Software Assurance — the upgrade-and-benefits add-on to Volume Licensing; required for new version rights and several mobility scenarios.

Browse the full glossary →
FAQ

Frequently asked questions

Can a 50-person enterprise really use Community for free?+
No. Community is licensed for individuals, OSS contributors, education and small teams of up to five developers in companies with less than US$1 million annual revenue. A 50-person company using Community for commercial development is out of compliance — every developer needs Professional or Enterprise.
Is GitHub Copilot included with Visual Studio?+
Not for all editions. Visual Studio Enterprise subscriptions at certain GitHub Enterprise tiers include GitHub Copilot Business; Community and Professional users buy Copilot separately. The IntelliCode features in the box are free and do not require Copilot.
Does Visual Studio 2022 still get major updates?+
Yes — minor versions (17.x) continue to ship roughly every quarter through 2026, with security and quality updates extending to 2032 under the LTSC channel. The next major release is on a separate roadmap, no longer tied to a fixed annual cadence.
Where can I legitimately buy a license?+
Through Microsoft's Retail channel, an authorised Cloud Solution Provider (CSP), or a Volume Licensing partner (MPSA, Enterprise Agreement, Open Value, Server & Cloud Enrollment). OEM keys are distributed only pre-installed by hardware manufacturers and stay bound to that device for life — they are not sold to end users as standalone products. If someone offers you a standalone OEM key, treat it as a red flag: it almost always means either a leaked volume key, a counterfeit, or a key harvested from decommissioned hardware, none of which Microsoft will honour at audit time.
What gets checked in a Microsoft licensing audit?+
Auditors map every installed copy of a product to a proof of purchase (Volume Licensing Service Center record, CSP invoice, or sealed Retail packaging with the original key). They also verify edition alignment — for example that every server reporting a Datacenter feature actually carries a Datacenter license — and that CAL counts cover the maximum number of authenticated users or devices during the audit window. Soft enforcement (warnings, true-up invoices) is common for small variances; large gaps escalate to formal Software Asset Management engagements and back-billing at list price.
Related

Other products in this category