Several people share one company computer. Each has Microsoft 365 Business Standard. Word works for the first person who signs in, but others see an activation error. The issue may be licensing rather than installation: shared use requires the right user entitlement, activation mode and an account for each person.
When one says "shared computer license", three different rights are often mixed up. The first is the authorization of a specific person to use Microsoft 365 desktop applications. The second is Shared Computer Activation (SCA), a way to activate these applications in an environment where people take turns. The third is the right to use the operating system or remote infrastructure, for example Azure Virtual Desktop (AVD) or Remote Desktop Services (RDS). One correct answer to the first question does not automatically solve the remaining two.
When Shared Computer Activation is needed
SCA is intended for a computer where multiple people sign in to Microsoft 365 Apps under their own accounts. It can be a shared station in the office, a shared computer in a training room, or a remote desktop on a shared host. Microsoft explicitly mentions both physical shared computers and RDS in shared activation overview.
At login, the application requests their own license token for each authorized person. Just because Word has been activated by one colleague does not mean it is activated for others. SCA is not a single license purchased "per computer" for any number of users. Users have their own accounts and assigned corresponding licenses.
On a personal laptop that is used by only one person, there is usually no reason to turn on shared activation. It's the actual usage that matters, not the name of the device in your inventory.
Business Standard versus Business Premium
Microsoft 365 Business Standard includes desktop applications, but does not include Shared Computer Activation permissions. In a number of Business plans, it is supported by Business Premium, according to current Microsoft documentation. Other examples are eligible plans with Microsoft 365 Apps for enterprise, such as Office 365 E3. The exact product and rights must be verified with each target group.
| Scenario | What to solve with Office applications | Separate question |
|---|---|---|
| One employee on their own PC | A plan that includes desktop apps; standard user activation | Windows license and status on the device |
| Multiple employees on one PC | Each own account and license supporting SCA; SCA mode on | Device and access rights management |
| More people on the RDS host | SCA and appropriate Microsoft 365 Apps license for everyone | Windows Server/RDS license and version support |
| Shared desktop in AVD | SCA for Office on a shared host | AVD user entitlement and Azure costs |
| Personal virtual desktop | Assess if the host is actually sharing | Rights to the virtual desktop and its configuration |
The table describes the decision issues, not the full license agreement. In addition, current support matters for Windows Server, legacy systems, and individual host technologies. For example, Microsoft's guide to Office on RDS differentiates between application, user account, system, and connectivity requirements.
AVD and Office are not one license
Business Premium is among the products that Microsoft lists as entitlements for internal AVD users on supported client Windows. This does not mean that the entire virtual desktop is free of additional costs. Virtual machines, storage, and other Azure services are handled separately. AVD on Windows Server uses a different licensing model than client Windows. Microsoft distinguishes these variants in AVD Licensing.
Likewise, the right to enter a virtual desktop is not the same as the right to run desktop Word. If Office is to be on a shared host, both the application license and the activation mode must match. If there will be no Office in the virtual desktop at all, do not automatically infer the need for SCA from its deployment.
Don't be swayed by the phrase "we have Business Premium" at RDS. This applies to applications and their shared activation, it does not deal with rights to Windows Server and remote sessions. Before buying, draw the whole path on paper: user → host type → operating system → application → activation mode.
How shared activation is set up
The simplest approach is to plan SCA when deploying the apps via the Office Deployment Tool. In the Office Customization Tool, you select a shared computer; in the configuration file corresponds to the SharedComputerLicensing setting with the value 1. Microsoft also describes the options for changing an existing installation without reinstalling. After the change, the device must be restarted. If the application was activated before SCA was turned on, it may be necessary to reset the original activation.
Don't blindly make a fleet-wide registry change. First, verify the pilot device and two different users with their regular accounts. An administrator logging in with a different license may not reveal the error that the employee will see.
SCA also needs a reliable connection to the Office Licensing Service. For RDS or virtual desktops, therefore, test not only the launch of Word on the day of installation, but also repeated logins and reactivation according to Microsoft's requirements for RDS deployment.
Troubleshooting Office activation on a shared PC
Proceed in this order:
- Describe the host. Is it a physical shared PC, an RDS session, a shared virtual desktop, or a personal VM?
- Verify the specific user. Does this person have a license assigned with desktop applications and the right to SCA? Are they signing into Office with his own account?
- Check installation mode. Is SCA actually enabled on the host and did the change take effect after a reboot?
- Check the token and connection. Can the host connect to the license service? Did the old activation method leave a token that needs to be reset?
- Test another account. One successfully activated user does not verify the entire group.
- Separate other errors. When AVD or RDS access fails before Office starts, address this layer first.
This sequence prevents the frequent shortcut: buy another license, even if the host configuration is causing the problem. The opposite is also true — switching SCA alone will not fix the missing license authority.
A practical example
A hypothetical company has eight people and two shared computers. They all work in desktop Word and Excel. Four have Business Premium, four Business Standard. The first four have a plan supporting SCA. The second one has desktop applications, but Business Standard is not enough for this method of activation. It is not right to buy a single additional Business Premium "per computer". The business must resolve the permissions of the individual people who actually use the applications on the shared stations, and then turn on and authenticate SCA.
If the same people start working through AVD, there will be more decisions about host type and right to virtual Windows. The number of two physical computers is no longer the main data for Office licensing. The basis is a list of users and their work scenarios.
Frequently asked questions
Can Business Standard be activated on a shared PC if it already has Word?
Business Standard includes desktop applications, but according to Microsoft, it does not support Shared Computer Activation mode. For a scenario where users rotate on one PC, choose a plan with the appropriate permission for each of them.
Is one Business Premium license per shared computer enough?
No. SCA obtains a token for a specific logged-in user. Each person using the application needs their own corresponding license and account.
Does Business Premium mean AVD costs nothing?
No. An eligible user license for certain internal scenarios does not cover virtual machines, storage, or other Azure resources. Also distinguish between client Windows and Windows Server.
Does a personal virtual desktop have to have SCA?
If the virtual machine is assigned to a single person and not shared, Microsoft provides a scenario without SCA in the RDS Guide. Assess specific topology and product rights.
Where do I start when Office reports an activation error?
For the affected user license, installation mode and connectivity to the license service. Only then decide whether it is an AVD or RDS problem. Record the exact error and host type.
What to check before you decide
For shared Office, asking "how many computers do we have" is not enough. List who is working on them, what is running, and where the host is running. Only then compare user licenses, set up SCA and check Windows and remote desktop rights separately. If you are also dealing with the basic device license, our article on Business Premium and Windows Home/Pro continues.
