Developer AA Licensing Information
- Can I put the software on machines in a lab shared with non-Developer AA students?
- The EULA says that I can use Developer AA software in my courses. Does the word “course” refer to individual courses or entire courses of study?
- Can a non-University affiliated organization like a computer club purchase a Developer AA Membership for use by its members?
- That’s great! So if my organization has some students and I purchase a Developer AA Membership does that mean that I can distribute Developer AA software to all of my organization members?
- What if I am a commercial organization with a legal Developer AA Membership distributing Developer AA software to my students and faculty only – can they do commercial work with the software?
- What if I build a new software product for an academic research project. Can I sell the product commercially after the project is completed?
- Can I transfer machines with Developer AA software to non-Developer AA member departments in my University?
(Q) Can I put the software on machines in a lab shared with non-Developer AA students?
(A) Sure, but the EULA is still applicable. If a lab is only accessed by member students and faculty, administration of the EULA is a relatively simple process. If you desire to put Developer AA software in a shared lab, we recommend that you only do it if you think you can enforce the EULA. For example, if a shared lab at a university has machines outfitted with Windows obtained from an OEM vendor and is accessed by Geogrpahy Students and Computer Science Students covered under a Developer AA agreement, the administrator may feel very comfortable that they can enforce the EULA. Since Windows was purchased via an OEM vendor, they will be legal for use by both parties (Geography and CS students) and the Geography Students will probably have little interest in using the technical offerings of Developer AA.
(Q)The EULA says that I can use Developer AA software in my courses. Does the word “course” refer to individual courses or entire courses of study?
(A) Both. The EULA is global and thus designed to be used in many different countries with many different languages and educational systems. The two main scenarios for this case are:
Non-STEM majors taking STEM courses. For example: in the case of an Art major taking a class in Visual Basic, the word “course” refers to an individual class taken by a student whose major field of study is not STEM related. Developer AA tools may be accessed and used for STEM classes by all students regardless of their major field of study. We do not require the students to de-install Developer AA software upon completion of the class, but please remember that the Academic only, Non-commercial usage rights always apply to Developer AA software. Therefore, we notify our students and faculty that the easiest way to ensure compliance for non-STEM majors is to install Developer AA software over a legally purchased Operating System.
STEM majors taking Non-STEM courses. For example: in the case of a Computer Science major taking a class in Art History to fulfill her degree requirements. Developer AA tools and software may be accessed and used by Students pursuing STEM-related degrees for all of their STEM courses.
(Q) Can a non-University affiliated organization like a computer club purchase an MSDN AA membership for use by its members?
(A) Sure, as long as the organization has one or more members who are currently enrolled in or teaching course(s) in Science, Technology, Engineering, or Mathematics.
(Q) That’s great! So if my organization has some students and I purchase a membership in MSDN AA, does that mean that I can distribute MSDN AA software to all of my organization members?
(A) Unfortunately, not. We restrict the use of MSDN AA software to students and faculty currently taking or teaching STEM courses.
(Q) What if I am a commercial organization with a legal MSDN AA membership distributing MSDN AA software to my students and faculty only – can they do commercial work with the software?
(A) No. Usage of MSDN AA software is always limited to non-commercial academic use regardless of the channel it was obtained from.
(Q) What if I build a new software product for an academic research project. Can I sell the product commercially after the project is completed?
(A) Sure, but only after you and all other members of your project team purchase commercial licenses of all products used to make the product.
(Q) Can I transfer machines with MSDN AA software to non-MSDN AA member departments in my University?
(A) Sure, but the EULA that you de-install the software prior to transfer. If MSDN AA software products are transferred to a non-MSDN AA department, it’s likely that their subsequent use will fall outside the terms and conditions described in the EULA.