Configure a machine to use Current Branch for Business with Windows 10

Q. How can I configure my Windows 10 machine to use Current Branch for Business (CBB)?

A. Windows 10 has shifted from features being delivered with new versions of Windows every few years to instead using a cadence of new features constantly being delivered throughout the year in new builds of Windows 10, essentially Windows-as-a-Service (WaaS). The exact cadence is not known as this point but it is expected to be every 3-4 months. Users can first start to experience and test the new features by being part of the Insider Preview branch/builds. Once features have been tested both internally by Microsoft and by the Insiders the features are released to the broad public as the new Current Branch (CB). Many businesses do not want the new features straight away and instead prefer to additionally delay to ensure the new features are tested even more broadly and to enable internal testing which is the Current Branch for Business (CBB) which will be one cycle behind the Current Branch (i.e. 3-4 months). Organizations that have enterprise deployment technologies will be able to further delay the deployment of the CBB to their internal systems for an additional duration which is not exactly known at this time but based on Group Policy it appears to be 8 months, i.e. a solution such as Windows Update for Business and other MDM solutions.

For organizations thinking about how to test and deploy Windows 10 I would think of it this way:

If you do not have an enterprise management solution but wish to use the CBB this can be done through a simple change on your Windows machine:

That's it! It can also be configured to machines using Group Policy (and MDM type solutions):

Note there is also the Long Term Servicing Branch (LTSB) but this is for machines that are not interested in innovation and instead need the highest levels of stability such as kiosks, ATMs and so on.