Microsoft SPUR: Understanding Service Provider Use Rights

SPUR, short for "Service Provider Use Rights," is a vital resource published by Microsoft. It breaks down, in detail, how Microsoft products acquired through SPLA can and cannot be used. This document is more than just a checklist—it’s the legal and operational roadmap that regulates what service providers are permitted (and prohibited) from doing with Microsoft software in a hosted environment.Microsoft’s technologies, from Windows Server to SQL Server and Microsoft 365, are governed by complex licensing frameworks. SPUR aims to make this complexity manageable. It provides clarity by documenting rights, restrictions, and obligations that specifically apply to hosted and managed environments operated by service providers. Whether you’re standing up virtual servers, running hosted Exchange, or serving remote desktops, SPUR is the authority you need to consult to operate compliantly and with confidence.

Microsoft SPUR is intentionally organized in a logical and user-friendly way. Its structure provides clarity and consistency, so licensees always know where to look for information.

Universal License Terms

At the very top of the SPUR hierarchy are the Universal License Terms. These are foundational statements that apply across all Microsoft products covered by SPLA and reflected throughout the SPUR. They address the big-picture, universal issues: general terms of use, common definitions, responsibilities regarding compliance, and rights of audit. For example, they might spell out that licensees are responsible for tracking software deployment and ensuring only authorized users have access.

Universal License Terms act as the ground rules. No matter which product or licensing model you’re working with, these terms always apply. They ensure that, regardless of new features, innovations, or licensing tweaks, there’s a backbone that enforces consistency across Microsoft’s broad product suite.

If you'd like to learn more, Microsoft provides dedicated articles and documentation for deeper understanding of the universal use rights found in SPUR. Here is an internal article to understand the universal use rights.

Licensing Models in SPUR

Licensing isn’t one-size-fits-all. To reflect how customers deploy and pay for services, Microsoft products in SPLA—and thus in SPUR—are licensed under different models. Each has its own rules, so it’s important to know which model applies to the product in question. The SPUR details three primary models:

1. Per Core Model:
   Many powerhouse products (think SQL Server, Windows Server) are licensed per processor core. Service providers report the number of physical or virtual cores being used for a particular product each month. This model allows scalable and predictable reporting in virtualized data center environments.
2. Per SAL Model (Subscriber Access License Model):
   This flexible model tracks users or devices (“subscribers”) granted access to a product or service. For applications such as Remote Desktop Services or hosted collaboration software, you need a SAL for each user or device authorized to use the service within the reporting month—regardless of actual usage.
   
   
3. Host/Guest Model::
   This model is often used for products designed to run in virtualized environments. The Host licenses the infrastructure, and Guest licenses cover the virtualized OS or application instances. This is common in desktop virtualization, where separating the rights of the host machine and VMs offers clarity.

By distinguishing these models, SPUR helps providers map their own service architectures to compliant licensing strategies.

While universal terms set the stage, the Product Specific Terms section is where most of the heavy lifting happens. Each Microsoft product has its own unique conditions and nuances.

What Does This Section Cover?

• Availability:

Not every Microsoft product is available under SPLA or for use in a hosted environment. Product Specific Terms clarify exactly which products can be licensed and under what conditions.

• Use Rights:

This is the meat of compliance. “Use rights” define precisely what you’re allowed to do with each product: installation, purposes of use, geographic scope, usage restrictions, and more.

• Licensing Model Rules:

Each product entry in SPUR dictates the specific licensing model (Per Core, Per SAL, etc.) applicable to that product and then describes the operational rules for service providers: counting users, servers, instances, or metrics necessary for reporting.

• Allowed Access Licenses:

Many products require additional licenses for users or devices to connect. The SPUR details which “access licenses” (like SALs) are allowed and any conditions for legitimate access. For example, using Exchange Server isn’t just about licensing the server—it’s about ensuring every mailbox is properly covered.

The Product Specific Terms section is indispensable for day-to-day service provider operations. When onboarding a new customer or deploying a new workload, it’s the checklist to follow—providing assurance that your licensing is up-to-date and that revenue reports will withstand an audit.

The Product Specific Terms are an integral component of SPUR, encompassing:

• Availability: Specifies which products are available for licensing.
• Use Rights: Outlines the rights pertaining to the usage of a specific product.
• Licensing Model Rules: Dictates the rules associated with the licensing models like Per Core, Per SAL, and Host/Guest.
• Allowed Access Licenses: Details the licenses that are permitted to access a given product by a user.

These terms serve as an all-encompassing guide, ensuring users are adeptly informed about their licensing agreements and are compliant.

The world of technology accelerates rapidly—Microsoft introduces new features, changes supported platforms, and occasionally redefines how products are licensed. That’s why SPUR is updated regularly, typically on a quarterly basis.

Every update is an opportunity (and a requirement) for service providers to review what’s changed. A product’s availability, use rights, or access model may shift unexpectedly. Relying on an old copy of SPUR is a sure way to wander into non-compliant territory. Staying current with SPUR is part of a compliance officer’s job—ignorance doesn’t absolve licensees from responsibility.

Subscribing to Microsoft partner newsletters, joining communities, or working with SPLA experts can help providers keep on top of these routine updates and avoid unwelcome surprises during audits.

If you’re thinking all this sounds complicated, rest assured that Microsoft has made major efforts to ensure that the SPUR is accessible online and easy to use.

How to Find Product Terms

1. Start at the SPUR Website:
   Microsoft hosts the SPUR documentation on a dedicated portal, making it the single stop for authoritative licensing information.
2. Search or Browse By Product:
   If you need details about, say, Exchange Server, head to the product index and select ‘Office Servers’. From there, you’ll see a breakdown by product family. Locate ‘Exchange Server’ in the list, and you’ll be presented with all the current terms that govern its use.
3. Explore Product-Specific Information:

Each product entry provides a comprehensive breakdown—availability, licensing model, use rights, access licenses, and more. All relevant sections are displayed in one view, and you can cross-reference universal terms as needed.

Viewing Historical Terms

Need to reconcile use rights from a prior year? Simply adjust the ‘Effective Date’ in the top right corner of the SPUR portal. This key feature allows you to look up what terms applied during previous periods—essential for multi-year contracts or when responding to audit queries.

Downloading and Printing

Microsoft understands documentation is sometimes best reviewed offline. The SPUR portal’s print icon (top right corner) provides options to download or print the entire document or just selected sections. This can be invaluable for sharing terms with stakeholders, maintaining compliance records, or assembling evidence during internal reviews or external audits.

Staying Compliant and Informed

For Microsoft partners and service providers, compliance with SPUR isn’t optional. It is the bedrock that safeguards both the provider and their end customers from licensing violations, audits, and potentially hefty penalties. A misstep in understanding service provider use rights can cost dearly in both dollars and reputational damage.

Adopting a habit of consulting SPUR regularly—whenever adding services, onboarding new customers, or updating existing solutions—is best practice. It adds rigor to service delivery and peace of mind to business operations.

Community Support

No one can be expected to be a licensing expert overnight. That’s why communities like the Octopus Cloud Community exist—to crowdsource answers, clarify tricky points, and exchange tips on navigating Microsoft licensing’s twists and turns. If you have any questions, don’t hesitate to reach out and ask. Sharing knowledge ensures everyone stays compliant and successful.

Microsoft SPUR is not just a compliance document—it’s an indispensable tool for anyone delivering Microsoft products under SPLA. By systematically explaining universal rights, specific product usage terms, and licensing models, it empowers service providers to make the right business decisions while protecting themselves from risk. So, next time you’re preparing a proposal or designing new offerings, let SPUR be your guide. If in doubt, check the latest SPUR, consult your peers, and never hesitate to ask questions. That’s the best way to thrive in the world of Microsoft licensing.