Contracting with Microsoft
Published: April 25, 2003 | Updated: June 03, 2013
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/suppliers and developing relationships with them that enable us all to grow toward our potential. A transition from using the term “vendor” to “supplier” is underway; accordingly you can expect to see both terms used interchangeably.
Standard agreements and tools save everybody time and concern.
The Master Supplier Services Agreement (formerly the Microsoft Master Vendor Agreement) and the Vendor Guidelines (formerly the Program Administrative Guidelines (PAG) are the two documents and the key policies central to contracting with Microsoft.
The Master Supplier Services Agreement (MSSA)
If such a contract is required by Microsoft, this contract must be duly executed by Microsoft and the vendor/supplier prior to doing any work. Because it is an overarching agreement, once the vendor/supplier 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/suppliers without discussion or concern, which frees both parties up for more critical activities—like completing the work! The MSSA 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/suppliers 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/suppliers who sign an MSSA with Microsoft will be obligated to comply with the terms of the Vendor Guidelines. Vendors/suppliers 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 Master Supplier Services Agreement, outlines the requirements vendors/suppliers are expected to follow, including
Microsoft travel policy. Required for all reimbursable travel, the vendor/supplier 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/suppliers 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/supplier contract with Microsoft and is intended to assist vendors/suppliers 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.
|File Name||Overview||Date Published|
Microsoft Vendor Guidelines
Microsoft Vendor Guidelines.pdf
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
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
Full requirements of the standards of conduct that vendors must follow. Other languages available here.
December 30, 2012
Master Supplier Services Agreement
Master Supplier Services Agreement.pdf
Engagement agreement that must be signed by vendors/suppliers and authorized agents of Microsoft.
June 3, 2013
Get Adobe Acrobat Reader (Adobe.com)
For More Information