Microsoft Product Terms: What You Need to Know

Microsoft Product Terms is the central document that governs how organizations can use software acquired through Microsoft's volume licensing programs. Whether you hold an Enterprise Agreement, use the Cloud Solution Provider program, or operate under a Services Provider License Agreement, the Microsoft Product Terms define your rights and restrictions.

This guide breaks down the structure, key provisions, and compliance implications of the Product Terms document. This is educational content, not legal advice. For specific licensing questions, consult a Microsoft licensing specialist or intellectual property attorney.

What Are Microsoft Product Terms?

Microsoft Product Terms (formerly known as the Product Use Rights, or PUR) is a comprehensive legal document published by Microsoft that specifies the terms and conditions under which organizations may use Microsoft software and online services obtained through volume licensing.

The document serves several critical functions:

• Defines use rights for every product available through volume licensing
• Specifies licensing metrics (per-core, per-user, per-device) for each product
• Sets restrictions on redistribution, hosting, and external use
• Incorporates data protection and privacy commitments
• Establishes geographic and industry-specific licensing variations

The Microsoft Product Terms apply to all major volume licensing programs, including Enterprise Agreements (EA), Microsoft Customer Agreements (MCA), Cloud Solution Provider (CSP), Services Provider License Agreement (SPLA), and Open Value agreements. They do not govern retail purchases or consumer subscriptions, which are covered by separate End User License Agreements.

Structure of the Microsoft Product Terms Document

The Product Terms document is organized into several major sections. Understanding this structure helps you locate the provisions relevant to your deployment.

Universal License Terms

This section contains terms that apply across all volume licensing products. Key provisions include:

• License assignment rules: How licenses must be assigned to devices or users, and minimum assignment periods (typically 90 days)
• Reassignment restrictions: When and how you can move a license from one device or user to another
• Multiplexing rules: Clarification that indirect access through hardware or software that pools connections still requires proper licensing
• Outsourcing rights: Conditions under which third parties can manage licensed software on your behalf
• License mobility: Rules for moving server licenses across server farms

Product-Specific Terms

Each Microsoft product family has its own section detailing:

1. Licensing model: Whether the product is licensed per-core, per-user, per-device, or by another metric
2. Edition differences: What distinguishes Standard from Enterprise, or E3 from E5
3. Use rights: Specific activities permitted under the license
4. Restrictions: Activities that are explicitly prohibited
5. Included components: Additional software or services bundled with the license

Online Services Terms

A dedicated section covers cloud and online services such as Microsoft 365, Azure, Dynamics 365, and Power Platform. These terms address:

• Service level agreements and uptime commitments
• Data location and sovereignty provisions
• Customer data handling and deletion policies
• Security incident notification requirements
• Acceptable use policies

Data Protection Addendum (DPA)

The DPA is incorporated by reference into the Product Terms and addresses Microsoft's obligations as a data processor under privacy regulations including the GDPR and CCPA. It covers data processing scope, sub-processor management, security measures, breach notification, and data subject rights assistance.

Key Provisions Every Organization Should Understand

Several provisions in the Microsoft Product Terms frequently cause confusion or lead to compliance issues. These deserve close attention.

License Mobility Through Software Assurance

License Mobility allows organizations with active Software Assurance to deploy certain server applications in shared hosting environments or third-party data centers. However, not all products qualify. Windows Server, for example, does not have License Mobility rights, meaning it cannot be deployed in a third-party environment under standard volume licensing terms.

Products that typically include License Mobility:

• SQL Server
• Exchange Server
• SharePoint Server
• Skype for Business Server
• System Center
• Dynamics 365 Server

Virtualization Rights

The Product Terms define specific virtualization rights that vary by product and edition. For Windows Server Datacenter, you receive unlimited virtualization rights on the licensed host. For Windows Server Standard, you receive rights for up to two virtual machines per license set.

Understanding these distinctions is critical for:

• Capacity planning in virtual environments
• Avoiding under-licensing during VM migrations
• Properly licensing disaster recovery environments
• Managing dynamic workload placement in clustered configurations

External User Access

When your licensed software is accessed by users outside your organization (customers, partners, vendors), the Product Terms impose specific requirements. Some products require External Connector licenses or per-user SALs (Subscriber Access Licenses) for each external user.

The rules differ significantly between:

• Internal users (your employees and on-site contractors)
• Authenticated external users (partners accessing a portal)
• Anonymous external users (public website visitors)

Misunderstanding external access rights is one of the most common sources of licensing non-compliance discovered during audits.

Government and Education Licensing

The Product Terms include specific provisions for government and academic institutions. These sectors often receive modified terms, reduced pricing, and additional use rights. However, these benefits come with strict eligibility requirements. An organization must qualify under Microsoft's definitions, which reference specific government entity types and educational accreditation standards.

Microsoft Product Terms and Data Privacy Obligations

The Microsoft Product Terms intersect with data privacy law in several important ways. Organizations using Microsoft products to process personal data must understand both their licensing terms and their regulatory obligations.

GDPR Alignment

Under Article 28 of the GDPR, any organization using Microsoft cloud services as a data processor must ensure adequate contractual protections exist. The Data Protection Addendum within the Product Terms is designed to satisfy this requirement. It specifies:

• Microsoft's role as a data processor or sub-processor
• The categories of personal data processed
• Technical and organizational security measures
• Data breach notification timelines (Microsoft commits to notification without undue delay)
• Sub-processor disclosure and change notification procedures

CCPA Considerations

For organizations subject to the California Consumer Privacy Act, the Product Terms clarify that Microsoft acts as a service provider (as defined under the CCPA) when processing customer data through its online services. This distinction is important because service providers are not considered to be "selling" personal information under the CCPA framework.

Building Your Own Privacy Documentation

While the Microsoft Product Terms cover Microsoft's obligations as a processor, your organization still needs its own privacy documentation for end users. A privacy policy generator helps create the foundational document that explains how your organization collects, uses, and shares personal data across all your tools and services, including Microsoft products.

If your website uses cookies for analytics, advertising, or functionality, you also need a comprehensive cookie policy that discloses these tracking technologies to visitors in compliance with the GDPR's consent requirements and the ePrivacy Directive.

Compliance Audits and Microsoft Product Terms

Microsoft's volume licensing agreements include audit rights, and the Product Terms define the scope of what auditors can examine.

Audit Triggers

While Microsoft does not publicly disclose its audit selection criteria, common triggers include:

• Significant changes in license ordering patterns (sudden decreases)
• Mergers, acquisitions, or divestitures
• Anonymous tips or competitor complaints
• Routine random selection
• License true-up discrepancies in Enterprise Agreements

Self-Assessment Programs

Microsoft offers a Software Asset Management (SAM) engagement program as an alternative to formal audits. SAM engagements are positioned as collaborative reviews rather than adversarial audits, though they still require full disclosure of your deployment environment.

Benefits of proactive SAM engagement include:

• More collaborative tone than a formal audit
• Opportunity to optimize your licensing before penalties apply
• Access to Microsoft licensing experts who can recommend cost-saving configurations
• Demonstrated good faith that may influence future audit decisions

Preparing for Compliance Reviews

Organizations should maintain ongoing readiness for potential audits by:

1. Running automated discovery tools quarterly to inventory all Microsoft deployments
2. Reconciling deployed software against purchased licenses
3. Documenting all license assignments, reassignments, and retirements
4. Keeping records of Software Assurance renewal dates and coverage
5. Maintaining clear documentation of virtualization configurations

How Microsoft Product Terms Change Over Time

One of the most important characteristics of the Microsoft Product Terms is that they are updated monthly. Each update can introduce new products, modify existing use rights, adjust licensing metrics, or add restrictions.

Tracking Changes

Microsoft publishes a change summary with each monthly update, highlighting modifications from the previous version. Organizations should:

• Subscribe to Microsoft licensing update notifications
• Review the change summary each quarter at minimum
• Assess whether changes affect current deployments
• Update internal compliance documentation accordingly
• Brief procurement and IT teams on material changes

Version Applicability

A critical nuance of the Product Terms is the "version applicable at the time of order" rule. When you place a license order, the Product Terms in effect at that time govern those specific licenses. This means your organization may simultaneously hold licenses governed by different versions of the Product Terms if orders were placed months or years apart.

This versioning system has practical implications:

• Newer versions sometimes expand use rights, which can be beneficial
• Newer versions can also add restrictions that affect future orders
• Organizations can choose to order under favorable terms before a change takes effect
• License renewals and true-ups may trigger application of current terms

Recent Notable Changes

Microsoft has made several significant changes to the Product Terms in recent years:

• Tightened restrictions on running licensed software in "Listed Provider" environments (major public cloud providers other than Azure)
• Introduced new licensing requirements for AI-powered features and Copilot integrations
• Updated data residency commitments for EU Data Boundary compliance
• Modified virtualization stacking rights for certain server products
• Added terms governing the use of Microsoft products with open-source software

Practical Steps for Managing Microsoft Product Terms Compliance

Managing compliance with the Microsoft Product Terms requires ongoing attention rather than a one-time review. Here are actionable steps for organizations of any size.

Establish a Licensing Governance Process

Assign a specific person or team as the owner of Microsoft licensing compliance. This role should:

• Monitor Product Terms updates monthly
• Maintain an accurate software asset inventory
• Approve all new Microsoft product deployments
• Coordinate with procurement on license orders and true-ups
• Serve as the point of contact for any audit activity

Use Automation Tools

Manual tracking of Microsoft licenses across complex environments is error-prone and time-consuming. Invest in:

• Software asset management platforms that automatically discover Microsoft deployments
• License optimization tools that identify savings opportunities
• Compliance dashboards that compare entitlements against actual usage
• Alerting systems that flag potential compliance gaps before audits

Align Licensing With Legal Compliance

Your Microsoft licensing compliance program should work in tandem with your broader legal compliance efforts. For organizations subject to the GDPR, CCPA, or other data protection regulations, ensure that your Microsoft deployment configuration aligns with the data processing commitments in the DPA.

TermsBox helps organizations manage their website compliance obligations alongside software licensing. Its automated compliance scanner can identify privacy policy gaps and cookie consent issues that may arise from Microsoft services embedded in your website.

Review Contracts Holistically

The Microsoft Product Terms do not exist in isolation. They interact with:

• Your specific volume licensing agreement (EA, MCA, CSP enrollment)
• Any amendments or special terms negotiated with Microsoft
• The Data Protection Addendum
• Online Services-specific SLAs
• Work orders and statements of work with Microsoft partners

Reviewing these documents together provides a complete picture of your rights and obligations. If your organization uses a terms of service generator for your own customer agreements, ensure those terms do not make promises about Microsoft products that exceed what the Product Terms permit. Likewise, if you license your own software to end users, you can create an end user license agreement that sets those terms independently of Microsoft's.

Frequently Asked Questions

What are Microsoft Product Terms?

Microsoft Product Terms is the official document that defines the use rights, restrictions, and conditions for all Microsoft commercial volume licensing products. It is updated monthly and applies to Enterprise Agreements, CSP, SPLA, and other volume licensing programs.

How often are Microsoft Product Terms updated?

Microsoft updates the Product Terms document on the first of each month. Changes can include new product additions, revised use rights, updated data processing terms, and modified licensing metrics. Organizations should review updates quarterly at minimum.

Are Microsoft Product Terms the same as an EULA?

No. An EULA (End User License Agreement) applies to retail and individual software purchases, while the Product Terms apply specifically to commercial volume licensing programs. The Product Terms are more detailed, cover a wider range of products, and are updated more frequently than a standard EULA.

What happens if you violate Microsoft Product Terms?

Violations can result in license compliance audits, back-dated licensing fees, financial penalties, agreement termination, and in severe cases, intellectual property infringement claims. Microsoft has the contractual right to audit any volume licensing customer.