How do I install Office 365 using Device Based Activation?

Summary

Microsoft has recently changed how Windows devices need to license Office 365 installations on a per-device basis, now called Device-Based Activation. These are the instructions to deploy Office to allow for licensing via device based activation.

Body

Microsoft has updated the licensing requirements for Office 365 installations on Windows devices, now referred to as Device-Based Activation. Below are the instructions for deploying Office to enable licensing via Device-Based Activation.

Prerequisites for Device-Based Activation Licensing

  • Version 1907 or later of Microsoft 365 Apps for enterprise [1].
  • The device must be Microsoft Entra joined or Microsoft Entra hybrid joined
  • The device must be running a supported version of:
    • Windows 10*
    • Windows 11
    • Windows Server 2019 or later

* Microsoft 365 apps will no longer be supported on Windows 10 after it reaches end of support on October 14, 2025

Step-by-Step Instructions

Verify Windows Version

Ensure your devices are running a supported version of Windows using:

  • PowerShell or Command Prompt: Type winver to get the version information.
  • Settings: Navigate to Settings > System > About and scroll to the "Windows specifications" section.

Ensure Microsoft Entra Join

Make sure your devices are Microsoft Entra joined or hybrid joined. For more information, refer to the following knowledge base article:

Deploy Microsoft 365 Apps for Enterprise

Deploy the latest version of Microsoft 365 Apps for enterprise using Device-Based Activation as the licensing method.

For Non-Endpoint Management Service Users:

  • You will need to create your own installer using the instructions below.

Create Your Own Microsoft 365 Installer

NOTE: There are two ways to host your source files for installing Office 365: MS Cloud and Local. Local allows your devices to utilize the same content within the UIC network without having to re-download all the installation files. Cloud deployments will download the content directly from Microsoft each time the installation is run.

Cloud Deployment

  1. Download the Office Deployment Tool from https://www.microsoft.com/en-us/download/details.aspx?id=49117

    • Run the self-extracting executable.
    • Place extracted files into a shared folder accessible by your devices.
  2. Create a Configuration File:

    • Navigate to the Office Configuration Tool in a web browser.
    • On the left navigation pane, click Customization to expand and select 'Device Configuration'.
      • Click on the "+Create" button and proceed through the wizard to customize your installation.
      • Refer to Microsoft's documentation for more information on the available settings
        • In the "Products and Releases" section, leave "Latest" selected.
        • In the "Installation" section, select "Office Content Delivery Network (CDN)".
        • In the "Licensing and activation" section, select "Device based".
        • Export the configuration file and move it to the same location as the Office Deployment Tool.
  3. Deploy/Install on a Device:

    • From an Administrator command prompt, run the Office Deployment Tool in configure mode: \\PATH-To-SETUP\setup.exe /configure \\PATH-TO-CONFIG\config.xml
    • If the installation is silent, check the task manager for the Click-to-Run executable running.

Local Deployment

  1. Create Shared Folders:

    • Create a folder to store your files.
    • Create a folder to store the Office Deployment Tool and configuration file.
  2. Download the Office Deployment Tool:

    • Run the self-extracting executable.
    • Place extracted files into the folder created in step 1b.
  3. Create a Configuration File:

    • Navigate to the Office Configuration Tool in a web browser.
    • On the left navigation pane, click Customization to expand and select 'Device Configuration'.
      • Click on the "+Create" button and proceed through the wizard to customize your installation.
      • Refer to Microsoft's documentation for more information on the available settings
        • In the "Products and Releases" section, leave "Latest" selected.
        • In the "Installation" section, select "Office Content Delivery Network (CDN)".
        • In the "Licensing and activation" section, select "Device based".
        • Export the configuration file and move it to the same location as the Office Deployment Tool.
      • Export the configuration file and move it to the folder created in step 1b.
  4. Download Installation Files to Shared Folder:

    • From a command prompt, run the Office Deployment Tool in download mode:
     \\PATH-To-SETUP\setup.exe /download \\PATH-TO-CONFIG\config.xml
    
    • Verify the downloaded files appear in the folder created in step 1a.
  5. Deploy/Install on a Device:

    • From an Administrator command prompt, run the Office Deployment Tool in configure mode: \\PATH-To-SETUP\setup.exe /configure \\PATH-TO-CONFIG\config.xml
    • If the installation is silent, check the task manager for the Click-to-Run executable running.

Verify Device is Obtaining a License

  1. Log onto the device.
  2. Launch a Microsoft Office application (e.g., Word or Excel).
  3. Click on Account.
  4. Under Product Information, it should say:
   Belongs to: This device

Potential Issue: Microsoft Teams Not Installing

Microsoft Teams installs per user. When you install Office 365 with Teams included, the installer drops the Microsoft Teams installer in:

C:\Program Files (x86)\Teams Installer

When a new user signs on, it will install Microsoft Teams for them. For existing accounts, run the installer manually or execute it silently through a script or command prompt:

C:\Program Files (x86)\Teams Installer\Teams.exe /s

If you experience any issues with licensing Office with Device-Based Activation, please submit an Endpoint Management support request at https://help.uillinois.edu/TDClient/37/uic/Requests/ServiceDet?ID=711

References
[1] Device-based licensing for Microsoft 365 Apps for enterprise

Details

Details

Article ID: 753
Created
Fri 1/15/21 7:05 PM
Modified
Tue 4/15/25 9:36 PM