Office For Mac License Installer



  1. Activate MS Office 2019/2016 for macOS - MicrosoftOffice2019VLSerializer Office 2019 above. Note that Office2019 DO NOT support activate via simple copy/paste plist license file which is the simplest way to activate Office 2016. Fortunately, you can also use the VL Serializer tool, just install Office 2019 and Serializer, then run Serializer to activate.
  2. Activate Office 365 versions of Office for Mac. If your organization has an Office 365 (or Microsoft 365) plan, make sure you assign each user a license for Office before you deploy Office for Mac to your users. If you don't assign a user a license, you can still deploy Office for Mac to that user, but the user won't be able to activate and use Office.
  3. To download and install Office 2013 for a single PC, Office 2016 for a single PC and Office 2016 for a single Mac go to MyAccount. Before you begin Make sure you have Your Office product key (xxxxx-xxxxx-xxxxx-xxxxx-xxxxx). Your license key must contain 25.

Change Office License Mac

-->

Download and install the trial version of Office 2019 for macOS first. If all ok, buy the license from us. Fully installed versions of Microsoft Outlook 2019, Word 2019, Excel 2019, PowerPoint 2019 and OneNote 2019 for Mac.

Office for Mac that comes with a Microsoft 365 subscription is updated on a regular basis to provide new features, security updates, and non-security updates. The following information is primarily intended for IT professionals who are deploying Office for Mac to the users in their organizations.

Note

  • Starting with Version 16.21, Microsoft Teams will be installed by default for new installations if you're using the Office suite install package. For more information, see Microsoft Teams installations on a Mac.
  • For security reason, Microsoft has deprecated the use of SHA-1. Learn more
  • Starting with the 16.17 release in September 2018, this information also applies to Office 2019 for Mac, which is a version of Office for Mac that’s available as a one-time purchase from a retail store or through a volume licensing agreement.
  • The update history information for version 16.16 and earlier also applies to Office 2016 for Mac, which is also a version of Office for Mac that’s available as a one-time purchase. Older versions up to and including 16.16 can be activated with an Office 2016 for Mac volume license. You can’t activate version 16.17 or later with an Office 2016 for Mac volume license. For information about Office 2016 for Mac releases from September onward, see Release notes for Office 2016 for Mac
  • For information about the features, security updates, and non-security updates that are included in a given release of Office for Mac, see Release notes for Office for Mac.
  • If you want early access to new releases, join the Office Insider program.

Most current packages for Office for Mac

The following table lists the most current packages for the Office suite and for the individual applications. The Office suite includes all the individual applications, such as Word, PowerPoint, and Excel. All packages are 64-bit only. The build date is listed in parentheses, in a YYMMDD format, after the version number. The install package is used if you don't have the application already installed, while the update package is used to update an existing installation.

To view release notes, see Release notes.

October 13, 2020

Version 16.42 (20101102)

ApplicationDownload linksSHA-256 hash for install package
Office suite (with Teams)Install package8AC425F0E31869B32C323F4349FB48E9B1C3A114B77EA68897D97C50D9B8BECB
Office suite (without Teams)Install package5FA1084BD240BF10FAAF94D908492939807EAD8E014582DCB2ADE7ECC484276B
WordInstall package
Update package
21C54A78343B106A93FFD176130DEB9A6C9154F56EB58446FC27192D1E191995
ExcelInstall package
Update package
2235E4FE0741CE013777E2B6811AD9EFF738F9A724860FBA0DFD31976BF96E62
PowerPointInstall package
Update package
EAF6B82C2042BD4D026779CEB4A58E0B92C8E320A9797C77CA3A588FD94B19EB
OutlookInstall package
Update package
566A1BD7AD446FCDD31156EBCA3FBD7F8F8BB2EFBCC8F3217CB55AA16A586420
OneNoteUpdate packageNot applicable

Release history for Office for Mac

The following table provides release history information and download links for Office for Mac. The table is ordered by release date, with the most recent release date listed first. The build date is listed in parentheses, in a YYMMDD format, after the version number. All releases after August 22, 2016 are 64-bit only. All releases prior to August 22, 2016 are 32-bit only.

Note

Download links are only provided for the most recent releases.

Release dateVersionInstall packageUpdate packages
October 13, 202016.42 (20101102)Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
September 15, 202016.41 (20091302)Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
August 11, 202016.40 (20081000)Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
July 14, 202016.39 (20071300)Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
June 16, 202016.38 (20061401)Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
May 12, 202016.37 (20051002)Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
April 21, 202016.36 (20041300)Office suite (with Teams)
Office suite (without Teams)
April 14, 202016.36 (20041300)Word, Excel, PowerPoint, Outlook, OneNote
March 10, 202016.35 (20030802)Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
February 11, 202016.34 (20020900)Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
January 14, 202016.33 (20011301)Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
December 10, 2019
16.32 (19120802)
Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
November 12, 2019
16.31 (19111002)
Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
October 15, 2019
16.30 (19101301)
Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
September 18, 2019
16.29.1 (19091700)
Word, Excel, PowerPoint
September 10, 2019
16.29 (19090802)
Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
August 13, 2019
16.28 (19081202)
Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
July 16, 2019
16.27 (19071500)
Office suite (with Teams)
Office suite (without Teams)
Word, Excel, PowerPoint, Outlook, OneNote
June 11, 2019
16.26 (19060901)

May 14, 2019
16.25 (19051201)

April 16, 2019
16.24 (19041401)

March 27, 2019
16.23.1 (19032603)
March 12, 2019
16.23.0 (19030902)

February 20, 2019
16.22 (19022000)


January 24, 2019
16.21 (19011700)
January 16, 2019
16.21 (19011500)
December 11, 2018
16.20 (18120801)
November 13, 2018
16.19 (18110915)
October 16, 2018
16.18 (18101400)
September 11, 2018
16.17 (18090901)
August 14, 2018
16.16 (18081201)
July 10, 2018
16.15 (18070902)
June 13, 2018
16.14.1 (18061302)
June 12, 2018
16.14.0 (18061000)
May 24, 2018
16.13.1 (18052304)
May 23, 2018
16.13.1 (18052203)
May 15, 2018
16.13.0 (18051301)
April 11, 2018
16.12.0 (18041000)
March 19, 2018
16.11.1 (18031900)
March 13, 2018
16.11.0 (18031100)
February 13, 2018
16.10.0 (18021001)
January 26, 2018
16.9.1 (18012504)
January 18, 2018
16.9.0 (18011602)
December 12, 2017
15.41.0 (17120500)
November 14, 2017
15.40.0 (17110800)
October 10, 2017
15.39.0 (17101000)
September 12, 2017
15.38.0 (17090200)
August 15, 2017
15.37.0 (17081500)
July 21, 2017
15.36.1 (17072101)
July 11, 2017
15.36.0 (17070200)
June 16, 2017
15.35.0 (17061600)
June 13, 2017
15.35.0 (17061000)
May 16, 2017
15.34.0 (17051500)
April 11, 2017
15.33.0 (17040900)
March 14, 2017
15.32.0 (17030901)
February 16, 2017
15.31.0 (17021600)
January 11, 2017
15.30.0 (17010700)
-->

To configure and perform deployments of volume licensed versions of Office 2019, including Project and Visio, for users in your organization, you use the Office Deployment Tool (ODT). The Office Customization Tool (OCT) that you previously used for Windows Installer (MSI) is no longer used.

The installation files for Office 2019 are available on the Office Content Delivery Network (CDN) on the internet instead of on the Volume Licensing Service Center (VLSC). You can install Office 2019 directly from the Office CDN. Or, you can download the installation files from the Office CDN to a location on your local network, such as a shared folder, and install Office 2019 from that location. You can use different methods for different sets of computers in your organization. Whichever method you choose, you use the ODT.

Change office license mac

Installing directly from the Office CDN requires the least amount of administrative effort and is recommended. But you might have constraints that prevent you from installing directly from the internet. For example, some computers might not have connectivity to the internet or you may have limited bandwidth to the internet.

Download the Office Deployment Tool from the Microsoft Download Center

The Office Deployment Tool is a free download from the Microsoft Download Center. We recommend that you always download and use the most current version of the ODT.

After you download the Office Deployment Tool, double-click on the officedeploymenttool executable (.exe) file to extract the ODT files. When you are finished, you should have several files: setup.exe and some sample configuration.xml files. For an Office 2019-specific sample, see Sample configuration.xml file to use with the Office Deployment Tool.

The setup.exe file is the ODT and is a command-line tool that supports downloading and installing Office 2019. The configuration.xml files are sample files to get you started. You use the configuration.xml file to provide settings for the ODT to use when downloading or installing Office 2019. The configuration.xml is a simple xml file that can be created and edited in any text editor, such as Notepad. You can name the file anything that you want, as long as it retains the xml file extension.

Create the configuration.xml

Once you have a copy of the ODT, you need to create a configuration.xml file. You can create multiple configuration.xml files to be used with the ODT. For example, you would create a configuration.xml file to download and install the 64-bit version of Office Professional Plus 2019 in English and a different configuration.xml file to install the 32-bit version of Visio Professional 2019 in French. When you run the ODT from an elevated command prompt, you specify which configuration.xml file to use.

Tip

Instead of using a text editor to create your configuration.xml, we recommend that you use the Office Customization Tool (OCT). The OCT provides a web-based interface for making your selections and creating your configuration.xml file to be used with the Office Deployment Tool. For more information, see Overview of the Office Customization Tool. Please note that this is different than the Office Customization Tool that you might have used in the past to install volume licensed versions of Office that used Windows Installer (MSI) as the installation technology.

There are a series of settings in the configuration.xml file that you configure to customize the Office 2019 download or installation. The following table lists the most common settings to configure in the configuration.xml file.

Configurationconfiguration.xml settingAdditional information
Where to download the Office installation files to and where to install Office from
For example, servershare (a shared folder on your local network)
SourcePathIf you don’t specify a SourcePath when using the ODT to install Office, the ODT looks for the installation files in the folder it’s located in. If it doesn’t find the Office installation files there, it goes to the Office CDN to get the installation files.
We recommend that you install Office directly from the Office CDN, if internet connectivity and network bandwidth make that possible.
Which products to download or install
For example, Office Professional Plus 2019
Product IDValid values for volume licensed versions of Office 2019 include the following:
- ProPlus2019Volume
- Standard2019Volume
- ProjectPro2019Volume
- ProjectStd2019Volume
- VisioPro2019Volume
- VisioStd2019Volume
For a list of Product IDs for other volume licensed versions of Office 2019, such as Access 2019, see Product IDs that are supported by the Office Deployment Tool for Click-to-Run.
Use Key Management Service (KMS) to activate Office 2019PIDKEYEnter the Generic Volume License Key (GVLK) for KMS activation.
Use Multiple Activation (MAK) to activate Office 2019PIDKEYEnter the product key for MAK activation.
Which languages to download or install
For example, English (en-us) and French (fr-fr).
Language IDYou can install multiple languages at the same time you’re Installing Office 2019, or you can install them later.
For more information, see Deploy languages for Office 2019.
Which proofing tools to installProduct IDThe Product ID is 'ProofingTools' and is used in combination with the Language ID.
For more information, see Deploy languages for Office 2019.
Which edition of Office 2019 to download or install.
For example, the 64-bit version.
OfficeClientEditionValid xml values are '32' and '64.'
All Office products on the computer must be of the same architecture. You can’t have both 32-bit and 64-bit Office products installed on the same computer.
We recommend 64-bit on computers that have 4 gb or more of memory. But you should assess application compatibility and other factors that might require you to use the 32-bit version.
For more information, see Choose between the 64-bit or 32-bit version of Office.
Which apps to install
For example, all apps except Publisher.
ExcludeAppBy default, all apps included in Office Professional Plus 2019 are installed.
For example, to not install Publisher, you can include the following line in your configuration.xml:
<ExcludeApp />
For more information, see ExcludeApp element.
Where to get security and quality updates from.
For example, directly from the Office CDN on the internet.
UpdatePathThe default is to get updates directly from the Office CDN on the internet. This is recommended and requires the least amount of administrative effort.
But if you need to update computers that don’t have connectivity to the internet, you can specify that Office gets updates, for example, from a shared folder on your local network. But this means that you must download the updates from the Office CDN and copy them to the shared folder.
For more information, see Update Office 2019 (for IT Pros).
Which update channel to install from and get updates fromChannelOffice uses the concept of update channels to determine which updates an installed version of Office receives.
For more information, see Update channel for Office 2019.
Whether to remove previous Windows Installer (MSI) versions of Office before installing Office 2019RemoveMSIThis is recommended.
For more information, see Remove existing versions of Office before installing Office 2019.

Tip

More information about these configuration.xml settings is available here: Configuration options for the Office Deployment Tool. Keep in mind that not all the information in that article applies to Office 2019. For example, the settings related to shared computer activation, such as SharedComputerLicensing and SCLCacheOverride, don’t apply to Office 2019.

Sample configuration.xml file to use with the Office Deployment Tool

The following is a sample configuration.xml file that can be used to either download or install the 64-bit version of Office Professional Plus 2019 in English using a shared folder on your local network and activate by using MAK. If you’re using this configuration.xml to install Office 2019, previous Windows Installer (MSI) versions of Office are removed as part of the installation process. Also, even though it’s not specified in the configuration.xml file, updates are automatically enabled and are configured to come directly from the Office CDN, because those are the default settings.

For the PIDKEY, replace #####-#####-#####-#####-##### with your MAK client activation key.

Remove existing versions of Office before installing Office 2019

We recommend that you uninstall any previous versions of Office before installing volume licensed versions of Office 2019. To help you uninstall versions of Office that use Windows Installer (MSI) as the installation technology, you can use the Office Deployment Tool and specify the RemoveMSI element in your configuration.xml file.

There are several ways that you can use the RemoveMSI element when installing volume licensed versions of Office 2019.

  • Uninstall all Office products on the computer.
  • Identify any existing language resources, like language packs, and install the same languages.
  • Keep some Office products and uninstall all other Office products on the computer.

RemoveMSI can be used to uninstall 2010, 2013, or 2016 versions of Office, Visio, or Project that were installed using Windows Installer (MSI).

For more information about using RemoveMSI, see Remove existing MSI versions of Office when upgrading to Microsoft 365 Apps. Even though this article is about Microsoft 365 Apps, most of the information also applies to volume licensed versions of Office 2019.

Download the Office 2019 installation files

Once you have a copy of the ODT and have created your configuration.xml file, you can download the Office 2019 installation files to your local network. To do that, open an elevated command prompt, go to the folder where you saved the ODT and the configuration.xml file, and type this command:

If you have saved the configuration.xml file with a different name, use that name in the command.

It will look as if nothing is happening, but the download is happening in the background. Once the download is complete, you are returned to a command prompt.

If you want to check that the files are downloading, go to the location you specified for your SourcePath in the configuration.xml file. You should see a folder named “Office” with a subfolder named “Data.” There will also be a folder named with the version number of the download. For example, 16.0.10336.20044. Which files you see and the names of the files depend on whether you are downloading the 32-bit or 64-bit version of Office and which languages you are downloading.

Office For Mac 2019 License Installer.pkg

Here some additional details about downloading Office 2019 installation files:

  • You must download the 32-bit and 64-bit versions separately.
  • All volume licensed versions of Office 2019 – such as Office Professional Plus 2019, Visio Professional 2019, and Project Professional 2019 – are included in the same download, regardless of which products you specify in the configuration.xml file. This helps you save disk space on your local network. The core files for the Office 2019 products are in the stream.x86.x-none.dat or stream.x64.x-none-dat file, depending if it’s the 32-bit or 64-bit version of Office.

Install Office 2019 by using the Office Deployment Tool

Once you have a copy of the ODT and have created your configuration.xml file (and downloaded the Office 2019 installation files to your local network, if necessary), you can install Office 2019. To do that, open an elevated command prompt, go to the folder where you saved the ODT and the configuration.xml file, and type the following command:

If you have saved the configuration.xml file with a different name, use that name in the command.

Once the installation is complete, you are returned to a command prompt and you can go open Office 2019 programs you’ve installed.

Install Office 2019 by using Microsoft Endpoint Configuration Manager

You can also use Microsoft Endpoint Configuration Manager to deploy volume licensed versions of Office 2019. Configuration Manager (current branch) has a wizard that steps you through the process and builds the configuration.xml file for you. Earlier versions of Configuration Manager require you to download the ODT and create your own configuration.xml file.

  • Configuration Manager (current branch): If you’re using Configuration Manager (current branch), you can use the Office 365 Client Installation wizard to deploy Office 2019. You must be using at least version 1710, but version 1806 is recommended. You’ll see an entry for Office Professional Plus 2019 in the Office 365 Client Installation wizard. On that same page, you can also select to install Project and Visio.

  • System Center 2012 R2 Configuration Manager: If you’re using System Center 2012 R2 Configuration Manager, the steps are different and much more manual. First you need to get a copy of the ODT from the Microsoft Download Center and create the appropriate configuration.xml file for your deployment. Then, in Configuration Manager, you create an application and a deployment type. After that you distribute the application and then deploy it.

Deploy languages for Office 2019

You can use the ODT and the configuration.xml file to install volume licensed versions of Office 2019, including Project and Visio, in multiple languages. For more details, see Language element.

You can also just install proofing tools by specifying the Product ID as 'ProofingTools' in your configuration.xml file along with the appropriate Language IDs. Proofing tools packages, which are a new capability for Office 2019, are much smaller than full language packs. Consider deploying proofing tools in cases where users work with documents in multiple languages but don’t need the Office product UI in all those languages. The proofing tools can be installed at the same time you’re installing Office 2019, or you can install them later. They can also be installed whether or not the language pack for a given language is installed.

If you're upgrading from a Windows Installer (MSI) version of Office, you can get Click-to-Run versions of the same language resources – for example, language packs, language interface packs, or proofing tools – installed when you deploy Office 2019. For more information, see Remove existing MSI versions of Office when upgrading to Microsoft 365 Apps. Even though this article is about Microsoft 365 Apps, most of the information also applies to volume licensed versions of Office 2019.

Related topics





Comments are closed.