Whenyou start an Microsoft 365 app that's not activated, you'll be prompted to sign in to Microsoft 365. Be sure to sign in using the Microsoft account, or work or school account, that you used to buy or subscribe to Microsoft 365.
To use Microsoft 365 on your new device, you can activate Microsoft 365 as a 1-month trial of Microsoft 365 Family. You can also buy Microsoft 365, add Microsoft 365 to an existing Microsoft 365 subscription, or enter a product key from a new product key card. If you have an older copy of Microsoft 365, you can install that instead.
A digital product key is transmitted to your PC, so you won't need or receive a printed product key. You activate Microsoft 365 by signing in with a Microsoft account. If we detect your Microsoft account, we'll show it on this screen. After you sign in, your product is added to your Microsoft account, so that you can reinstall it later, or manage your new subscription, without a product key.
If you bought Office Professional Plus, Visio Professional, or Project Professional through your employer's Microsoft Workplace Discount Program (formerly known as Microsoft Home Use Program) benefit, select I don't want to sign in or create an account (at the bottom of the screen) and enter your product key.
If you bought a new Microsoft 365 product key card, or you received a product key when you bought Microsoft 365through an online store, go to Office.com/setup or Microsoft365.com/setup and follow the on-screen prompts. This is a one-time process that adds your new product to your Microsoft account. After you redeem your key, you can install Office.
If Microsoft 365 can't activate, it eventually becomes unlicensed and all editing features of Microsoft 365 are disabled. Microsoft can become unlicensed for a number of reasons. For example, if your Microsoft 365 subscription expires, you must renew your subscription to restore all features of Microsoft 365.
Multiple Activation Key (MAK) activation is used for one-time activation through Microsoft-hosted activation services, either via the internet or by telephone. MAK activation requires that a MAK is installed on a client computer and instructs that computer to activate itself against those services.
Each MAK has a predetermined number of allowed activations and is based on your volume licensing agreement. Each Office activation that uses MAK counts toward the activation limit. After Office is activated, no reactivation is required unless the hardware changes significantly.
MAK proxy activation by using VAMT enables one computer with internet access to process activation requests on behalf of multiple computers. MAK proxy activation is configured by using the Volume Activation Management Tool (VAMT). MAK proxy activation is appropriate for environments in which security concerns might restrict direct access to the internet or to development and test labs. For more information, see Perform Proxy Activation.
If you're using MAK to activate Office LTSC 2021, you specify the key in the configuration.xml file used by the Office Deployment Tool when you deploy Office LTSC 2021 to the users in your organization. For more information, see Deploy Office LTSC 2021.
If you're using MAK to activate volume licensed versions of Office 2019, you specify the key in the configuration.xml file used by the Office Deployment Tool when you deploy Office 2019 to the users in your organization. For more information, see Deploy Office 2019 (for IT Pros).
If you need to change the Office 2016 product key on multiple computers after Office is installed, we recommend that you use Volume Activation Management Tool (VAMT) 3.1. For more information, see Volume Activation Management Tool (VAMT) Technical Reference.
An administrator can create a registry key that lets a standard user (a user who isn't an administrator) activate Office 2016 with MAK. By default, volume-licensed versions of Office 2016 disable this behavior.
In some organizations, different groups have different MAK keys for their volume licensed versions of Office, Project, or Visio. Unfortunately, you can't include multiple MAK keys in the same configuration.xml file (for Office LTSC 2021 or Office 2019) or in the Office Customization Tool or config.xml file (for Office 2016).
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 their own computers and no one else uses those computers, use product key activation for Microsoft 365 Apps.
To activate Microsoft 365 Apps, TLS 1.2 must be enabled by default on the operating system. Some older operating systems, such as Windows 7 Service Pack 1 (SP1) and Windows Server 2012, need an update applied to enable TLS 1.2 by default. For more information, see Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows. But, running Microsoft 365 Apps on these older operating systems isn't supported. For more information, see End of support resources for Office.
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:
When you're using the Office Customization Tool at
config.office.com or the wizard built into Microsoft Configuration Manager, make sure that you enable the option Shared Computer in the Product activation section.
If Microsoft 365 Apps is already installed and you want to enable shared computer activation, there are three options to choose from. A reinstallation isn't 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 enable the "Use shared computer activation" policy. This policy is found under Computer Configuration\Policies\Administrative Templates\Microsoft Office 2016 (Machine)\Licensing Settings.
The Support and Recovery Assistant fully automates all of the steps to verify requirements for shared computer activation and to enable shared computer activation. It's available in two versions: enterprise and UI. Use the version that's best suited for your situation.
The Enterprise version of the Microsoft Support and Recovery Assistant is a command-line version. This version supports scripting for managing multiple devices, including those devices not immediately accessible. Download the Enterprise version.
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 synchronizes Office 365 (Microsoft Entra ID) and local Active Directory (AD) accounts, users are unlikely to encounter any prompts. Microsoft 365 Apps can automatically retrieve the necessary information about the user's account in Office 365.
These steps are repeated for each user who signs in 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 sign in the computer.
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 sign in 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 isn't 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. In this mode 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.
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 is assigned a license for Microsoft 365 Apps. For more information, see Microsoft 365 identity models and Microsoft Entra ID.
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 virtual desktop infrastructure (VDI) scenarios.
3a8082e126