فا
MSLicenseHub
developer · reference
🧑‍💻

Visual Studio 2022

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

Before licensing Visual Studio 2022

01Developer02IDE edition03Dev / test rights
Visual Studio 2022 · licensing decision diagram, not a product screenshot

Assign paid Visual Studio rights to the licensed user. Check Community eligibility and the exact subscription benefits; software provided for development and testing does not automatically carry production-use rights.

Confirm against official Microsoft sources

Licensing terms and guides · Product lifecycle directory

Record the exact edition, version, quantity, agreement and support date. Obtain written confirmation of delivery, refund and support terms; a perpetual licence is not a lifetime support guarantee.

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
Edition and deployment guidance; verify current rights against official sources.
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

Compare the stated edition details. An omitted capability is not evidence that a feature is unavailable; verify the exact release in Microsoft's documentation.

CapabilityCommunityProfessionalEnterprise
Edition and licensing notesFree for individuals, OSS, education and small teams (<5 devs, <$1M revenue). Same core IDE features.Per user. Full IDE, Azure DevOps Basic for 5, $50/month Azure credit on subscriptions, training.Per user. Adds IntelliTrace, Live Unit Testing, advanced profilers, $150/month Azure credit, larger training catalogue.
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 leaves mainstream support on 12 January 2027 and receives security fixes until 13 January 2032. Visual Studio 2026 is the newer release; 2022 remains common where toolchains or extensions are pinned to it.

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

Confirm that the exact SKU is available in the proposed channel and region. A channel name does not establish entitlement or guarantee a lower price.

Evidence to request

  • Exact product, edition, version and licence quantity.
  • Order, invoice and applicable agreement or subscription record.
  • Ownership in your organisation's account, where applicable.
  • Written reassignment, renewal and support conditions.

OEM is supplied only pre-installed by hardware manufacturers, never sold as a standalone licence.

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
Exact product
Identify

Record the release, edition and servicing channel of Visual Studio 2022; family names alone do not establish support dates.

Phase 2
Official lifecycle
Verify

Look up the exact product in Microsoft's lifecycle directory. Fixed and Modern Lifecycle policies differ; not every release has extended support.

Phase 3
Deployment
Plan

Confirm supported operating systems, application dependencies and upgrade rights before deployment.

Phase 4
End of support
Migrate

A perpetual licence can remain valid after support ends, but it does not guarantee security updates. Check any ESU programme separately.

Purchase preparation

What to include in a Visual Studio 2022 quote request

People
Number of developers who will use the licensed software.
IDE
Exact Visual Studio version and edition.
Benefits
IDE-only purchase or subscription benefits required.
Environment
Development/test requirements, separate from production rights.

These are planning inputs, not a licence calculation. Confirm the final quantity and use rights against the exact version and agreement.

Compare like-for-like quotations
  • Match product, edition, version, quantity and perpetual or subscription terms.
  • Confirm total cost, renewal conditions and the evidence of ownership supplied.
  • Obtain written delivery, refund and support conditions before payment.
Official product licensing guide
Request a quote
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

Assume Community is permitted for all organisational work. Enterprise restrictions have specific exceptions for classroom learning, academic research and open-source contributions; read the exact licence terms.

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

Illustrative planning scenarios, not customer case studies. Check the exact product rights and deployment requirements.

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

Compare entitlement, deployment and renewal costs; savings depend on your workload and written quotation.

💰
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

Eligible Visual Studio subscribers may use designated Azure dev/test offers subject to subscription, workload and user requirements. Ordinary Azure VMs do not automatically receive dev/test pricing.

🎯
Right-size Enterprise vs Professional

Compare the exact Visual Studio feature matrix and subscription benefits. IntelliTrace and architectural tooling differ by edition; Live Share is not an Enterprise-only entitlement, and Test Professional is a separate offering.

Counterfeit & risk

Red flags when buying second-hand

These warning signs require further verification; activation alone cannot establish licence ownership.

⚠ 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 not an eligible standalone purchase; request documented rights through an appropriate channel.

⚠ 02
Lifetime key with no invoice or Microsoft 365 admin center volume licensing record

Request applicable order and agreement records, such as Microsoft Store purchases, CSP subscription records or volume licensing details in the Microsoft 365 admin center. Activation alone is not proof of entitlement.

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

Activation failures can have several causes, including key eligibility, activation counts, connectivity and hardware changes. Check the error through official Microsoft guidance; it does not by itself prove counterfeiting.

⚠ 04
Seller refuses to put the entitlement in your tenant

For tenant-based subscriptions, confirm your organisation controls the tenant and can read its subscription records. Retail and on-premises entitlements use different records; not every licence is assigned through a tenant.

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.

Microsoft 365 admin center volume licensing

Volume licensing administration — agreements, keys and downloads are now managed in the Microsoft 365 admin center.

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 feature updates?+
Version 17.14 is the final feature release of Visual Studio 2022. Mainstream support ends on 12 January 2027, and security fixes continue until 13 January 2032. New features ship in Visual Studio 2026.
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?+
A licensing review compares deployed software and access with documented entitlements: edition, version, quantity, assignment, agreement and any qualifying subscription or Software Assurance benefits. Use applicable order and agreement records, including volume licensing records in the Microsoft 365 admin center where relevant. CALs cover licensed users or devices, not simply concurrent sessions. Audit procedures and remedies depend on the agreement; no universal penalty or outcome is assumed.
Related

Other products in this category