Update 7/15/2019: As a reminder to customers on Windows 10, version 1809 using Windows Update for Business with a Branch Readiness Level set to Semi-Annual Channel and a default 0-day deferral, your ...
Updated Jul 15, 2019
Version 8.0
Blog Post
In my opinion this is a step backwards. It has been the recommendation from the begging to move to a continual release model adopting with the adoption of incremental release periods. This has been a model that has worked from the begging whether it is named CB \ CBB or SAC-T \ SAC-B , the point is that we know when we are at day zero. We also know we still have a version that may have not been tested across the business ecosystem and that 4 to 6 month later we will be notified of Business ready version. We also know we have this time to address issues with vendors.
I do not see how this new change to remove Sac-T is being made to align with Office 365 when Office utilizes a First release \ targeted channel as well . https://docs.microsoft.com/en-us/officeupdates/update-history-office365-proplus-by-date
Seem to be a disconnect here. Specially if you view the image that illustrates the release history for Office 365 ProPlus or if you look at the version information from the Office aplication itself.
image from Outlook Desktop application.