ANAVEM
Reference
Languagefr
How to Install Office 365 Offline for Enterprise Deployment

How to Install Office 365 Offline for Enterprise Deployment

Deploy Microsoft 365 Apps across enterprise networks without internet using Office Deployment Tool (ODT) to download installation sources and configure offline installations.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
3/16/2026 15 min 0
mediumoffice365 7 steps 15 min

Why Deploy Office 365 Offline for Enterprise?

Enterprise environments often require controlled, standardized software deployments without relying on internet connectivity for each installation. Microsoft 365 Apps offline deployment using the Office Deployment Tool (ODT) addresses critical enterprise needs: bandwidth conservation, installation consistency, and deployment control across hundreds or thousands of computers.

The traditional approach of individual online installations creates several challenges: unpredictable bandwidth usage, varying installation configurations, and dependency on internet connectivity for each target machine. ODT version 16.0.16825.20102 solves these issues by enabling administrators to download complete installation sources once, then deploy them across the network without internet requirements on target computers.

What Makes ODT the Preferred Enterprise Solution?

Unlike consumer-focused IMG/ISO methods, ODT provides enterprise-specific features: XML-based configuration management, channel selection for update control, application exclusion capabilities, and integration with existing deployment tools like SCCM or Group Policy. The Monthly Enterprise Channel offers the stability enterprises need while maintaining access to new features and security updates.

This tutorial walks you through creating a complete offline deployment infrastructure, from initial ODT setup through network-based installation and ongoing update management. You'll learn to configure enterprise-specific settings, handle licensing activation, and establish maintenance procedures for your Office 365 deployment.

Implementation Guide

Full Procedure

01

Download and Extract the Office Deployment Tool

Start by creating a dedicated folder and downloading the latest ODT version 16.0.16825.20102. This tool is Microsoft's official method for enterprise Office deployments.

Create the ODT directory:

mkdir C:\ODT
cd C:\ODT

Download the Office Deployment Tool from the Microsoft Download Center. Search for "Office Deployment Tool" or visit the official download page. Save the officedeploymenttool.exe file to your C:\ODT folder.

Extract the ODT files by double-clicking officedeploymenttool.exe. Accept the license agreement and the tool will extract setup.exe and sample configuration files to your ODT folder.

Verification: Check that C:\ODT\setup.exe exists and run setup.exe /? to see available commands.

Pro tip: Always use the latest ODT version as Microsoft frequently updates it with bug fixes and new features for enterprise deployments.
02

Create the Configuration XML File

The configuration XML file defines what Office applications to install, the update channel, and deployment settings. Create a file called configuration.xml in your C:\ODT folder.

Here's a comprehensive configuration for enterprise deployment:

<Configuration>
  <Add OfficeClientEdition="64" Channel="MonthlyEnterprise">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
      <ExcludeApp ID="Groove" />
      <ExcludeApp ID="Lync" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="0" />
  <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
  <Updates Enabled="FALSE" />
  <Display Level="None" AcceptEULA="TRUE" />
  <Logging Level="Standard" Path="C:\ODT\Logs" />
</Configuration>

Key configuration options explained:

  • OfficeClientEdition="64": Installs 64-bit version (recommended for enterprise)
  • Channel="MonthlyEnterprise": Uses Monthly Enterprise Channel for stability
  • ExcludeApp: Removes OneDrive for Business and Skype for Business
  • Updates Enabled="FALSE": Disables automatic updates for controlled environments

Create the logs directory:

mkdir C:\ODT\Logs

Verification: Validate your XML using an online XML validator or by running the download command in the next step.

Warning: Ensure you use the correct Product ID. O365ProPlusRetail is for Microsoft 365 Apps for enterprise, while O365BusinessRetail is for business plans.
03

Download Office Installation Files Offline

Now download the complete Office installation source files (approximately 4-6 GB) to create your offline installation package. This step requires internet connectivity but only needs to be done once.

Run the download command from your ODT directory:

C:\ODT\setup.exe /download C:\ODT\configuration.xml

The download process will create an Office subfolder containing all installation files. Monitor the download progress - it typically takes 15-30 minutes depending on your internet connection.

During download, you'll see output similar to:

Downloading Microsoft 365 Apps for enterprise in English (United States)...
Download has started...
Download completed successfully.

The final directory structure should look like:

C:\ODT\
├── setup.exe
├── configuration.xml
├── Logs\
└── Office\
    ├── Data\
    └── [Various .cab and .msi files]

Verification: Check that C:\ODT\Office contains multiple .cab files and the total folder size is around 4-6 GB.

Pro tip: If the download fails or gets interrupted, simply run the same command again. ODT will resume from where it left off rather than starting over.
04

Set Up Network Share for Enterprise Deployment

For enterprise-wide deployment, copy your offline installation files to a network share accessible by all target computers. This centralizes the installation source and simplifies management.

Create a network share on your file server. For example, on Windows Server:

mkdir D:\Shares\Office365Offline
net share Office365Offline=D:\Shares\Office365Offline /grant:"Domain Users",READ

Copy the entire ODT folder contents to your network share:

xcopy C:\ODT\* \\fileserver\Office365Offline\ /E /H /C /I

Set appropriate NTFS permissions on the share folder:

  • Domain Users: Read & Execute
  • Domain Admins: Full Control
  • SYSTEM: Full Control

Test network access from a client computer:

dir \\fileserver\Office365Offline

You should see the setup.exe, configuration.xml, and Office folder.

Verification: From any domain computer, run \\fileserver\Office365Offline\setup.exe /? to confirm network access works.

Warning: Ensure your network share has sufficient bandwidth. Multiple simultaneous installations can saturate network links, especially over WAN connections.
05

Deploy Office 365 to Target Computers

Now deploy Office to your target computers using the offline installation files. You can do this locally on each machine or remotely using deployment tools.

For local installation on each computer, run:

\\fileserver\Office365Offline\setup.exe /configure \\fileserver\Office365Offline\configuration.xml

For silent deployment via Group Policy or deployment tools, create a batch script:

@echo off
echo Installing Microsoft 365 Apps...
\\fileserver\Office365Offline\setup.exe /configure \\fileserver\Office365Offline\configuration.xml
if %errorlevel% equ 0 (
    echo Installation completed successfully
) else (
    echo Installation failed with error code %errorlevel%
)
pause

For PowerShell deployment across multiple computers:

$computers = Get-Content "C:\computers.txt"
foreach ($computer in $computers) {
    Write-Host "Installing Office on $computer"
    Invoke-Command -ComputerName $computer -ScriptBlock {
        Start-Process "\\fileserver\Office365Offline\setup.exe" -ArgumentList "/configure \\fileserver\Office365Offline\configuration.xml" -Wait
    }
}

Monitor installation progress by checking the log files:

type C:\ODT\Logs\*.log

Verification: After installation, check that Office applications appear in the Start menu and run winword /safe to test Word launches correctly.

06

Configure Licensing and Activation

After installation, users need to activate their Office applications using their Microsoft 365 enterprise credentials. This step requires internet connectivity on each client computer.

For user-based activation, instruct users to:

  1. Open any Office application (Word, Excel, etc.)
  2. Click "Sign in" when prompted
  3. Enter their organizational Microsoft 365 credentials
  4. Complete the activation process

For shared computer scenarios (RDS/Citrix), modify your configuration.xml to include:

<Property Name="SharedComputerLicensing" Value="1" />

Verify activation status using the Office Software Licensing Management Tool:

cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /dstatus

For bulk activation verification across multiple computers, use this PowerShell script:

$computers = Get-Content "C:\computers.txt"
foreach ($computer in $computers) {
    Write-Host "Checking activation on $computer"
    Invoke-Command -ComputerName $computer -ScriptBlock {
        $status = cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /dstatus 2>$null
        if ($status -match "LICENSE STATUS: ---LICENSED---") {
            Write-Host "$env:COMPUTERNAME: Activated" -ForegroundColor Green
        } else {
            Write-Host "$env:COMPUTERNAME: Not Activated" -ForegroundColor Red
        }
    }
}

Verification: Open Word and go to File > Account. You should see "Product Activated" and the user's Microsoft 365 license information.

Pro tip: For environments with limited internet access, consider using KMS activation or Active Directory-based activation for Office LTSC instead of Microsoft 365 Apps.
07

Enable Updates and Maintenance

Once deployment is complete, configure how Office updates will be managed in your environment. You can enable automatic updates or maintain centralized control.

To enable automatic updates after deployment, create a new configuration XML file called enable-updates.xml:

<Configuration>
  <Updates Enabled="TRUE" UpdatePath="" />
  <Display Level="None" />
</Configuration>

Apply the update configuration:

\\fileserver\Office365Offline\setup.exe /configure enable-updates.xml

For centralized update management, set up a local update source by downloading updates:

<Configuration>
  <Add OfficeClientEdition="64" Channel="MonthlyEnterprise">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add>
  <Updates Enabled="TRUE" UpdatePath="\\fileserver\Office365Updates" />
</Configuration>

Download updates to your update share:

C:\ODT\setup.exe /download update-config.xml

Monitor update status across your environment:

Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Microsoft 365*"} | Select-Object Name, Version, InstallDate

Verification: Check Office update settings in any Office app under File > Account > Update Options to confirm your configuration is applied.

Warning: Automatic updates can consume significant bandwidth and may introduce compatibility issues. Test updates in a pilot group before enterprise-wide deployment.

Frequently Asked Questions

Can I deploy Office 365 offline without internet on target computers?+
Yes, once you download the installation files using ODT, target computers don't need internet for installation. However, they will need internet connectivity later for license activation and to sign in with Microsoft 365 credentials. The actual Office applications and features work offline after activation.
What's the difference between Monthly Enterprise Channel and other update channels?+
Monthly Enterprise Channel provides monthly feature updates with additional validation and testing time compared to Current Channel. It offers a balance between new features and stability for enterprise environments. Semi-Annual Enterprise Channel updates only twice yearly for maximum stability, while Current Channel updates immediately when features are released.
How much disk space do I need for Office 365 offline installation files?+
The complete Office 365 installation source requires approximately 4-6 GB of disk space, depending on the languages and applications included. Each target computer needs about 4 GB for the actual Office installation. Plan for additional space if you're hosting multiple language packs or update files on your network share.
Can I exclude specific Office applications during offline deployment?+
Yes, use the ExcludeApp element in your configuration XML to remove unwanted applications. Common exclusions include OneDrive for Business (Groove), Skype for Business (Lync), and Microsoft Teams. This helps reduce installation size and prevents deployment of applications your organization doesn't use or has alternatives for.
How do I handle Office 365 updates after offline deployment?+
You have three options: enable automatic updates for internet-connected computers, set up a local update source by downloading updates with ODT to a network share, or disable updates completely for locked-down environments. Most enterprises use a hybrid approach with centralized update management through tools like WSUS or SCCM for controlled rollouts.
Emanuel DE ALMEIDA
Written by

Emanuel DE ALMEIDA

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...