I’m writing this blogpost to help understanding what happens when you are deploying Office Pro Plus on a Intune managed device.
First of all Office 365 installation is not a application installation in traditional sense!!
It is not the same as a Win32 app deployed from Intune that are using the Intune Management extension (IME) or MSI LOB app deployment that are using the build-in MDM stack in Windows 10.
Office Pro Plus installation from Intune is a policy – a CSP policy
That is also the reason why you cannot create a dependencies from a Win32 app installation, on a Office Pro Plus app in Intune. The example I often get is, can we create a Win32 app that are installing a plugin for Office only if Office is already installed.
Trouble shooting is also different for Office Pro Plus installation as you need to look for different thinks on the end user device and not in the IME logs.
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeCSP
In the Default key there is a link to http://go.microsoft.com/fwlink/?LinkID=829801 – that link point to installation of setup.exe
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeCSP\9725059b-1892-443f-bee1-509ca15c0c16
In Default you can see the configuration.xml file that are used to install Office Pro Plus
Here is the default configuration.xml from the Intune installation. If you need other settings in your installation you can upload a custom configuration.xml file into Intune.
<Configuration><Add Channel=”FirstReleaseCurrent” OfficeClientEdition=”64″ MigrateArch=”TRUE”><Product ID=”O365ProPlusRetail”><ExcludeApp ID=”Access” /><ExcludeApp ID=”Groove” /><ExcludeApp ID=”InfoPath” /><ExcludeApp ID=”Lync” /><ExcludeApp ID=”OneNote” /><ExcludeApp ID=”SharePointDesigner” /><Language ID=”MatchOS” /><Language ID=”MatchPreviousMSI” /></Product></Add><Display Level=”None” AcceptEULA=”TRUE” /><RemoveMSI /><Property Name=”SharedComputerLicensing” Value=”0″ /><ExecCount xmlns=”http://schemas.microsoft.com/intune”>1</ExecCount><LastExecuteTime xmlns=”http://schemas.microsoft.com/intune”>4/12/2020 9:04:16 AM</LastExecuteTime></Configuration>
FinalStatus:
- When status = 0: 70 (succeeded)
- When status != 0: 60 (failed)
In file:///C:/Users/Public/Documents/MDMDiagnostics/MDMDiagReport.html you can also see that Office is installed
The end user will also get a notification when you Office Pro Plus is finish installing.
Happy deployment
Read more:
Office CSP
Description of Office 365 Desktop Setup Tool logging errors
Cloud First 
Hey! You have a link for “Office 365 Desktop Setup Tool” at the Read More section. How would you use this for installations of O365 that are done through Intune?
Is the ID consistent? I just reset a machine and got a different identifier under the OfficeCSP key. Would there be a reason why it could be different?
I have excluded Skype for Business from the installation yet it still installs. What would cause this behavior?
“The end user will also get a notification when you Office Pro Plus is finish installing.” If only… (sigh). Our users get no notice and the Portal doesn’t update when O365 is completed, only after the user restarts the PC.
Thanks for sharing this info, this was really enlightening!
I am struggling a little bit with re-installation and migration of Microsoft 365 Apps.
Do you know if there is a way to force a client to re-evaluate the installation status of 365 Apps?
(Just like you can do with Win32-apps by deleting the corresponding key under ..\IntuneManagementExtension\Win32Apps in the registry and the restarting the IME service)
Just as Tony ,I am also very interested in knowing if you know how to force a client to re-evaluate the installation status of 365 Apps?
(Just like you can do with Win32-apps by deleting the corresponding key under ..\IntuneManagementExtension\Win32Apps in the registry and the restarting the IME service)