Preface: So I wrote this blog series about a week before Microsoft decided to change the product name from Office 365 to Microsoft 365, then rebrand the office channels and add a new one.
While I'm going to do my best to update these posts, I'm sure I'll miss some references, so I apologize now for any inconsistencies. As always, feel free to him me up on twitter to ask any questions. - Gary Blok (@gwblok)
Now, one to the first post:
This post will go over the Deployment and Maintenance of Office 365 using Microsoft's Endpoint Manager, Configuration Manager (MEMCM / SCCM). In this series we will cover:
Configuration Manager has a node dedicated to Office 365. [MS Docs] We're going to leverage it for this series, but I'll also point to parts of the process that can be done outside of CM for additional flexibility. We're also going to cover prerequisites for these features. [MS Docs]
I've added these to the main Default Client Settings, but showing them in a new Client Setting for example. First one is enabling CM to manage the Office Updates. [MS Docs]
Hardware Inventory for Office Information [MS Docs]
Let's add Office 365 updates to our software updates list. [MS Docs]
Note, in POST 5, I got much more in depth and show more images about getting updates going, then monitoring systems, but for now, just the basics.
Now let's create the ADR [MS Docs]
Ok, now we've got everything in place to support Office 365. In the next post we'll go over making the actual office deployment.
Check out all posts within this series:
Office 365 Deployment Series with MEMCM - Post 2 - Creating the Office Installer - Simple
Office 365 Deployment Series with MEMCM - Post 3 - Creating the Office Installer - Advanced
Office 365 Deployment Series with MEMCM - Post 4 - Deployment Methods
Office 365 Deployment Series with MEMCM - Post 5 - Office Updates / ADR
