Office 365 Pro



Increase the impact of your insights by sharing them with teammates in the tools they use every day such as Microsoft Teams, Dynamics 365, and the Microsoft Power Platform. Encourage data exploration and insight sharing with an intuitive, familiar experience that looks and works like the other Microsoft technologies your teams already use. Select Office 365 apps to begin the installation. The 64-bit version is installed by default unless Office detects you already have a 32-bit version of Office (or a stand-alone Office app such as Project or Visio) installed. In this case, the 32-bit version of Office will be installed instead.

-->

Tip

The information in this article is intended for administrators and IT Pros. For information about activating a personal copy of Office, see Activate Office.

Shared computer activation lets you deploy Microsoft 365 Apps to a computer in your organization that is accessed by multiple users. Here are some examples of supported scenarios:

  • Three workers at a factory share the same physical computer, with each worker using Office on that computer during their eight-hour shift.
  • Fifteen nurses at a hospital use Office on ten different computers throughout the day.
  • Five employees connect remotely to the same computer to run Office.
  • Multiple employees use Office on a computer that's located in a conference room or some other public space in the company.
  • Multiple users access an instance of Office that is hosted through Remote Desktop Services (RDS).

Shared computer activation is required for scenarios where multiple users share the same computer and the users are logging in with their own account. Normally, users can install and activate Microsoft 365 Apps only on a limited number of devices, such as 5 PCs. Using Microsoft 365 Apps with shared computer activation enabled doesn't count against that limit. If your users have dedicated computers and no other users work on those computers, you use product key activation for Microsoft 365 Apps.

How to enable shared computer activation for Microsoft 365 Apps

Office 365 Pro

To use shared computer activation, you need an Office 365 (or Microsoft 365) plan that includes Microsoft 365 Apps and also supports shared computer activation. Shared computer activation is available for the following plans:

  • Any plan that includes Microsoft 365 Apps for enterprise (previously named Office 365 Plus). For example, Office 365 E3 or Microsoft 365 E5.
  • Any plan that includes the desktop version of Project or Visio. For example, Project Plan 3 or Visio Plan 2.
  • The Microsoft 365 Business Premium plan, which includes Microsoft 365 Apps for business.

Note

  • The Microsoft 365 Business Premium plan is the only business plan that includes support for shared computer activation. There are other business plans, such as Microsoft 365 Business Standard, that include Microsoft 365 Apps for business, but, those business plans don't include support for shared computer activation.
  • Shared computer activation is available for Education plans that include Microsoft 365 Apps for enterprise. For example, Office 365 A3 or Microsoft 365 A5.
  • Shared computer activation isn't available for Office for Mac.

Make sure you assign each user a license for Microsoft 365 Apps and that users log on to the shared computer with their own user account.

If you want to enable shared computer activation during the initial installation of Microsoft 365 Apps, you can instruct the Office Deployment Tool to do so during installation.

  • When you are using the Office Customization Tool at config.office.com or the wizard built into Microsoft Endpoint Configuration Manager, make sure that you enable the option Shared Computer in the Product activation section.
  • When you are crafting the configuration file manually, make sure to include the following line:

If Microsoft 365 Apps is already installed and you want to enable shared computer activation, there are three options to choose from. A re-installation is not required. The device must be rebooted in order to apply the change.

  • Use Group Policy by downloading the most current Administrative Template files (ADMX/ADML) for Office and enabling the 'Use shared computer activation' policy setting. This policy setting is found under Computer ConfigurationPoliciesAdministrative TemplatesMicrosoft Office 2016 (Machine)Licensing Settings.

  • Use Registry Editor to add a String value (Reg_SZ) of SharedComputerLicensing with a setting of 1 under HKEY_LOCAL_MACHINESOFTWAREMicrosoftOfficeClickToRunConfiguration.

  • Download and run the Microsoft Support and Recovery Assistant. This is required to change the activation method from subscription mode to shared mode.

    Note

    Microsoft 365 Apps for business doesn't support the use of Group Policy, so you'll need to use another method to enable shared computer activation.If a user already activated the Microsoft 365 Apps before shared computer activation was enabled, you have to reset the activation to allow shared computer activation to work.

After Microsoft 365 Apps is installed, you can verify that shared computer activation is enabled on that computer.

Office 365 Professional Plus

How shared computer activation works for Microsoft 365 Apps

Here's what happens after Microsoft 365 Apps is installed on a computer that has shared computer activation enabled.

  1. A user logs on to the computer with their account.

  2. The user starts an Office program, such as Word.

  3. Microsoft 365 Apps contacts the Office Licensing Service on the internet to obtain a licensing token for the user.

    To determine whether the user is licensed to use Microsoft 365 Apps, the Office Licensing Service has to know the user's account for Office 365. In some cases, Microsoft 365 Apps prompts the user to provide the information. For example, the user might see the Activate Office dialog box.

    If your environment is configured to synchronize Office 365 (Azure Active Directory) and local Active Directory (AD) accounts, then the user most likely won't see any prompts. Microsoft 365 Apps should automatically be able to get the necessary information about the user's account in Office 365.

  4. If the user is licensed for Microsoft 365 Apps, a licensing token is stored on the computer in the user's profile folder, and Microsoft 365 Apps is activated. The user can now use Microsoft 365 Apps.

These steps are repeated for each user who logs on to the shared computer. Each user gets a unique licensing token. Just because one user activates Microsoft 365 Apps on the computer doesn't mean Microsoft 365 Apps is activated for all other users who log on to the computer.

If a user goes to another computer that also is enabled for shared computer activation, the same steps occur. There is a different licensing token for each computer that the user logs on to.

If a user logs on to a shared computer again, Microsoft 365 Apps uses the same licensing token, if it is still valid.

Additional details about shared computer activation for Microsoft 365 Apps

Licensing token renewal The licensing token that is stored on the shared computer is valid only for 30 days. As the expiration date for the licensing token nears, Microsoft 365 Apps automatically attempts to renew the licensing token when the user is logged on to the computer and using Microsoft 365 Apps.

If the user doesn't log on to the shared computer for 30 days, the licensing token can expire. The next time that the user tries to use Microsoft 365 Apps, Microsoft 365 Apps contacts the Office Licensing Service on the internet to get a new licensing token.

Internet connectivity Because the shared computer has to contact the Office Licensing Service on the internet to obtain or renew a licensing token, reliable connectivity between the shared computer and the internet is necessary.

Reduced functionality mode If the user is not licensed for Microsoft 365 Apps, or if the user closed the Activate Office dialog box, no licensing token is obtained and Microsoft 365 Apps isn't activated. Microsoft 365 Apps is now in reduced functionality mode. This means that the user can view and print Office documents, but can't create or edit documents. The user also sees a message in the Office program that most features are turned off.

Activation limits Normally, users can install and activate Microsoft 365 Apps only on a limited number of devices, such as 5 PCs. Using Microsoft 365 Apps with shared computer activation enabled doesn't count against that limit.

Microsoft allows a single user to activate Microsoft 365 Apps on a reasonable number of shared computers in a given time period. The user gets an error message in the unlikely event the limit is exceeded.

Office 365 Products

Single sign-on recommended The use of single sign-on (SSO) is recommended to reduce how often users are prompted to sign in for activation. With single sign-on configured, Microsoft 365 Apps is activated using the user credentials that the user provides to sign in to Windows, as long as the user has been assigned a license for Microsoft 365 Apps. For more information, see Microsoft 365 identity models and Azure Active Directory.

If you don't use single sign-on, you should consider using roaming profiles and include the %localappdata%MicrosoftOffice16.0Licensing folder as part of the roaming profile.

Licensing token roaming Starting with Version 1704 of Microsoft 365 Apps, you can configure the licensing token to roam with the user's profile or be located on a shared folder on the network. Previously, the licensing token was always saved to a specific folder on the local computer and was associated with that specific computer. In those cases, if the user signed in to a different computer, the user would be prompted to activate Microsoft 365 Apps on that computer in order to get a new licensing token. The ability to roam the licensing token is especially helpful for non-persistent VDI scenarios.

To configure licensing token roaming, you can use either the Office Deployment Tool or Group Policy, or you can use Registry Editor to edit the registry. Whichever method you choose, you need to provide a folder location that is unique to the user. The folder location can either be part of the user's roaming profile or a shared folder on the network. Microsoft 365 Apps needs to be able to write to that folder location. If you're using a shared folder on the network, be aware that network latency problems can adversely impact the time it takes to open Office programs. The location is only needed if you prefer to not use the default location, which is %localappdata%MicrosoftOffice16.0Licensing.

  • If you're using Group Policy, download the most current Administrative Template files (ADMX/ADML) for Office and enable the 'Specify the location to save the licensing token used by shared computer activation' policy setting. This policy setting is found under Computer ConfigurationPoliciesAdministrative TemplatesMicrosoft Office 2016 (Machine)Licensing Settings.

  • If you're using the Office Deployment Tool, include the SCLCacheOverride and SCLCacheOverrideDirectory in the Property element of your configuration.xml file. For more information, see Configuration options for the Office Deployment Tool.

  • To edit the registry, go to HKEY_LOCAL_MACHINESOFTWAREMicrosoftOfficeClickToRunConfiguration, add a string value of SCLCacheOverride, and set the value to 1. Also, add a string value of SCLCacheOverrideDirectory and set the value to the path of the folder to save the licensing token.

    Note

    If you're using Microsoft Application Virtualization (App-V) to deploy Microsoft 365 Apps, the registry location is HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice16.0CommonLicensing.

Related articles

-->

Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. To learn more about this name change, read this blog post. In our documentation, we'll usually just refer to it as Microsoft 365 Apps.

Office 365 ProPlus is the version of Office that comes with several enterprise, government, and education subscription plans. For example, Office 365 E5 and Office 365 A3. Even though those plans aren't being renamed, Office 365 ProPlus that comes with those plans will be renamed.

Office 365 Pro Plus Comparison

When does the new name take effect?

The new name will appear in Version 2004 onwards, starting on April 21, 2020. For example, the following screenshot is an example of what you'll see under the Product Information section when you go to File > Account in an Office app, such as Word.

Starting with Version 2005, when you go to Control Panel > Programs > Programs and Features, you will see an entry similar to the following:

Microsoft 365 for enterprise – en-us

Office 365 Pro Plus Plan

Older versions of Office 365 ProPlus won't be updated with the new name. For example, if you're using Version 1908 of Semi-Annual Enterprise Channel, you'll still see Office 365 ProPlus under the Product Information section and in Control Panel.

References to Microsoft 365 Apps for enterprise will begin to appear on April 21 in other places as well. For example, references on product websites, in documentation, and in the user interface (UI) of deployment tools, such as the Office Customization Tool. Some references to the new name might not occur until after April 21.

What do admins need to do?

Because of this name change, you might need to adjust some of your existing workflows and update your internal documentation.

Office Deployment Tool

Office 365 Project Management

If you use the Office Deployment Tool to deploy Office 365 ProPlus, the product ID will remain as O365ProPlusRetail. Therefore, you don't have to make any changes to your existing configuration.xml files.

Update packages used by Configuration Manager

If you use an automatic deployment rule (ADR) to deploy updates by using Configuration Manager, you'll need to make changes to your ADRs if they rely on the 'Title' property. That's because the name of update packages in the Microsoft Update Catalog is changing.

Currently, the title of an update package for Office 365 ProPlus begins with 'Office 365 Client Update' as seen in the following example:

Office 365 Client Update - Semi-annual Channel Version 1908 for x64 based Edition (Build 11929.20648)

For update packages released on and after June 9, the title will begin with 'Microsoft 365 Apps Update' as seen in the following example:

Microsoft 365 Apps Update - Semi-Annual Enterprise Channel Version 1908 for x64 based Edition (Build 11929.50000)

Registry key values

Office 365 Pro Plus 2019 Lifetime Account

Some registry key values might change to reflect the new naming. If you rely on these values in your workflows or scripts, you'll want to test your workflows or scripts when the name change begins rolling out on April 21. In general, because registry key values can possibly change in future builds of Office, we don't usually recommend relying on them in your workflows or scripts.

PowerShell scripts

There shouldn't be any changes needed to PowerShell scripts for licensing. The string ID and GUID that were used for Office 365 ProPlus in PowerShell cmdlets are the same string ID and GUID that are now used for Microsoft 365 Apps for enterprise. But it's always a good idea to test your scripts before applying them broadly in your organization.

For more information about licensing identifiers used with PowerShell cmdlets, see Product names and service plan identifiers for licensing.