-->
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.
Download Microsoft Teams now and get connected across devices on Windows, Mac, iOS, and Android. Collaborate better with the Microsoft Teams app. Office 365 is installed as a 32-bit program on your Windows PC by default. Microsoft recommends the 32-bit version, even on 64-bit systems, to avoid compatibility issues with third-party add-ons.
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.
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.
Download Microsoft Teams now and get connected across devices on Windows, Mac, iOS, and Android. Collaborate better with the Microsoft Teams app. Office 365 is installed as a 32-bit program on your Windows PC by default. Microsoft recommends the 32-bit version, even on 64-bit systems, to avoid compatibility issues with third-party add-ons.
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. How to play xbox on ipad.
October 13, 2020
Version 16.42 (20101102)
| Application | Download links | SHA-256 hash for install package |
|---|---|---|
| Office suite (with Teams) | Install package | 8AC425F0E31869B32C323F4349FB48E9B1C3A114B77EA68897D97C50D9B8BECB |
| Office suite (without Teams) | Install package | 5FA1084BD240BF10FAAF94D908492939807EAD8E014582DCB2ADE7ECC484276B |
| Word | Install package Update package | 21C54A78343B106A93FFD176130DEB9A6C9154F56EB58446FC27192D1E191995 |
| Excel | Install package Update package | 2235E4FE0741CE013777E2B6811AD9EFF738F9A724860FBA0DFD31976BF96E62 |
| PowerPoint | Install package Update package | EAF6B82C2042BD4D026779CEB4A58E0B92C8E320A9797C77CA3A588FD94B19EB |
| Outlook | Install package Update package | 566A1BD7AD446FCDD31156EBCA3FBD7F8F8BB2EFBCC8F3217CB55AA16A586420 |
| OneNote | Update package | Not 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.
Snapshot on mac. Note
Download links are only provided for the most recent releases.
| Release date | Version | Install package | Update packages |
|---|---|---|---|
| October 13, 2020 | 16.42 (20101102) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| September 15, 2020 | 16.41 (20091302) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| August 11, 2020 | 16.40 (20081000) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| July 14, 2020 | 16.39 (20071300) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| June 16, 2020 | 16.38 (20061401) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| May 12, 2020 | 16.37 (20051002) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| April 21, 2020 | 16.36 (20041300) | Office suite (with Teams) Office suite (without Teams) | |
| April 14, 2020 | 16.36 (20041300) | Word, Excel, PowerPoint, Outlook, OneNote | |
| March 10, 2020 | 16.35 (20030802) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| February 11, 2020 | 16.34 (20020900) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| January 14, 2020 | 16.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) |
Up to now, if you had the 32-bit version of Microsoft 365 Apps installed on a device and you wanted to change to the 64-bit version, you needed to uninstall the existing 32-bit version and then install the 64-bit version. It also required that you account for all the other deployment settings configured for that device, such as the update path and the installed languages, so that those settings would be included when you did the 64-bit installation.
But now, to make it easier to change from a 32-bit to a 64-bit installation of Microsoft 365 Apps, the Office Deployment Tool and its configuration.xml file supports an optional attribute named MigrateArch. If the MigrateArch attribute is set to True, then your installation of Microsoft 365 Apps will be changed to the architecture (sometimes referred to as the bitness) that is specified in the OfficeClientEdition attribute.
With MigrateArch, you don't have to account for all the installed products and languages or other deployment settings. The migration process will preserve those during the migration process. But, if you want to make any changes to the installed products and languages, or other deployment settings, you can do that as part of the migration process by explicitly specifying those settings in your configuration.xml file. For more information, see Sample configuration.xml file to use with the Office Deployment Tool.
Requirements for using the MigrateArch attribute
To use the MigrateArch attribute, you need the following:
- At least Version 1902 of Microsoft 365 Apps installed on the device that you want to change the bitness of.
- At least version 16.0.11615.33602 of the Office Deployment Tool from the Microsoft Download Center.
- A location that contains all the product and language files for the architecture that you are changing the installation to.
Before starting the migration process to a different bitness, you must have Version 1902 or later installed on the device that you want to change the bitness of. Migration is allowed to the same version, or to any later version, but you must have at least Version 1902 installed on the device before beginning the migration process.
Version 1902, or later, is available in Current Channel, Monthly Enterprise Channel, Semi-Annual Enterprise Channel (Preview), and Semi-Annual Enterprise Channel.
Providing a source location to be used with the MigrateArch attribute
When using the MigrateArch attribute, you need a location that contains the installation source files of the bitness that you're moving to.
For this location, if network bandwidth or internet connectivity is not an issue, we recommend that you use the Office Content Delivery Network (CDN), because the CDN will always have the most up-to-date program and language installation files that you need.
If you are using a location that's on your local network, be sure to use the Office Deployment Tool to download all the necessary product and language files ahead of time. You can download the 32-bit and 64-bit installation files to the same share for a given update channel. For example, you can download the 32-bit and 64-bit installation files for Semi-Annual Enterprise Channel to server01sec. But, you need to download the installation files for Current Channel to a different location, such as server01current.
If your local network location doesn't contain files of the correct bitness, the migration fails and the bitness of the installation will remain as-is. If this location doesn't contain all the necessary language source files – for example, the French language files are missing – the migration will fail. To avoid this situation, we strongly recommend that you include AllowCdnFallback='True' in your configuration.xml file. This will use the Office Content Delivery Network (CDN) on the internet as a backup source from which to install the language files.
Sample configuration.xml file to use with the Office Deployment Tool
The following is a sample configuration.xml that will change an existing 32-bit installation of Microsoft 365 Apps to a 64-bit installation. Vlc mac 10 6 5. All existing products, languages, and other deployment settings, such as update path, will be preserved.
Update Microsoft Office To 64 Bit Mac
Then, run the Office Deployment Tool in /configure mode and specify this configuration.xml file to make the change from 32-bit to 64-bit. The 32-bit version will be uninstalled and then the 64-bit version will be installed.
Office 2011 64 Bit Mac
If you want to change the products or languages installed, or want to change other deployment settings, you need to specify those in your configuration.xml file. For example, if you want to change a 64-bit installation of Microsoft 365 Apps for enterprise in English to a 32-bit installation that includes English and German, changes the update path, and adds Visio in English, you would use a configuration.xml file that looks similar to the following example.
Additional information about using MigrateArch attribute
Before changing to a different architecture, especially when changing to 64-bit, make sure that your existing add-ins, macros, and complex Office files work on the new architecture. For more information, see Use the Readiness Toolkit to assess application compatibility for Microsoft 365 Apps.
The MigrateArch attribute can also be used to change the architecture of the subscription versions of the Project and Visio desktop apps.
The MigrateArch attribute won't migrate the bitness of Office programs on the device that were installed by using Windows Installer (MSI). Those programs can be removed by the using the RemoveMSI element in your configuration.xml file.
The MigrateArch attribute can only migrate Office products installed by using Click-to-Run and have a version number that starts with 16.0. For example, you can't use the MigrateArch attribute if Visio Professional 2013 was installed on the device by using Click-to-Run, because the 2013 version of Visio has a version number that starts with 15.0. You can find this version information by going to Control Panel > Programs > Programs and Features. If there are any Office products on the device that were installed by using Click-to-Run, and whose version number starts with 15.0, then the migration will fail.
If the architecture that you specify to move to is already the architecture of the currently installed products, then no migration takes place when you run the Office Deployment Tool. Your existing installation will not be removed and reinstalled. But if your configuration.xml includes other changes, such as adding a language, then those changes will be implemented.
If a user has an Office app, such as Word, open when the migration process begins, and the Level attribute is set to Full for the Display element in your configuration.xml file, then the user will be prompted to close the app. If they cancel the prompt, the migration is canceled. If the Level attribute is set to None, and Office apps are running on the device, then the migration will fail. You can use the FORCEAPPSHUTDOWN property in your configuration.xml file, but that will close the user's apps without any warning.
Microsoft Office 64 Bit Install
Related topics
