Deploy Office 365 Updates Using SCCM

This post is a step by step guide to deploy Office 365 updates using SCCM. SCCM makes it easy not to deploy Office 365 but to manage office 365 software updates as well. In my previous posts, I covered on deploying Office 365 using SCCM. I also posted Office 365 client management dashboard details.

After you deploy Office 365, deploying software updates is the next major task. SCCM has the ability to manage Office 365 client updates by using the Software Update management workflow.

Office 365 updates when deployed to client computers are first downloaded in local client cache. Since Office 365 client updates are huge, ensure that you configure the cache settings prior to deployment. Starting with SCCM 1606, you can specify the cache folder size using client settings in the Configuration Manager console.

Step-by-Step Guide to Deploy Office 365 Updates Using SCCM

To deploy Office 365 updates using SCCM, you need to configure some basic steps. Once you configure these steps, you can quickly deploy Office 365 updates using configuration manager.

Step 1 – Verify the Requirements

To deploy Office 365 updates ensure you meet the below requirements.

Your setup must have at least SCCM 1606 or later version of SCCM running.

An Office 365 client and Supported channel version for Office 365 client.

Windows Server Update Services (WSUS) 4.0

If you have met all the above requirements, you can proceed to step 2.

Step 2 – Configure Software Update Points

I am sure you would have configured software update point because that is required to deploy updates. However if you not configured your software update point, then you can follow this post.

Under Software Update Point component properties, click Classifications tab. Ensure that Updates classification is checked. In addition to this, if you make any other changes, remember to synchronize software updates once.

Step 3 – Enable Office 365 clients to receive updates from SCCM

With Configuration Manager version 1606 and above, you can easily manage Office 365 client agent. This setting is part of Configuration Manager client settings. Once you configure this setting, the SCCM client agent talks to Office 365 client agent to download the updates from a distribution point and install them.

In step 2 we configured SUP to include Office 365 updates. We will now go through the steps to deploy Office 365 updates using SCCM.

After running software updates sync, i have got some more Office 365 updates. All these updates won’t be deployed. Looking at my Office 365 client edition, the current build is 9126.2275. Out of all the updates, I use search criteria to filter out the updates. In the below screenshot, i have set to filter updates that aren’t expired and date release is less than or somewhere between 10 days. The basic idea is to deploy updates that are released recently.

Step 4.1 – Download Office 365 Updates

In some organizations you will find both x64 and x86 versions of Office 365 client deployed. If you have got only Office 365 x86 client deployed, you can select only x86 client based edition updates and proceed. In this example, I am selecting both x64 and x86 edition Office 365 client update – Semi-Annual channel version 1803 updates. Select the updates, right click and click Download.

Create a new deployment package. Specify name and path to store the updates. Click Next.

Hi, I am Prajwal Desai. For last few years I have been working on multiple technologies such as SCCM / Configuration Manager, Intune, Azure, Security etc. I created this site so that I can share valuable information with everyone.

Hi Prajwal Desai, can I deploy O365 deployment to any specific client?

0

Reply

Rajesh Rajput

February 6, 2020 6:51 pm

can we install click to run update silently with commands like /s

0

Reply

Ulf Andersson

October 10, 2019 1:37 pm

Great work!

0

Reply

Matt R

September 20, 2019 6:57 pm

Great walk through. Thanks Prajwal!

0

Reply

Matt

August 21, 2019 2:44 am

Hello everyone.

I have a different builds of office 365 in our environment, i am newbie in the update process.

We have Semi-annual Channel clients in builds 1803 and 1808.

Can I made a only Software Update Group with the different updates to the builds and deploy this update group to all clients? or must create different Software Update Group and different collections for each build?

Best regards

3

Reply

Jesse T

August 17, 2019 1:19 am

Prajwal,

So, if I my O365 build is the monthly one, then I’d want to download the monthly updates, correct?

0

Reply

Noel

June 26, 2019 12:11 am

I am having trouble downloading the updates using the wizard. It fails with “Error: failed to download content id 16872757. Error: Incorrect function”

0

Reply

mela

May 14, 2019 12:36 pm

Hi, can oyu give a tipp on this?

my Client have the version 1803 9126.2259 and I am trying to update to 9126.2382 wihtout success (Client already Compliant). Intresting is that any update under Office 365 Updates is requiered, i get a lot of installed, compliant, but any are requiered…..

what I am missing hier?

note: management of the Office 365 client agent, is enable.

BR Mela

0

Reply

George Khouri

May 10, 2019 11:48 am

I have an issue with the Update, SCCM is not pushing the updates if 1) you have both installation and update in same SCCM package, or if i created a separate package.

0

Reply

Gianpaolo

April 5, 2019 12:45 am

hello together, is it possible to reject individual security updates as before by SCCM or to uninstall after an installation because of problems (eg Outlook archive can not be searched anymore) I’m not interested in the assignment of feature updates that has been well explained, I really want to know if I have a system that every 6 months a new feature update may receive if I still monthly allow the individual security updates or reject? With Office 2016 or older, it is possible to allow or reject individual KBs, is this also possible in Office 365? Have a nice… Read more »

0

Reply

Richard Bruce

January 31, 2019 9:09 pm

Hi. Has anyone come across an issue where the base version doesn’t update? i.e. User has 1705 installed so only updates to 1705 are deployed. We need to update to 1808 and keep on latest versions as they are released. Has anyone figured out how to do this?

Hi, you’ve deployed them manually, but I can you automate this? I’ve tried to deploy (available) multiple builds (even previous ones) to a pc and it showed all the updates instead of just showing the newer ones for that channel, which I think should have been the behavior.

Thks

0

Reply

Sokoban

September 25, 2018 2:02 pm

Hi , great article. Would have been good if there was an article How to Troubleshoot Office365 Software Updates and how the files download from the cloud. 😉

Currently they most of them are in 16.0.8431.2236 and i tried to upgrade to 16.0.9126.2259. Tried them on few test machines and i am facing a weird issue. It shows complaint in SCCM but the office version still remains the same(old version). have rebooted, ran the machine policies but no luck. Any leads please