Content reviewed: 12 October 2026

Shared Microsoft 365 Apps requires three separate checks: the user’s desktop-app entitlement, the activation model, and the host’s Windows or remote-access rights. Shared Computer Activation (SCA) handles activation for eligible users on a shared host. Azure Virtual Desktop (AVD) and Remote Desktop Services (RDS) have their own access and infrastructure requirements.

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

Business Standard includes desktop apps but does not support SCA. Microsoft’s current overview lists Business Premium and plans containing Apps for enterprise, such as Office 365 E3. Check each user’s actual product and rights.

Device licensing is a separate model

Microsoft also offers Microsoft 365 Apps for enterprise (device). For commercial customers it documents EA/EAS availability; eligible licensed devices allow signed-in people to use the apps. The model needs the appropriate product, supported environment, Entra join or hybrid join and DeviceBasedLicensing configuration. It is not one Business Premium assigned to a computer or merely enabling SCA. The SCA diagnostics below address user licensing; assess device licensing separately, including the agreement channel.

Comparison of scenarios and controls
ScenarioWhat to solve with Office applicationsSeparate question
One employee on their own PCA plan that includes desktop apps; standard user activationWindows license and status on the device
Multiple people on a PC with user licensingEach own account and license supporting SCA; SCA mode onDevice and access rights management
More people on the RDS hostSCA and appropriate Microsoft 365 Apps license for everyoneWindows Server/RDS license and version support
Shared desktop in AVDSCA for Office on a shared hostAVD user entitlement and Azure costs
Personal virtual desktopAssess whether the host is actually sharedRights 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

Plan SCA in the Office Deployment Tool configuration, or select Shared Computer in Office Customization Tool. The setting is SharedComputerLicensing with value 1. Microsoft documents changing an existing installation without reinstalling; reboot to apply the change. Reset previous activation if the user activated Apps before SCA was enabled.

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.

The SCA overview adds important boundaries: SCA is unavailable for Office for Mac. Apps for business in Business Premium cannot enable SCA through Group Policy; use ODT or another documented method for that product. Check the installed product, not only the subscription name.

Tokens, five devices and lost profiles

Microsoft documents a 30-day SCA token lifetime in the user profile, with renewal attempted while apps are used. After a longer absence, launching Office may need another connection to the licensing service. Token lifetime does not extend subscription rights. SCA activation does not consume the ordinary five-PC allowance, although reasonable shared-device activation limits still apply.

Our diagnostic examples
SymptomPossible causeCheck
Activation after a 35-day absenceExpired local tokenUser entitlement and renewal connectivity
Sign-in on every new hostNon-persistent profile or tokenProfile retention and supported token roaming
Only the administrator succeedsDifferent rights or Office accountEmployee’s actual destination licence and sign-in
SCA enabled but editing restrictedMissing entitlement or tokenExact product, user, activation and service

For non-persistent VDI, Microsoft supports token roaming with the profile or a designated network folder. The location must be unique to the user and writable. Network storage introduces latency considerations; do not combine everyone’s tokens in one folder to avoid repeated activation.

Activation does not prove server support

Microsoft 365 Apps support by server
HostFull Apps supportFurther distinction
Windows Server 2016/2019Ended 14 October 2025Apps security updates until 10 October 2028
Windows Server 2022Ends October 2026Apps security updates until 10 October 2028
Windows Server 2025During mainstream support until October 2029Also check Apps version and update channel

This follows the current support guide. Continued Apps security updates do not extend full configuration support. The Windows Server OS lifecycle is a separate question. Successful activation on an old host therefore still needs a migration plan to a supported platform.

Troubleshooting Office activation on a shared PC

Two colleagues are verifying Office activation on a laptop together

Proceed in this order:

  1. Describe the host. Is it a physical shared PC, an RDS session, a shared virtual desktop, or a personal VM?
  2. 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 their own account?
  3. Check installation mode. Is SCA actually enabled on the host and did the change take effect after a reboot?
  4. 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?
  5. Test another account. One successfully activated user does not verify the entire group.
  6. 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

Our hypothetical company has eight people using desktop Word and Excel on two shared PCs. Four hold Business Premium and four Business Standard. Under the user-based SCA design, the first four have an eligible plan and the other four need appropriate rights. One extra Business Premium assigned as if it licensed the computer does not resolve this. Choose the intended licensing model, cover its requirements, then configure and verify activation.

Moving those people to AVD adds host OS and virtual-desktop access decisions. Keep the user list, application rights, activation mode and infrastructure costs in the design.

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?

Start with the affected user’s entitlement, installation mode and licensing-service connectivity. If remote access fails before Office opens, diagnose that layer separately. Record the exact error and host type.

Does successful server activation prove full support?

No. Entitlement, activation and the supported OS/Apps combination are separate checks. Verify the current support matrix, not only whether Word runs.

Before ordering

Before ordering, record who uses the apps, what they need and where the host runs. Select the actual licensing model, configure activation and verify Windows or remote-access rights separately. See our Business Premium and Windows Home/Pro guide for underlying device licensing.