If you deploy Office from a local source on your network, use the Office Content Delivery Network (CDN) as a backup source for language packs that might not be available at that local source.Automatically install the same languages as the operating system.When deploying multiple languages in a large organization, we recommend these best practices:

If a setting isn't yet available in the OCT, steps are given for creating the configuration file in a text editor. The steps in this article assume that you're deploying with Configuration Manager or the Office Deployment Tool, and that you use the Office Customization Tool (OCT) to create the configuration files for your deployment. You can deploy multiple languages by including those languages directly in the Office packages, or you can deploy languages as a separate package, after Office is already installed. In general, you deploy languages for Microsoft 365 Apps with the same process and tools that you use to deploy Office itself. For example, you can't use language packs downloaded from the Volume Licensing Service Center (VLSC) with Microsoft 365 Apps. You can't use language resources for Windows Installer (MSI) versions of Office with Microsoft 365 Apps, which uses Click-to-Run. The subscription version of the Visio desktop app that comes with Visio Plan 2.The subscription version of the Project desktop app that comes with Project Plan 3 or Project Plan 5.Microsoft 365 Apps for business, which comes with some Microsoft 365 business plans.Microsoft 365 Apps for enterprise, which comes with many Office 365 and Microsoft 365 enterprise plans.The guidance in this article applies to the following Office products: We recommend using this article as part of planning your Office deployment. This article covers the options for deploying languages for Microsoft 365 Apps, including what method to use, where to deploy languages from, how to deploy proofing tools, and best practices.

Office 365 full installer