Systems Management

Lessons Learned from Microsoft 365 Deployment with ConfigMgr: Part 3 – Self Service Deployments

Topics: Systems Management

Lessons Learned from Microsoft 365 Deployment with ConfigMgr

Part 3: Self Service Deployments

Hey Team. In this post I’m going to cover how we’re doing our Self Service Deployments for the Microsoft 365 Apps. We’re controlling it via Active Directory Group Membership.

Our Deployment team can add users into these groups in AD that will then have access to the Apps.

User Collections.

Each User Collection has a direct rule of the AD Group.

There is no point to have it update since this is done at the AD level.
On the Semi-Annual Enterprise Channel User Collection, we have 3 deployments.

The rest of the collections only have one deployment, the deployment for the corresponding application. I’ll be going over the Microsoft 365 Self-Service Notification Baseline in depth in the next post.

Microsoft 365 Content is a required deployment, ASAP, so that it gets the M365 Installer Content down to the machines as soon as it can. I go over that content a bit more in a previous post.

The Microsoft 365 Office – Semi-Annual Enterprise Channel is a required deployment set out for 10 years.

It is also hidden:

We don’t want to force the software down. Instead, we want it to be available for them to install themselves. However, we don’t want it to show up until the required content is completely downloaded, so we keep it hidden until it’s downloaded, then we have that Baseline come along and flip some properties in WMI to change it from Hidden and Required, to Show in Software Center and be Available. I’ll cover that more in the next post as well.

As a Bonus, here is the script I used to create the AD Groups and User Collections.

It looks through CM, finds all of the Applications that start with Microsoft 365 (excluding anything with Content in the name) then uses that name to base the AD Group and CM User Collections on.

Check it out on GitHub. I plan to add the lines that will automatically create the deployments as well. Note, I created it in about 10 minutes and used it once in my lab, so no real testing has been done… be warned.

Conclusion: Self Service Deployments in Microsoft 365

Thanks for checking out the post and after this series, if you have questions, please let me know and I’ll see where I can fill in any blanks. – Gary


Lessons Learned from Microsoft 365 Deployment with ConfigMgr

After sharing my series on deploying Microsoft 365 with ConfigMgr, this follow up series details lessons learned by “someone” during a recent large-scale deployment.

  1. Microsoft 365 Deployment with ConfigMgr – Lessons Learned 
  2. Microsoft 365 Deployment with ConfigMgr- Lessons Learned – Changing Channels
  3. Microsoft 365 Deployment with ConfigMgr- Lessons Learned – Deployments – You are Here
  4. Microsoft 365 Deployment with ConfigMgr – Lessons Learned – ConfigMgr Baseline
Right Click Tools icon

Right Click Tools Community is just a download away.

A free, limited, and powerful add-on, Right Click Tools Community offers a taste of the full suite of tools.

Back to Top