USE VISUAL STUDIO SOFTWARE

Visual Studio subscribers are permitted to run вЂњmostвЂќ of the subscriber software on VMs in Azure, for test and development purposes. These credits can only be used for test & development uses and cannot be combined across accounts.

USE VISUAL STUDIO FREE

вЂњ creating, deploying and managing lab environment(s) using Microsoft Azure Test PlanвЂќ Azure Monthly creditsД®ach вЂњstandardвЂќ Visual Studio subscription includes a monthly allowance of free Azure credits: System Center VMMДЄre permitted to run System Center Virtual Machine Manager (VMM) for:

Enterprise Annual (cloud subscription no longer available)ДЄs well as rights to the server product, each subscription also provides 1 x CAL.

USE VISUAL STUDIO PLUS

Additional use rights Production use Office Professional Plus / Office 365 ProPlus (Apps for Enterprise) One big thing to note is that Cloud subscriptions donвЂ™t include вЂњSubscriber BenefitsвЂќ or any perpetual rights вЂ“ they are aimed at programmers working in a DevOps environment rather than those developing with Microsoft technologies. Test Professional & MSDN Platforms donвЂ™t include the Visual Studio IDE вЂ“ so no programming environment.

Standard subscriptionsД®nterprise edition is the most fully featured with Professional coming in next вЂ“ however, features in MSDN Platforms that are not in Professional include: Visual Studio subscriptions come in 2 flavours вЂ“ Standard and Cloud. This can be a useful tool when managing Visual Studio software spend although may need additional management when reviewing historical compliance. This is done simply by purchasing the appropriate SKU. to move from a higher edition (say Enterprise) to a lower edition (say Professional) at the point of renewal. Visual Studio is a rare beast in that it allows you to вЂњrenew downвЂќ вЂ“ i.e. However, updates are not permitted, and product keys can only be used up to their activation limit.

USE VISUAL STUDIO LICENSE

While no new software or license keys can be downloaded, existing downloads and product keys can continue to be used. Visual Studio subscriptions purchased via perpetual license programs allow limited perpetual use after a subscription expires. However, as weвЂ™ll discuss later вЂ“ mixed environments can make audits more difficult. This doesnвЂ™t preclude you from mixing VMs running MSDN & Production software on one server as, according to the above, each VM constitutes its own environment rather than it being that host in its entirety. Environments that are used for production at least some of the time, such a server that is rotated into production during peak periods of activity.Environments that support disaster-recovery or backup for a production environment.Environments that connect to a production database.вЂњ any Physical or Virtual OSE running a production workload or accessing production data, or Physical OSE hosting one or more Virtual OSEs running production workloads or accessing production dataвЂќДЄnd the Visual Studio Licensing Guide gives the following examples: The Microsoft Product Terms define this as: Visual Studio software cannot be used in a production environment. Visual Studio subscriptions can be reassigned between users but only once every 90 days Production Environment The requirement for a вЂњdedicated deviceвЂќ precludes Visual Studio from being used in public cloud shared environments such as Amazon AWS and Google GCP вЂ“ although it can (in most cases) be run on Microsoft Azure. вЂњ design, develop, test, and demonstrate their programsвЂќ вЂњ any number of copies of the software and any prior version on any deviceвЂќ Visual Studio subscriptions are licensed Per User with each licensed user able to use:

Use visual studio