If you work with Microsoft tools, sooner or later you're going to run into them. Visual Studio subscriptions and its entire ecosystem of benefitsIDEs, Azure, GitHub, support, training, and much more. The problem is that the information is often scattered across portals, partner centers, and help pages, and it's easy to get lost among so many plans, tiers, and terms.
In this guide we have compiled and reorganized the information clearly. Everything you need to know about Visual Studio subscription plans and benefits: license types, what each one includes, differences between monthly and annual cloud subscriptions, how they are managed together with GitHub Enterprise, what has changed with the Microsoft AI Cloud Partner Program, and what options you have depending on the type of organization, including startups, SMEs, and large enterprises.
What is a Visual Studio subscription and what does it include?
A Visual Studio subscription is not just an IDE license: it's a complete package of tools, services and resources Designed to enable development teams to create, test, and deploy applications faster and more securely, both in the cloud and on-premises.
With an active subscription, the developer gains access to the Visual Studio integrated development environment (IDE) in the edition that corresponds to you (Professional or Enterprise, mainly), in addition to a wide set of additional benefits: Azure services, Azure DevOps, software downloads, technical support and specialized training.
These subscriptions are offered through different purchasing channels to suit every scenario: volume licensing for organizations that want to centralize management and billing, partner programs, cloud solution providers (CSPs), retail (Microsoft Store), and monthly cloud subscriptions for those who need maximum flexibility.
Beyond the SDI, one of the great attractions is access to Product downloads and licenses for development and testingas well as special economic conditions on certain Azure services for non-production workloads, allowing for cost reduction in test and pre-production environments.
Visual Studio license types and levels
Visual Studio subscriptions are always licensed per user and must be nominally assigned to be valid. This is especially important in business and partner contexts, where license compliance is tightly controlled.
Broadly speaking, the Visual Studio ecosystem is organized into several main products, each with its target audience and level of functionality:
- Visual Studio Community: designed for individual use, students, classroom training, academic research and contribution to open source projects.
- Visual Studio Professional: geared towards teams and companies that need a complete IDE, with advanced debugging, collaboration and professional features.
- Visual Studio Enterprise: the most complete edition, with advanced testing tools, diagnostics, code coverage, complex workloads, and scalability capabilities for large teams.
- Visual Studio Code: a lightweight, cross-platform editor that, combined with extensions, becomes a powerful environment for a multitude of languages.
Visual Studio Community is Free but with limitations on use in business environmentsIn non-business organizations (fewer than 250 PCs or less than $1 million in annual revenue), up to five users are permitted to work with Community outside of educational, academic, or open source settings. In business organizations, its use is permitted only for open source, academic research, and classroom training, with no exceptions.
Visual Studio Professional and Enterprise, on the other hand, They market it as a paid subscription.with different rights and associated benefits depending on whether they are acquired via volume licensing, CSP, retail or as part of partner programs.
Visual Studio versions and Windows compatibility
Currently, the Visual Studio ecosystem consists of several versions of the IDE focused on different needsboth in terms of platform and capacity.
Visual Studio 2022 It is the latest version of Microsoft's main IDE. It is a 64-bit application, which allows you to open and work with very large solutions and complex projects without significantly impacting performance. It includes support for modern technologies such as .NET 5 and later, improvements to IntelliCode (AI-based smart suggestions), and stronger Git integration, including support for multiple repositories within the same environment.
Visual Studio 2019 It was the previous version and represented a significant leap in user experience, with a optimized interface for faster solution loadingImprovements to code cleanliness and organization, and advanced refactoring capabilities. Starting with this version, support for macOS (Visual Studio for Mac) was expanded, especially for the Professional edition and later.
Visual Studio 2017 It stands out for its cross-platform development orientation: it allows the creation of applications for Android, iOS, Windows, Linux and the web, with a strong focus on cloud-based development and testing scenarios, including tools for diagnosis and corrective testing.
On the other hand, Visual Studio Code It's a lightweight yet powerful editor that works well with C++, .NET, Node.js, JavaScript, Python, and many other languages. Its cross-platform and extensible design makes it an ideal choice for those who prefer a more modular environment.
Regarding compatibility with Windows operating systems, the relationship between versions is clear: Windows 11 only officially supports Visual Studio 2022 (Previous editions are not supported in this version of Windows.) Windows 10 supports Visual Studio 2022, 2019, and 2017, offering considerable flexibility. And on Windows 7, with the latest updates applied, Visual Studio 2019 and 2017 can be used, although it's advisable to review the extended support requirements.
Main benefits of Visual Studio subscriptions
Beyond the IDE license, Visual Studio subscriptions are designed as a productivity suite for developersAlthough the specific details depend on the subscription level, they usually cover several key areas.
In the tools and services section, a subscription may include monthly Azure credits for development and testing...up to around $150 per month depending on the tier, as well as special pricing for dev/test workloads on certain Azure services. It also typically offers access to Azure DevOps basic or trial plansMicrosoft 365 developer accounts and, in some cases, Microsoft 365 for business apps.
In terms of professional development, subscriptions typically provide access to third-party training resources and training partnerswith specific content to develop skills in modern application development. Certain plans offer exclusive discounts on training platforms for subscribers.
Technical support is also part of the package: some subscriptions include up to four professional technical support incidents with Microsoft, very useful when working with complex Azure environments, continuous integration, or IDE-specific problems.
Finally, one of the most tangible values is the access to product downloads for use in development and testing environmentsThis includes versions of Visual Studio itself, as well as other Microsoft products needed to set up test labs, always within the terms of the subscription and without production use.
How cloud subscription cancellation works
When managing a Visual Studio subscription in the cloud (the so-called monthly or annual cloud subscriptions), it is very important to understand what happens when it is cancelled to avoid surprises and service interruptions.
When you cancel a cloud subscription, what you're actually doing is stop auto renewalThe subscription remains active until the scheduled renewal date, at which point it simply expires. Once expired, the subscriber loses the right to use Visual Studio and any other benefits included in that subscription.
For cloud subscriptions with monthly billing, cancellation takes effect on first day of the following monthIf only some subscriptions are cancelled out of several, it's advisable to check at the beginning of the month who retains access, to ensure that the correct users still have an active subscription assigned.
For annual cloud subscriptions, cancellation takes effect on first day of the month following the end date of the 12-month cycle from the original purchase date or from the last annual renewal charge. For example, a purchase made on January 3, 2018, would remain active until February 1, 2019, at which point it would automatically renew for another year unless canceled beforehand.
If you cancel a Visual Studio cloud annual subscription before the end of the current year, the subscription It remains active until the end of the already paid period, but there is no right to a refund.In other words, future renewal is simply deactivated and the subscription expires when it is due.
Use and activation of subscriber benefits
The benefits associated with a subscription are primarily managed through the Visual Studio subscriber portal (my.visualstudio.com). From there you can view, activate and use the various included features.
Each benefit can have a different activation processSince many of these benefits are provided by external partners (training platforms, third-party services, etc.), the necessary steps are documented for each benefit: account creation, software installation, online resource setup, and credit redemption.
The portal clearly states which subscriptions include each benefit Step-by-step instructions are provided for activating and starting to use each feature. For more details, the official support documentation recommends going to the "Subscriptions" section and then to "Benefits" in the navigation panel.
If you don't find a specific advantage you were expecting, it may be because The benefits available depend on the subscription level and may change over timeTo see what each paid subscription level includes, Microsoft maintains a specific page listing the benefits organized by categories such as Tools, Azure, Software and Downloads, Services, Learning, and Technical Support.
Download, keys and activation of the Visual Studio IDE
Your subscription level determines what you get. You can access the Visual Studio IDE editionA Visual Studio Professional subscription, for example, does not grant access to Visual Studio Enterprise, and vice versa. If you are unsure which subscription level you have been assigned, you can check it on the subscriptions page of your portal.
To download and activate the IDE, the basic flow is quite straightforward:
- Access the subscription portal with the account to which the license has been assigned.
- In the Tools section, locate the Visual Studio IDE icon that corresponds to your level.
- Click on the download link located under the benefit icon.
- You will be redirected to the Visual Studio download results page, from where you can obtain the installer.
- Follow the steps in the download and installation wizard.
Once the IDE is installed, you can Log in directly with the email address associated with your subscription.No product keys are required. This login activates the license for as long as your subscription is active.
If you need to work offline for an extended period, there is the option to Retrieve a product key linked to your subscriptionThis allows you to use the IDE offline while respecting the terms of use. This key can also be obtained through the subscriber portal.
In case you need previous versions of the IDE, the subscription portal includes a specific downloads section for previous versions, where builds of Visual Studio 2019, 2017, etc. are listed, useful for legacy projects or compatibility scenarios.
Visual Studio Community and options for startups
For projects with tight budgets, especially in the initial stages, Microsoft offers Visual Studio Community as a free option provided the license rules are respected. This edition allows an unlimited number of users to use the IDE in educational settings (classroom), academic research, or to contribute to open-source projects, free of charge.
In other use cases, Visual Studio Community can be used in non-business organizations with up to five users that do not fall into the educational, academic, or open source categories. In business organizations, any use other than open source, classroom training, or academic research is prohibited with Community.
They do not exist direct discounts for startups within Visual Studio subscriptions as such, but there are specific programs for emerging companies through Microsoft's platform for startups, where you can get Azure resources, technical support and other ecosystem advantages.
If your project is just starting out, it's key to carefully review the Visual Studio Community license terms and assess whether you meet the eligibility requirements. Otherwise, the most sensible option is to upgrade to a paid plan (Professional or Enterprise) or explore Microsoft's startup offerings.
Visual Studio with GitHub Enterprise: how they integrate
Some advanced plans offer a combination of Visual Studio subscriptions with GitHub Enterprisedesigned for organizations that want to align their development environment with private repositories, advanced security, and modern collaboration tools.
This package is managed in two separate parts: the Visual Studio subscription (Professional or Enterprise) and the GitHub Enterprise component. When a user receives a Visual Studio subscription with GitHub, the Visual Studio subscription manager assigns the corresponding license, and the user receives an email notification.
From that moment on, the subscriber can see in https://my.visualstudio.com/benefits All the benefits of your subscription, including access to GitHub Enterprise. This benefit initially appears as pending or not activated.
GitHub Enterprise administration is performed independently from within the GitHub organization itselfWhen a company sets up its GitHub Enterprise Cloud account, GitHub sends an email notifying them that their Visual Studio subscription has been linked. The benefit icon in the Visual Studio portal changes status to reflect this, although this setup may take some time to complete depending on the organization's internal processes.
When the GitHub organization administrator sends the user an invitation to join the organization or a specific repository, the user receives an email from GitHub and the Visual Studio's benefits panel is updated againAfter accepting the invitation, the GitHub Enterprise tile in the benefits portal changes from "Pending" to "Activated," and the user can now start taking advantage of GitHub Enterprise with all its features.
Microsoft AI Cloud Partner Program and Developer Benefits
The partners participating in the Microsoft AI Cloud Partner Program They offer a set of specific benefits for developers associated with the Visual Studio Enterprise IDE and other cloud and training resources.
Visual Studio subscriptions in this context must be licensed per user, explicitly assigned, and aligned with the program's rights applicable to the partner. These are not isolated licenses, but rather benefits integrated into packages of advantages that the organization receives at the company level.
As part of the 2026 benefits update, Microsoft has introduced relevant changes: the following are offered more learning resources and technical support geared towards the development of modern applications, including specific training material, Azure-focused community forums and a Concierge Chat service that guides partners to get the most out of their benefits.
These changes aim to provide partner development teams with better tools to Incorporate new technologies, maintain continuous learning and increase their daily productivity. At the same time, the way some legacy benefits are delivered has been reviewed to align them with current security and cloud development practices.
For example, Azure credits are no longer tied to each individual IDE license and are now... to be allocated at the organizational level through benefits packagesThis allows for grouped usage planning, sharing credits between teams and projects, and reducing the percentage of credits that remain unused or expire.
Changes to Azure credits and legacy downloads
One of the most notable changes in the benefits update is that Azure individual monthly credits Associated with each developer subscription have been removed in favor of a per-organization model.
Now the credits are grouped into the partner program benefits package and can be used from the Azure subscriptions that the organization designatesThis allows for centralized consumption management, with better cost reporting and more efficient use of Azure resources.
Some historical advantages have also been withdrawn, such as downloads on traditional installations and transferable keys for products such as Windows, Office, or certain servers within the partner program's developer bundle. These products remain available through Microsoft's usual licensing channels, but are no longer included as part of the developer benefits.
Additionally, tools have been removed that They don't fit with modern cloud-centric workflowsreplacing them with current services, training resources and tools aligned with cloud-first developments and updated security standards.
Despite these changes, the core advantages for development teams remain: the Visual Studio Enterprise license, Azure DevOps basic and trial plans, C# resources in Visual Studio Codeas well as access to developer communities such as Microsoft Q&A, Tech Community and events such as Visual Studio Live.
Managing Azure credits that are about to expire
If you previously used individual monthly Azure credits Linked to your developer subscription, it's important to act before the associated subscription is withdrawn to avoid disruptions to running resources.
The first option consists of Reimplement the resources using the bundled credits package from the partner program. This involves redeploying your services on an eligible Azure subscription, associated with your current benefits package. To monitor and plan for this usage, Microsoft recommends using Cost Management reporting tools.
The second alternative is to keep the resources where they are, but Remove the spending limit and move to a pay-per-use billing modelIn this way, services continue to function without interruption, but the cost is paid according to actual consumption without depending on promotional credits.
As a third option, you can move the resources to another subscription or resource group that best fits the organization's strategy, whether within the same tenant or in a different context, following Azure's migration guidelines.
Visual Studio license allocation and reassignment for partners
In the Partner Center, Partner Program administrators have a defined workflow for assign or revoke access to the Visual Studio portal and the associated advantages.
The standard process for granting a Visual Studio Enterprise subscription to a user involves logging into the Partner Center, going to the Benefits section, and then, within the Developer Tools tab, selecting Visual Studio subscription benefits. From there, you choose the specific benefit you want to activate and, in the wizard, select the user to whom the subscription will be assigned.
If the user does not yet appear on the list, you can Register from the account settings from the Partner Center. Once assigned, the user will manage their subscription from the Visual Studio portal like any other subscriber.
The same interface allows View and remove assigned users to any active Visual Studio subscription. Simply go to the View and Remove Users tab, locate the user, and click the Remove option. There is also a feature to reassign a subscription from one user to another, although this option only appears after at least 90 days have passed since the initial subscription was activated.
Regarding GitHub Enterprise, administration is done from another Benefits section of the Partner Center, where the GitHub Enterprise Cloud subscription is activated and the instructions are followed to complete the activation and link with the corresponding GitHub organization.
Partner designation transitions and renewals
During the transition of Designations inherited from the partner program to the new Solutions Partner designationsNew Visual Studio subscriptions may be created associated with the organization's new status.
In those cases, the partners must reassign Visual Studio subscriptions to the users who really need to continue working with them. This involves reviewing who was previously using licenses and, based on the company's priorities, assigning the new licenses to the same users or to others.
If the organization maintains the same solution area upon renewal (for example, remaining in Enterprise Applications), user license assignments typically inherit automatically And it's not necessary to reassign everything on every anniversary. However, if you change solution areas (for example, from Enterprise Applications to Modern Work) or lose eligibility for a specific designation, you need to manually review and reassign the licenses.
The partners participating in the Microsoft AI Cloud Partner program are responsible for carrying out their own internal control Regarding the use of licenses and services provided by the program, Microsoft does not provide a historical list of users assigned to Visual Studio subscriptions in legacy enrollments prior to the transition, so it is advisable to have your own tracking processes in place.
For other usage-based benefits, such as Azure credits, the need for reassignment depends on whether the organization renews within the same solution area or changes its designation. The recommendation is to periodically review deployed resources and anticipate changes before each annual renewal.
The set of plans, benefits, and usage rules surrounding Visual Studio subscriptions offers a A very powerful platform for development teams to work with up-to-date tools, controlled access to Azure resources, continuous training, and technical support.Provided that the differences between subscription levels, purchase options, partner programs, and cancellation or transition conditions are well understood, a clear understanding of this licensing architecture and its benefits is key to leveraging the true value of the Visual Studio ecosystem, minimizing unnecessary costs, and maintaining compliance with licensing requirements and best security practices within the organization.