Shared Computer Activation

Shared Computer Activation (SCA) is the Microsoft 365 Apps activation mode for multi-user environments — Azure Virtual Desktop, Windows 365 multi-session, Citrix, terminal servers, RDS hosts, and similar. Without SCA, Office activation binds to a device (with a 5-device-per-user limit); on shared hosts, that quickly exceeds the limit. With SCA, activation is per-session and short-lived (the user gets a token valid for a few days), not tied to the host machine. Enabled via the Office Deployment Tool, Intune Microsoft 365 Apps profile, or registry / Group Policy. Required for any multi-user Office deployment; not needed for single-user devices.

Worked example

A call centre deploys Azure Virtual Desktop with a single shared session host that dozens of agents log into and out of across three shifts a day. Without Shared Computer Activation, each agent's sign-in would try to bind Office activation to that one host machine, and the organisation would burn through the 5-device-per-user activation limit for every agent almost immediately, since the "device" is really one shared host serving many people. With SCA enabled through the Office Deployment Tool configuration, each agent instead gets a short-lived, per-session activation token tied to their own account rather than the host — so any number of agents can use the same session host without anyone hitting a device limit.

Common pitfalls

Deploying Office on a multi-session or VDI host without enabling SCA is the most common and most disruptive mistake — users start hitting "this copy of Office isn't activated" errors as device-activation limits are exhausted, often days or weeks after the rollout when the problem is much harder to trace back to its actual cause. Enabling SCA on a normal single-user desktop by mistake, rather than leaving it off, can cause unnecessary re-activation prompts on that device, since SCA changes the assumptions Office makes about how sessions and devices relate. And forgetting that SCA is configured at deployment time (via the Office Deployment Tool XML, Intune profile, or Group Policy) rather than something an individual user or even a local admin can toggle after installation means a host built without it usually needs Office reinstalled with the correct configuration, not just a settings change.