About

Contracting with Microsoft

Published: April 25, 2003 | Updated: October 13, 2009

In the last several years, procurement processes at Microsoft have become more and more streamlined. This means we can put the focus on what is most important—choosing qualified vendors and developing relationships with them that enable us all to grow toward our potential.

Standard agreements and tools save everybody time and concern.

The Microsoft Master Vendor Agreement and the Vendor Guidelines (formerly the Program Administrative Guidelines (a.k.a. PAG)) are the two documents and the key policies central to contracting with Microsoft.

The Microsoft Master Vendor Agreement (MMVA)

If such a contract is required by Microsoft, this contract must be duly executed by Microsoft and the vendor prior to doing any work. Because it is an overarching agreement, once the vendor has signed this Agreement, no further contracts are needed for work performed (other than specific statements of work depending on the nature of the project). Having a uniform agreement in place helps ensure that Microsoft can consistently rely on certain aspects of its relationships with vendors without discussion or concern, which frees both parties up for more critical activities—like completing the work! The MMVA outlines, in addition to other things, the following:

Standard purchase order and payment terms, which include 2% 10/Net 60.
Tier X reporting, which helps Microsoft ensure that all vendors at all levels are doing everything they can to ensure as much diversity as possible within the supply chain.

The Vendor Guidelines (formerly the Program Administrative Guidelines)

Note: Vendors who sign an MMVA with Microsoft will be obligated to comply with the terms of the Vendor Guidelines. Vendors who have signed a Microsoft Vendor Program Agreement or other similar agreement that expressly references the PAG are obligated to comply with the terms of the Program Administrative Guidelines.

The Vendor Guidelines, an adjunct to the Microsoft Master Vendor Agreement, outlines the requirements vendors are expected to follow, including

Microsoft travel policy. Required for all reimbursable travel, the vendor travel policy is consistent with employee travel policy and enables the supplier to take advantage of the Microsoft travel program and associated negotiated pricing.
Vendor code of conduct. Because Microsoft is committed to promoting a positive work environment, we expect our vendors and their employees, agents, and subcontractors to adhere to the same standards of conduct and behavior that we expect from our own employees while they are on Microsoft property or doing business with Microsoft. This code of conduct is part of the vendor contract with Microsoft and is intended to assist vendors in functioning smoothly and efficiently while performing work for Microsoft.
Pre-placement policy. Required of all contingent staffing agencies and other vendors with employees who will be accessing Microsoft facilities or networks, this is a basic background check process that helps ensure the safety and security of Microsoft physical and electronic assets as well as all other individuals working for Microsoft.
Statement of Work (SOW) parameters. A SOW helps ensure that expectations are understood and agreed upon by all parties up front. Each SOW should include price, delivery dates, and specifications for the work. Legal term should not be included in a SOW.

Downloads

File Name	Overview	Date Published
Microsoft Vendor Guidelines Microsoft Vendor Guidelines.pdf 212 KB PDF file	Full policy and procedure requirements for vendors providing products and services to Microsoft. Vendors who sign an MMVA must comply with these guidelines.	December 17, 2012
Microsoft Vendor Travel Policy Microsoft Vendor Travel Policy.pdf 100 KB PDF file	Full policy and procedure requirements for vendor travel. Vendors who sign an MMVA must comply with these guidelines.	July 17, 2012
Vendor Code of Conduct Vendor Code of Conduct.pdf 135 KB PDF file	Full requirements of the standards of conduct that vendors must follow.Other languages available here.	December 30, 2012
Microsoft Master Vendor Agreement Microsoft Master Vendor Agreement.pdf 499 KB PDF file	Engagement agreement that must be signed by vendors and authorized agents of Microsoft.	July 6, 2011