Support update for SharePoint 2010 workflows in Microsoft 365

Agree that this is getting to be a habit where the dates we've been given cannot be trusted. We use these product lifecycle dates to plan for depreciation but when an announcement comes out like this, that effectively changes support for SharePoint Designer [might I remind you that the workflow types in SPD 2013 are part of the tool and "supposed" support?] by nearly six years, that it does come down to a matter of trust. I agree with the statement about InfoPath, and despite the above I would not "trust" that your 2013 workflows will be safe either. 

Yes, I hear you when you say why are you using legacy workflows when you should be using the newer ones available. Actually we are. And we use the end of support dates to "plan" since many of my peers globally who have been in the business long enough have been using SP Designer. To have plans escalated six years.....is ridiculous. I'm sure there will be a lot of uproar over this. 

Finally, all of us use legacy tools. If you use IE11 to access something that won't work in anything else, if you're using classic sites, and older software. Heck, if you're running Windows 7 or 8, you're using legacy software. If you're an IT professional that's been around for any length of time, if you think hard enough, you have or had recent experience with something "legacy". Again, moving from legacy software is something that needs to be done carefully and often over time. We depend on these "sunset" dates for planning purposes. And the new stuff? I can tell you that even in "Flow" or what's called Power Automate, they've already "depreciated" things without any notice at all. So it's not the age of the tool, it's the principal of saying you're going to support something until 2026, and then gutting it six years early and expecting everyone to be happy about it.