This is exactly what I was getting at. For individuals and small organizations that often have no dedicated IT staff at all, they're the ones who'll get hit by Microsoft's forced-upgrade policy.
But for any large organization with deployed Windows systems, that absolutely requires a managed Windows environment for an ocean of reasons. That means a competent Windows IT staff that handles all those things, including: security configuration and updates, controlled testing and release of updates, data retention and deletion policies, and on and on.
For such shops, handling a change like this from Microsoft is already day-in-the-life. They already have to vet updates that may (and do) break business-critical software, while also ensuring that critical security updates are pushed out in a timely manner, etc.
But for any large organization with deployed Windows systems, that absolutely requires a managed Windows environment for an ocean of reasons. That means a competent Windows IT staff that handles all those things, including: security configuration and updates, controlled testing and release of updates, data retention and deletion policies, and on and on.
For such shops, handling a change like this from Microsoft is already day-in-the-life. They already have to vet updates that may (and do) break business-critical software, while also ensuring that critical security updates are pushed out in a timely manner, etc.