Overview of volume activation of Office
Applies to: Volume licensed versions of Office 2019 and Office 2016, including Project and Visio
Activation is the process of validating software with the manufacturer after it has been installed on a specific computer. Activation confirms that the product is genuine—not a fraudulent copy—and that the product key or serial number is valid and has not been compromised or revoked. Activation also establishes a link or relationship between the product key and the particular installation.
If you're a user trying to activate a personal copy of Office, see Activate Office instead of reading this article.
Volume activation is the process that Microsoft volume licensing customers use to automate and manage the activation of Windows operating systems, Microsoft Office, and other Microsoft products across large organizations.
There are three different methods that you can activate volume licensed versions of Office, including Project and Visio:
Key Management Service (KMS): Office is activated by contacting a KMS host computer on your network.
Multiple Activation Key (MAK): Office is activated online by Microsoft-hosted activation servers or by telephone.
Active Directory-based: Office on a domain-joined computer is activated through Active Directory.
Which activation method you choose depends on the size, network infrastructure, connectivity, and security requirements of your environment. You can choose to use different activation methods for different versions of Office and for different computers, for example desktops and laptops. Because these three activation methods are also used to activate volume licensed versions of Windows, you might be able to use the same method to activate both Windows and Office. For more information, see Volume Activation for Windows 10 and Volume Activation Overview.
All volume licensed versions of Office, including Project and Visio, have a preinstalled product key, called a Generic Volume License Key (GVLK), that can be used for KMS and Active Directory-based activation. You don't have to enter a product key for each Office installation if you're activating Office by using KMS or Active Directory. If you're activating Office by using MAK, you must enter a product key for each Office installation, but there are ways to automate that.
Key Management Service (KMS) activation of Office
KMS activation is a client-server model in which each client requests activation from a KMS host computer. The keys needed to activate Office are installed on the KMS host computer. The client uses DNS to locate a KMS host computer to request activation.
For more information, see the following:
- Configure a KMS host computer to activate volume licensed versions of Office
- Configure DNS for activating volume licensed versions of Office by using KMS
- Activate volume licensed versions of Office by using KMS
Multiple Activation Key (MAK) activation of Office
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 re-activation is required unless the hardware changes significantly.
For more information, see Activate volume licensed versions of Office by using MAK.
Active Directory-based activation of Office
Active Directory-based activation can activate Office installed on domain-joined computers. The product key information, which is the same that is used by KMS, is stored in Active Directory and replicated throughout the forest. If Office can't contact Active Directory for activation, Office tries to activate by using KMS.
For more information, see Activate volume licensed versions of Office by using Active Directory.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.