Microsoft Office Licensing in SPLA

For Service Providers, hosting Microsoft Office is often viewed as a commodity—a simple add-on to a desktop-as-a-service offering. However, because Office is the most popular business software in the world, it is also the most scrutinized in audits.

In the Services Provider License Agreement (SPLA), Office licensing seems simple on the surface but contains hidden dependencies and strict edition rules. Furthermore, the introduction of the Flexible Virtualization Benefit (FVB) has completely changed how you can monetize Office hosting.

Below is your guide to navigating Office SALs, avoiding the "Pro Plus" trap, and leveraging the new BYOL rules.

1. The Standard SPLA Model: Subscriber Access Licenses (SAL)

In the standard SPLA model, Microsoft Office (Standard or Professional Plus) is licensed by User.

The Rule: You must report an Office SAL for every unique individual authorized to access the software.
Authorization vs. Concurrency: SPLA does not support concurrent licensing. If 50 users are in the Active Directory group that grants access to Office, you must pay for 50 SALs, even if only 5 users are logged in at any given moment.
Zero-Use Rule: Even if a user does not actually open the software, if they are "authorized" to do so, the license is required.

2. The Hidden Cost: The "Double Tax" of RDS

A critical factor often overlooked by new Service Providers is that you rarely host Office in a vacuum. To allow a user to access Office on a hosted server, they almost always utilize Remote Desktop Services (RDS).

The Dependency: You cannot use the SPLA Office SAL to cover the remote access capability.
The Math: For every user accessing hosted Office, you generally need to report two licenses:

Office SAL (for the application).
RDS SAL (for the access to the GUI).

3. Common Compliance Pitfalls

Auditors frequently target Office because errors here scale linearly with user counts.

1. The "Pro Plus" Trap

Microsoft offers two main editions in SPLA: Office Standard and Office Professional Plus.

The Mistake:Service Providers often install the "Professional Plus" image because it is easier to find or includes Access, but they only report the cheaper "Standard" SAL because they think the customer isn't using the extra features.
The Rule: You must pay for what is installed. If Office Professional Plus is installed on the server, you must report the Professional Plus SAL for all users, even if they only use Word and Excel.

2. The "Automation" Error

Some providers host applications that use Excel or Word in the background to generate reports (server-side automation), where the user never sees the Office interface.

The Rule: If the user benefits from the functionality of the Office software (e.g., receiving an Excel report generated by the server), they are considered a user of the software. A SAL is required for every user accessing the solution, regardless of whether they see the desktop interface.

4. Special Scenario: The Flexible Virtualization Benefit (FVB)

Before late 2022, bringing a customer's own Office license (like Office 365) to a shared SPLA environment was highly restricted and required specific "SCA" (Shared Computer Activation) partners. The Flexible Virtualization Benefit has democratized this.

The Scenario: The Microsoft 365 Customer Your customer, BizCorp, already pays for Microsoft 365 Apps for Enterprise (formerly Office 365 ProPlus) for their 100 employees. They want a hosted desktop experience but do not want to pay you an extra fee for SPLA Office licenses.

The New Rules (FVB):

1. Eligibility: You must be an Authorized Outsourcer (any provider who is not a Listed Provider like AWS, Google, or Alibaba).

2. Deployment: You can host Microsoft 365 Apps on your shared multi-tenant servers.

3. Requirements:

The customer uses their own subscription licenses.
Shared Computer Activation (SCA): The installation must utilize the Shared Computer Activation feature to ensure the activation token travels with the user, not the hardware.

4. Reporting: You do not report Office SALs on your SPLA.

5. Windows Dependency: If hosting on Windows Server, the customer still needs RDS CALs with SA (or equivalent subscriptions). If hosting on Windows 10/11 (via FVB), they need Windows Enterprise E3/E5.

Why this matters: This allows you to separate the Infrastructure (which you sell) from the Software (which the customer buys from Microsoft). It lowers the monthly bill for the customer, making your hosting solution more competitive against on-premise hardware.

Streamline Office Licensing with Octopus Cloud

With Octopus Cloud, service providers can confidently host Microsoft Office while staying fully compliant.

By leveraging the Flexible Virtualization Benefit and supporting customer-owned Microsoft 365 subscriptions via Shared Computer Activation, Octopus Cloud simplifies licensing, reduces audit risk, and ensures your hosted solutions remain efficient, scalable, and competitive.

Find out more about it here.