MicrosoftMicrosoftDear John_Cable Joe_Lurie
I don't conclude with this change it might make sense from your point of view.
On the other hand all the sudden changes on support lifecycles distrust any relationship to partners and professionals and software developers because you carefully plan them into actions and preach to #staycurrent and not only preach, but implement needed actions at high costs at the beginning for the sake of perfect structures that lowers costs for the future. This was your model at MSFT too and it works out.
If you keep changing the support cycles that arbitrary I promise you customers will lean on this as "this has been done in the past" if there is just enough public pressure from big customers or partners.
You extended the extended support phase of Exchange 2010 and Office 2010, Office 2016 equally to office 2019, translates for customers why should it buy 2019 when 2016 is cheaper with the same support cycle.
Please stop these changes.
The channels like SAC etc have been renamed multiple times.
Now we have seen multiple times of support cycle changes on Windows 10 peaking in 30 months only for Business and Edu but only with H2 releases.
IF we had the commitment that it will stay like this with 1903 and 1909 having same updates and category for 2004 and 2012, then it is all OK, but the changes are just causing confusion if you don't follow your own schemes once created.
I hope you get my point and stop changes to the support policy in Windows 10 for the next years.
I am unpleased that Microsoft does not publish the telemetry about Windows 10 fragmentation like Google did. We need to know how many million devices run unsupported OS which is a threat to the safety of us all connected to the Internet.
Please don't take this post as a rant. It is not. My personal business experience doesn't mean the world but I know that customers start to distrust policies and investments to #staycurrent when they are changed "as appropriate".
MSFT had 5 years to get this model well shaped.
