Search Google Appliance

Information Technology

Microsoft Campus Agreement - End User License Agreement

These license terms apply to your use of all Microsoft software and online services licensed under your volume license agreement.

Your Use Rights. If you comply with your volume license agreement, including these product use rights and the Product List, you may use the software and online services only as expressly permitted in these product use rights.

Rights to Use Other Versions. License terms for certain products permit use of one or more copies or instances at a time. For any of these products, for any permitted copy or instance, you may create, store and run in place of the version licensed, a copy or instance of a

  • Prior version
  • Different permitted language version
  • Differently available platform version (for example, 32 bit or 64 bit)
  • You may not use different versions of different components, such as server software and additional software, unless the license terms for the product expressly permit you to do so.

Third Party Software. If other terms come with software licensed by a third party, those terms determine your rights to use it and any other related rights or remedies you have.

Pre-release Code. If other terms come with pre-release code, those terms apply to your use of it.

Updates and Supplements. We may update or supplement the software you license. If so, you may use that update or supplement with the software. If other terms come with an update or supplement, those terms apply to your use of it.

No Commercial Hosting. You may not host the products for commercial hosting services.

Other Rights. Rights to access the software on any device do not give you any right to implement Microsoft patents or other Microsoft intellectual property in software or devices that access that device.

Documentation. Any person that has valid access to your computer or internal network may copy and use the documentation for your internal reference purposes. Documentation does not include electronic books.

Product Activation. Some products and online services require activation and a Volume License key to install or access them. Activation associates the use of the software with a specific device. For information about when activation or a key is required, see the Product Activation section on http://www.microsoftvolumelicensing.com/. You are responsible for both the use of keys assigned to you and activation of products using your Key Management Service (KMS) machines. You should not disclose keys to third parties.

For more information, see http://www.microsoft.com/licensing/existing-customers/product-activation.aspx. By using the software, you consent to the transmission of this information. Before you activate, you have the right to use the version of the software installed during the installation process. Your right to use the software after the time specified in the installation process is limited unless it is activated. This is to prevent its unlicensed use. You are not licensed to continue using the software after that time if you do not activate it. If the device is connected to the Internet, the software may automatically connect to Microsoft for activation. You can also activate the software manually by Internet or telephone. If you do so, Internet and telephone service charges may apply. Some changes to your computer components or the software may require you to reactivate the software. The software will remind you to activate it until you do.

  1. KMS and Multiple Activation Key (MAK) Activation. During Multiple Activation Key (MAK) activation, the software will send information about the software and the device to Microsoft. During Key Management Service (KMS) host activation, the software will send information about the KMS host software and the host device to Microsoft. KMS client devices activated using KMS do not send information to Microsoft. However, they require periodic reactivation with your KMS host. The information sent to Microsoft during MAK or KMS host activation includes:
    • the version, language and product key of the software
    • the Internet protocol address of the device
    • information derived from the hardware configuration of the device.
  2. Proper Use of KMS. You may not provide unsecured access to your KMS machines over an uncontrolled network such as the Internet.
  3. Unauthorized Use of MAK or KMS Keys. Microsoft may take any of these actions related to unauthorized use of MAK or KMS keys:
    • prevent further activations
    • deactivate
    • otherwise block the key from activation or validation.
    • Key deactivation may require the customer to acquire a new key from Microsoft.

Additional Functionality. We may provide additional functionality for the products. Other license terms and fees may apply.

Using More than One Product or Functionality Together. You need a license for each product and separately licensed functionality used on a device or by a user. For example, if you use Office on Windows, you need licenses for both Office and Windows. Likewise, to access Remote Desktop Services in Windows Server you need both a Windows Server CAL and a Remote Desktop Services CAL.

Font Components. While the software is running, you may use its fonts to display and print content. You may only

  • embed fonts in content as permitted by the embedding restrictions in the fonts; and
  • temporarily download them to a printer or other output device to print content.

.NET Framework and PowerShell Software. The software for the products listed below contains Microsoft .NET Framework software and may contain PowerShell Software. Other products may also contain .NET Framework software or PowerShell Software. These software components are part of Microsoft Windows. Except as provided in Benchmark Testing below, the license terms for Microsoft Windows apply to your use of these components.

  • BizTalk Server
  • Customer Care Framework
  • MSDN
  • SQL Server
  • System Center Essentials and System Center Essentials with SQL Server Technology
  • Visual Studio (all editions) with and without MSDN
  • Visual Studio Team Foundation Server

Benchmark Testing.

  • Software. You must obtain Microsoft’s prior written approval to disclose to a third party the results of any benchmark test of the server software or additional software that comes with it. This applies to products in the Microsoft Servers or Microsoft Developer Tools licensing models (see Table of Contents). This does not apply to the .NET Framework (see below) or to the following products: Class Server, Live Communications Server, Systems Center Operations Manager, System Center Data Protection Manager, System Center Essentials, Systems Management Server, Virtual Server, Windows Server, Microsoft Services for Netware, Windows Small Business Server. It, however, does apply to SQL Technology, in any, licensed with these products.
  • Microsoft .NET Framework. The software may include one or more components of the .NET Framework (".NET Components"). If so, you may conduct internal benchmark testing of those components. You may disclose the results of any benchmark test of those components, provided that you comply with the conditions set forth at http://go.microsoft.com/fwlink/?LinkID=66406. Notwithstanding any other agreement you may have with Microsoft, if you disclose such benchmark test results, Microsoft shall have the right to disclose the results of benchmark tests it conducts of your products that compete with the applicable .NET Component, provided it complies with the same conditions set forth at http://go.microsoft.com/fwlink/?LinkID=66406.

Multiplexing. Hardware or software you use to:

  • pool connections,
  • reroute information,
  • reduce the number of devices or users that directly access or use the product, or
  • reduce the number of operating system environments, devices or users the product directly manages, (sometimes referred to as "multiplexing" or "pooling"), does not reduce the number of licenses of any type that you need.

Distributable Code. The software or online service may include code that you are permitted to distribute in programs you develop if you comply with the terms below.

1.  Right to Use and Distribute. The code and text files listed below are "Distributable Code." These product use rights may provide rights to other Distributable Code.

  • REDIST.TXT Files. You may copy and distribute the object code form of code listed in REDIST.TXT files.
  • Sample Code. You may modify, copy, and distribute the source and object code form of code marked as "sample."
  • OTHER-DIST.TXT Files. You may copy and distribute the object code form of code listed in OTHER-DIST.TXT files.
  • Third Party Distribution. You may permit distributors of your programs to copy and distribute the Distributable Code as part of those programs.
  • Additional license terms for MSDN Universal, MSDN Premium, and Visual FoxPro 9.0.
    • MSDE 2000. Distributable Code includes Microsoft SQL Server 2000 Desktop Engine (MSDE 2000). You may copy and distribute the object code form of MSDE 2000.
  • Additional license terms for Products in the Developer Tools Section of these Product Use Rights. The software may also contain the following Distributable Code. You may
    • Microsoft Merge Modules. Copy and distribute the unmodified output of Microsoft Merge Modules;
    • MFCs, ATLs and CRTs. Modify the source code form of Microsoft Foundation Classes (MFCs), Active Template Libraries (ATLs), and C runtimes (CRTs) to design, develop and test your programs, and copy and distribute the object code form of your modified files under a new name;
    • MDAC. Copy and distribute the object code form of the MDAC_TYP.EXE file; and
    • Image Library. Copy and distribute images and animations in the Image Library as described in the software documentation. You may also modify that content. If you modify the content, it must be for use that is consistent with the permitted use of the unmodified content.

2.  Distribution Requirements. For any Distributable Code you distribute, you must

  • add significant primary functionality to it in your programs;
  • require distributors and external end users to agree to terms that protect it at least as much as your volume license agreement, including these product use rights and the Product List;
  • display your valid copyright notice on your programs; and
  • indemnify, defend, and hold harmless Microsoft from any claims, including attorneys’ fees, related to the distribution or use of your programs.

3.  Distribution Restrictions. You may not

  • alter any copyright, trademark or patent notice in the Distributable Code;
  • use Microsoft’s trademarks in your programs’ names or in a way that suggests your programs come from or are endorsed by Microsoft;
  • distribute Distributable Code, other than code listed in OTHER-DIST.TXT files, to run on a platform other than Microsoft operating systems, run-time technologies or application platforms;
  • include Distributable Code in malicious, deceptive or unlawful programs; or
  • modify or distribute the source code of any Distributable Code so that any part of it becomes subject to an Excluded License. An Excluded License is one that requires, as a condition of use, modification or distribution, that:
    • the code be disclosed or distributed in source code form, or
    • others have the right to modify it.

The following license terms apply to your use of products in the Microsoft Servers licensing models. They also apply to your use of Windows 7 software under licenses for which you have current Software Assurance coverage.

Instance. You create an "instance" of software by executing the software’s setup or install procedure. You also create an instance of software by duplicating an existing instance. References to software include "instances" of the software.

Run an Instance. You "run an instance" of software by loading it into memory and executing one or more of its instructions. Once running, an instance is considered to be running (whether or not its instructions continue to execute) until it is removed from memory.

Operating System Environment. An "operating system environment" is:

  • all or part of an operating system instance, or all or part of a virtual (or otherwise emulated) operating system instance which enables separate machine identity (primary computer name or similar unique identifier) or separate administrative rights, and
  • instances of applications, if any, configured to run on the operating system instance or parts identified above.

There are two types of operating system environments, physical and virtual. A physical operating system environment is configured to run directly on a physical hardware system. The operating system instance used to run hardware virtualization software (e.g. Microsoft Virtual Server or similar technologies) or to provide hardware virtualization services (e.g. Microsoft virtualization technology or similar technologies) is considered part of the physical operating system environment. A virtual operating system environment is configured to run on a virtual (or otherwise emulated) hardware system. A physical hardware system can have either or both of the following:

  • one physical operating system environment
  • one or more virtual operating system environments

Server. A server is a physical hardware system capable of running server software. A hardware partition or blade is considered to be a separate physical hardware system.

Assigning a License. To assign a license means simply to designate that license to one device or user.

No Separation of Software. You may not separate the software for use in more than one operating system environment under a single license, unless expressly permitted. This applies even if the operating system environments are on the same physical hardware system.

Physical and Virtual Processors. A physical processor is a processor in a physical hardware system. Physical operating system environments use physical processors. Solely for licensing purposes, A virtual processor is a processor in a virtual (or otherwise emulated) hardware system. Virtual operating system environments use virtual processors. A virtual processor is considered to have the same number of threads and cores as each physical processor on the underlying physical hardware system.

Maximum Instances. The software or your hardware may limit the number of instances of the software that can run in physical or virtual operating system environments on a device.

Please remember: The terms and conditions of your volume license agreement, and the product use rights documented in that agreement, govern your use of products licensed from Microsoft. While we have endeavored to facilitate your access to and understanding of the product use rights through this online tool, your use of this site should not serve as a substitute for reading and understanding your volume license agreement. We will work to keep the contents of this site consistent with the governing volume license documentation, but in the case of conflicting content, you should refer to the terms and conditions of your agreement.

If you acquire licenses under the GSA our GIA programs, please contact your reseller or Microsoft licensing executive for the applicable license agreement/product use rights.

Note: Because of the way that the Product Use Rights are designed, some provisions may appear that relate to other products, as noted in these pages.