If you are running a terminal server environment and wondering which Office 365 version can be used on a terminal server, you are not alone. This is one of the most commonly misunderstood areas of Microsoft licensing for UK small and medium businesses, and getting it wrong can expose your organisation to compliance issues and unexpected costs.
Terminal servers, also known as Remote Desktop Services (RDS) hosts, allow multiple users to log in simultaneously and share a single Windows Server instance. Running Microsoft 365 apps in this kind of shared environment requires a specific type of licence, and not every plan supports it. This guide explains exactly what you need, what to avoid, and how to make the right choice for your business.
What Is a Terminal Server and Why Does Licensing Matter?
A terminal server is a centralised server running Windows Server with the Remote Desktop Services role enabled. Users connect remotely using Remote Desktop Protocol (RDP) clients and run applications directly on the server rather than on their own devices. This setup is popular with UK businesses that want centralised control, easier software management, and the ability to support remote or home workers without deploying full workstations.
The key licensing challenge here is that Microsoft Office and Microsoft 365 apps are traditionally licensed per device or per user for single-device use. When multiple users run the same software simultaneously on the same server, different licensing rules apply. Microsoft refers to this as a “shared computer” scenario, and it requires what is called Shared Computer Activation (SCA) to be enabled. Without SCA-eligible licensing, you are technically in breach of Microsoft’s licence terms.
This is not a minor technicality. Microsoft licence audits do happen, and UK businesses found to be non-compliant can face significant remediation costs. Understanding which plans support terminal server use is therefore a practical and financial necessity, not just an administrative formality.
Which Microsoft 365 Plans Support Terminal Servers?
Not all Microsoft 365 plans include the right to use Office apps in a shared computer or terminal server environment. The key requirement is that the plan must include Shared Computer Activation. Microsoft has made this relatively straightforward by including SCA support in their business and enterprise plans that include the full desktop Office applications.
The plans that support terminal server deployment with Shared Computer Activation include Microsoft 365 Business Premium, Microsoft 365 Apps for Business, Microsoft 365 Apps for Enterprise, Microsoft 365 E3, and Microsoft 365 E5. Older Office 365 equivalent plans such as Office 365 E3 and Office 365 E5 also qualify. What these plans share is the inclusion of the full, locally installed Microsoft 365 Apps (formerly known as Office 365 ProPlus).
It is worth noting that Microsoft 365 Business Basic does not qualify, as it only includes the web-based versions of Office apps and does not include the desktop Office suite. Similarly, Exchange Online standalone plans or any plan that excludes the desktop apps will not meet the requirements for a terminal server deployment.
| Microsoft 365 Plan | Includes Desktop Apps | Supports Terminal Server (SCA) |
|---|---|---|
| Microsoft 365 Business Basic | No | No |
| Microsoft 365 Business Standard | Yes | No |
| Microsoft 365 Business Premium | Yes | Yes |
| Microsoft 365 Apps for Business | Yes | Yes |
| Microsoft 365 Apps for Enterprise | Yes | Yes |
| Microsoft 365 E3 | Yes | Yes |
| Microsoft 365 E5 | Yes | Yes |
| Office 365 E3 | Yes | Yes |
| Office 365 E5 | Yes | Yes |
What About Microsoft 365 Business Standard?
This is where many UK businesses get caught out. Microsoft 365 Business Standard includes the full desktop Office applications and allows installation on up to five devices per user. However, it does not officially support Shared Computer Activation for use on terminal servers or Remote Desktop Session Hosts (RDSH).
Microsoft’s own documentation states that plans in the Business tier (Basic, Standard, and Premium below Apps for Business) have limitations around shared computer use, and Business Standard is not listed as a supported plan for RDS environments. If you are currently running Microsoft 365 Business Standard on a terminal server, you should review your licence compliance position carefully.
The upgrade path most commonly recommended for SMBs running RDS is to move to Microsoft 365 Business Premium or Microsoft 365 Apps for Business, both of which are reasonably priced at the time of writing and include Shared Computer Activation rights. If you are looking at broader cloud options for your business, our guide on Microsoft 365 covers the full range of plans in detail.
How Does Shared Computer Activation Work in Practice?
Shared Computer Activation is a licensing mode built into Microsoft 365 Apps that allows multiple users to run the Office applications from a single installation on one machine. Instead of the software being activated once for the device, it activates on a per-user basis each time someone logs in. Each user must sign in with their own Microsoft 365 credentials, and the activation is tied to their account rather than the hardware.
When a user logs into the terminal server and opens Word, Excel, or Outlook, Microsoft 365 checks that the user’s account has a valid licence that supports SCA. If it does, a temporary activation token is issued. This token is typically valid for a set period and is renewed each time the user signs in. If the user’s licence is removed or expires, the apps will enter a reduced functionality mode after a grace period.
From a deployment perspective, SCA is enabled during the Office installation using the Office Deployment Tool (ODT) or via Microsoft Endpoint Configuration Manager. You set a property in the configuration XML file to enable shared computer activation before deploying the Office suite to your terminal server. The process is straightforward for IT managers familiar with Microsoft tools, and Microsoft’s documentation provides step-by-step guidance for configuring this correctly.
- Each user logs in with their own Microsoft 365 account credentials
- Activation is per-user, not per-device
- A temporary token is issued and stored locally for that session profile
- Tokens refresh automatically on subsequent logins
- If a licence is removed, apps enter reduced functionality mode after a grace period
- SCA must be explicitly enabled during the Office installation process
Licensing Each User on the Terminal Server
A critical point that some businesses overlook is that every user who will access Microsoft 365 Apps on the terminal server must have their own qualifying Microsoft 365 licence. You cannot purchase a single Microsoft 365 Apps for Enterprise licence and use it for ten concurrent users. The licensing model requires one licence per named user, regardless of how many simultaneously connect to the server.
This is separate from your Windows Server CAL licensing and your RDS CALs. Those cover the right to connect to the server and use Windows-based services. The Microsoft 365 licence on top of that covers the right to use the Office applications themselves. Both sets of licences must be in place for a fully compliant terminal server environment.
For UK businesses procuring licences, Microsoft 365 plans are typically purchased through Microsoft directly, through UK cloud resellers such as Giacom, Sherweb, or Pax8, or through a Microsoft Cloud Solution Provider (CSP). Prices for qualifying plans such as Microsoft 365 Apps for Business typically start from around £8 to £10 per user per month in the UK at the time of writing, though pricing can vary by reseller and any active promotions. If you are also considering broader cloud infrastructure changes alongside your Office licencing review, the guide on Microsoft 365, Azure, Google Workspace and cloud migration is worth reading.
What Happens If You Use the Wrong Licence?
Using a Microsoft 365 plan that does not support Shared Computer Activation on a terminal server is a licence violation under Microsoft’s Product Terms. In practice, the software may still run in many cases, particularly if it was installed with device-based activation before the server became shared. However, this does not mean you are compliant, and the risk of running non-compliant software should not be underestimated.
Microsoft conducts licence audits, and software asset management is an increasing area of focus for IT governance in UK organisations. If found to be non-compliant, businesses may be required to retrospectively purchase the correct licences and may face penalties. Beyond the direct cost, the reputational and operational disruption of a compliance review is reason enough to get it right from the outset.
There is also a practical risk. Office applications installed without proper SCA configuration on a shared server can behave unpredictably. Users may encounter activation prompts mid-session, see errors when multiple users try to open Office at the same time, or experience issues when licences are not correctly validated. Getting the licensing right is not just a compliance matter; it also protects the stability of your users’ working environment.
- Non-compliant use is a breach of Microsoft’s Product Terms
- Retrospective licence purchases may be required following an audit
- Users may experience activation errors and Office instability
- Multiple simultaneous logins can cause licence conflicts without SCA
- IT governance requirements increasingly include software licence compliance
Practical Steps for IT Managers Setting Up Office 365 on a Terminal Server
If you are setting up Microsoft 365 Apps on a terminal server for the first time, or auditing an existing deployment, here is a practical checklist to work through. The process follows Microsoft’s recommended deployment path and ensures both compliance and a stable user experience.
Start by confirming that every user who will log in to the terminal server holds a qualifying Microsoft 365 licence. This means Microsoft 365 Business Premium, Apps for Business, Apps for Enterprise, E3, or E5. If any users are on Business Standard or Business Basic, you will need to upgrade those licences before proceeding. Then download the Office Deployment Tool from Microsoft and create a configuration XML file that includes the SharedComputerLicensing value set to 1. Deploy the Office package to the server using this configuration.
Once deployed, verify that SCA is active by checking the registry key at HKEY_LOCAL_MACHINESOFTWAREMicrosoftOfficeClickToRunConfiguration and confirming that SharedComputerLicensing is set to 1. You can also verify user activation status using the ospp.vbs script or the Microsoft 365 Apps admin centre. It is good practice to test with a few user accounts before rolling out fully, particularly on live production servers.
- Confirm all users have a qualifying Microsoft 365 licence
- Download the Office Deployment Tool (ODT) from Microsoft
- Create a configuration XML file with SharedComputerLicensing set to 1
- Deploy Microsoft 365 Apps using the ODT configuration
- Verify SCA is active via the registry or admin centre
- Test with a small group of users before full rollout
- Monitor licence health through the Microsoft 365 admin centre
Key Takeaways
- Not all Microsoft 365 plans support use on a terminal server. You need a plan that includes Shared Computer Activation.
- Qualifying plans include Microsoft 365 Business Premium, Apps for Business, Apps for Enterprise, E3, and E5.
- Microsoft 365 Business Standard does not officially support terminal server or RDS use, despite including desktop apps.
- Every user accessing Office on the terminal server must hold their own individual qualifying licence.
- Shared Computer Activation must be explicitly enabled during Office deployment using the Office Deployment Tool.
- Running non-compliant licences on a terminal server risks audit penalties and user-facing activation errors.
- UK businesses can procure qualifying licences through Microsoft or UK-based CSP resellers such as Giacom or Pax8.
Related Guides
- Microsoft 365 Plans Explained for UK Businesses
- Microsoft 365, Azure, Google Workspace and Cloud Migration Guide
- On Prem vs Hosted Servers After End of Life
- Windows Server End of Life Checklist for Businesses
- Best Servers for Small Business in 2025
Frequently Asked Questions
Can I use Microsoft 365 Business Standard on a terminal server?
No, not in a compliant manner. Microsoft 365 Business Standard includes the full desktop Office applications, but it does not include rights for use via Shared Computer Activation on a Remote Desktop Services host or terminal server. To use Office apps in a shared server environment, you need to upgrade to Microsoft 365 Business Premium, Microsoft 365 Apps for Business, or one of the enterprise-tier plans that explicitly support SCA.
Does every user need their own Microsoft 365 licence on a terminal server?
Yes. Microsoft 365 licensing is per named user, not per server or per concurrent session. Every individual who will access Microsoft 365 Apps through the terminal server must hold their own qualifying licence. There is no concurrent user or server-based licensing model available for Microsoft 365 Apps. This is a common source of confusion for businesses transitioning from older volume licence agreements.
What is Shared Computer Activation and do I need to enable it manually?
Shared Computer Activation is a Microsoft technology that allows multiple users to run Microsoft 365 Apps from a single installation on a shared computer or server. It activates Office on a per-user basis rather than per-device. Yes, you do need to enable it manually. It is not active by default. You enable it by setting the SharedComputerLicensing property to 1 in your Office Deployment Tool configuration XML before deploying the apps to the server.
What happens if a user’s Microsoft 365 licence expires while they are using a terminal server?
If a user’s licence expires or is removed, Microsoft 365 Apps will continue to function normally during a short grace period. After that, the apps will enter reduced functionality mode, which means users can open and view existing files but cannot create or edit documents. To restore full functionality, the licence must be reinstated and the user must sign in again to trigger a fresh activation. Monitoring licence status through the Microsoft 365 admin centre is therefore important in an RDS environment.
Can I use a perpetual Office licence such as Office 2021 on a terminal server instead?
Yes, perpetual versions of Office such as Office LTSC 2021 or Office 2019 can be used on terminal servers, but they require volume licensing under a Microsoft Open or Microsoft 365 volume agreement with appropriate Software Assurance or LTSC rights that cover RDS use. Standard retail or OEM perpetual Office licences do not cover use on a terminal server. If you are considering this route, speak with a Microsoft licensing specialist or a UK-based CSP to confirm the correct agreement type for your situation.
Related Posts
- What Is Microsoft 365?
- Microsoft 365 for Small Business UK: Is It Worth It?
- Microsoft 365 vs Google Workspace
- Microsoft 365, Azure, Google Workspace and Cloud Migration
- Azure vs AWS vs Google Cloud for UK SMEs
- What Is Google Workspace?
