

DBA was essentially a field solution created to help EDU organizations quickly and successfully deploy Office 365 Pro Plus client to their devices so students, faculty and staff could take advantage of the latest updates to Office 365, instead of running legacy, feature-limited Office 9 clients.

So, if the outcome is the same, why the change in deployment technologies? There are a number of reasons, but I would argue the biggest is support.
Office 365 proplus apps how to#
I’m also going to touch on how to migrate from DBA to DBS, should that be your case. In August 2019, Microsoft officially announced DBS so I want to go into a little bit of depth what’s different from DBA, and how to configure and deploy DBS in your environment. I would highly recommend a look-see at the previous blog if you want some historical background. Today, I’m excited to provide a follow up to that post with how to deploy Microsoft 365 Apps with Device-based Subscription (DBS), sometimes referred to as Device-based licensing, using both ConfigMgr and Intune. In that time, the blog post has accumulated over 20k views from schools all over the world! So thank you to everyone for making it so successful and I hope it served as a great resource! Hopefully, you will find this post as valuable as the last one. Hi there! It’s been a while! The last blog I wrote was roughly two and a half years ago, where I wrote a step by step guide to deploy Office 365 ProPlus with Device Based Activation (DBA) with SCCM. In addition the OSD section has been updated and a new section called “DBA Clean Up”. The majority of this post has been updated to reflect those changes.
Office 365 proplus apps update#
Update 5/13/20: Microsoft has recently updated the name of “Office 365 ProPlus” to “Microsoft 365 Apps”.
