As part of a move away from standard OS deployment with SCCM toward Windows Autopilot with Intune, one of the usual key component is managing the installation of Office 365. Intune provides a built-in way of creating the application.
While the end result will remain the same as other methods of installing Office 365, one of the great benefits of using this method is that it can automatically install the latest build available for the chosen channel, without a need for administrative modifications.
In this post, we will detail how to prepare Office 365 application with Intune.
This post is part of a series on Windows Autopilot that will be published in the following weeks. In the next posts, we will cover the following subjects :





Remember that OneNote 2016 is to be deprecated in favor of the modern app.

If you wish to convert an actual 32-bit installation to 64-bit, you will need a provide the configuration via the Enter XML data wizard. See our post about changing 32-bit to 64-bit for help on the XML configuration.


When using this deployment method, it will take advantage of the Enrollment status page when using Windows Autopilot. This means that computer being configured by Windows Autopilot will prevent a user from login in until Office is actually installed on the computer.

Otherwise, the end-user experience will be the exact same as using SCCM to deploy Office 365.

For more details, see Microsoft docs
[ratings]
Please fill out the form, and one of our representatives will contact you in Less Than 24 Hours. We are open from Monday to Friday.
Thank you for subscribing to our newsletter or requesting a quote. You will receive our next month's newsletter. If you have requested a quote, we will get in touch with you as soon as possible.
Something went wrong!
Thank for your reply!