Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

5.1.2. Deploying Microsoft 365 Apps with Intune, the ODT, and Autopilot

💡 First Principle: Microsoft 365 Apps isn't installed from a package you upload — it streams from Microsoft's content network, guided by a small configuration file that says which apps, languages, architecture and update channel to use. Every deployment method is just a different way of handing the device that configuration. Pick the method by asking who else is installing software at the same moment: during Autopilot, the answer changes everything.

Picture a 300-person firm rolling out new laptops. Some devices are already in use and just need the suite; others arrive fresh from the manufacturer through Autopilot. You have three tools, and they overlap.

The built-in Intune app type. Choose Apps > All Apps > Create > Microsoft 365 Apps > Windows 10 and later. The suite appears as a single app, and you configure it with either the Configuration designer (pick apps such as Word and Excel, other licensed apps such as Project Online desktop client and Visio Online Plan 2, architecture, update channel, version, shared computer activation, languages and whether to remove other versions) or Enter XML data, which accepts an Office Deployment Tool configuration file. Microsoft 365 Apps for business is supported only through XML data. Under the hood, Intune uses the Office CSP, and the device downloads from officecdn.microsoft.com. Required assignments install silently; Available assignments appear in Company Portal.

Several rules make good exam distractors. If older MSI-based Office is present, you must select Remove MSI or the install fails — and it removes all Office MSI apps, not just the ones you picked. Only one Microsoft 365 Apps deployment is delivered to a device, so you can't layer two. The 64-bit edition installs only on 64-bit devices. Activation requires Microsoft 365 Apps licenses. And open Office apps during the install can make it fail.

The Office Deployment Tool (ODT) is two files, setup.exe and configuration.xml. Its modes are /download, /configure (install, remove or update, which requires local admin), and /customize (apply only application preferences). Microsoft's best practice is to build the XML with the Office Customization Tool at config.office.com rather than by hand. A few elements matter: <Display Level="None" AcceptEULA="TRUE" /> gives a silent install, <RemoveMSI /> removes older MSI Office first, and ExcludeApp drops apps such as Publisher or Teams. If no channel is set and Office isn't installed, the default is Current Channel; an enabled Group Policy Update Channel setting overrides the ODT's channel value.

Update channels changed in 2026. The primary channels have been Current Channel (features at least monthly, the default for Microsoft 365 Apps), Monthly Enterprise Channel (once a month on the second Tuesday, each version supported for three months) and Semi-Annual Enterprise Channel. Beginning with Version 2606 (July 2026), Semi-Annual Enterprise Channel unified with Monthly Enterprise Channel: those devices get the same feature and security updates as Monthly Enterprise and show "Monthly Enterprise Channel" in File > Account, with no admin action needed. Channels are set per device, not per user.

During Autopilot, the built-in type is the wrong tool for classic Autopilot. It isn't managed by the IME, so it can run at the same moment as an ESP-tracked Win32 install and make the ESP fail; the ESP documentation lists it as a known cause of hangs. Microsoft's recommendation is to deploy Microsoft 365 Apps as a Win32 app: package the ODT setup.exe and your configuration.xml into a .intunewin file and use setup.exe /configure configuration.xml as the install command. Autopilot device preparation is different — it supports the Microsoft 365 app type among its up to 25 essential apps, installing LOB and Microsoft 365 apps before Win32, Store and Enterprise App Catalog apps.

What breaks most often? A conflicting settings catalog policy that sets a different update channel or version than the deployment can cause unexpected behavior, including reinstallation. For troubleshooting, the Office CSP reports status codes such as 997 (installing), 0 (success), 1603 (failed a prerequisite check, for example an MSI Office still present) and 17002 (canceled or out of disk).

⚠️ Exam Trap: When Microsoft 365 Apps must install as a blocking app during classic Autopilot, the answer is a Win32 app built from the ODT, not the built-in Microsoft 365 Apps type. The built-in type runs outside the IME and can collide with ESP-tracked Win32 installs — the same Trusted Installer collision that rules out mixing Win32 and MSI apps.

Reflection Question: A device already has Office 2016 MSI installed, and you assign the built-in Microsoft 365 Apps type without selecting Remove MSI. What happens, and why might enabling Remove MSI surprise the user who relies on Visio 2016?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned