It can be configured via Intune, ConfigMgr, Group Policy, or heck … registry settings (please … don’t do that).
It’s important to note that since WUfB is part of the Windows OS instead of its own product that it isn’t exclusive to Intune. If you have servers, this isn’t the solution you are looking for (I’ll get to that one at some point). Heck, Intune as a whole really isn’t for them. If you still have Windows 7 or older operating systems then Intune patching isn’t for those devices. Which leads to the first limitation of WUfB: it’s only for the Windows 10 operating system.
Specifically, it’s a set of new Windows Update configuration options for Windows 10. WUfB is simply an evolution of the Windows Update configuration built into the Windows OS. It sounded a lot like a new product, maybe a successor the to cranky old guy who lives on the corner: WSUS. When WUfB was first announced back in 2015 there was a fair amount of confusion about what it really was. Instead, with Intune you can manage the endpoint’s Windows Update for Business (WUfB) configuration. At least not in the way that ConfigMgr has a patching solution. The first thing to get straight is that Intune doesn’t really have a patching solution. In the second part I’ll talk more about what I like, what I don’t, and generally try to outline where I think this solution fits in the buffet of patching solutions. In this first part I’m going to try and cover the technical details and make sense of some of the docs. I helped implement Intune at work ( Recast Software) which was a great opportunity to dig into the patching side of things.