SharePoint 2010 and 2013 Workflows Kaput in Office 365

Workflow Retirement Series TOC​

Part 1 – SharePoint 2010 and 2013 Workflows Kaput in Office 365
Part 2 – Finding All the SharePoint 2010 Workflows in SharePoint Online
Part 3 – Find Only the Active SharePoint 2010 Workflows in SharePoint Online 
Part 4 – Use PowerShell to Work with SharePoint 2010 Workflow Scan  ​

Hot off the presses! Today Microsoft announced the SharePoint 2010 workflow retirement in Office 365. They sort of buried it, but SharePoint 2013 workflows are meeting the same fate. Here’s a quick breakdown of the dates where stuff stops working:

SharePoint 2010 workflows turned off for new tenantsAugust 1, 2020
SharePoint 2010 workflow turned off for ALL tenantsNovember 1, 2020
SharePoint 2013 workflow turned off for new tenantsNovember 1, 2020
SharePoint 2013 workflow turned off for ALL tenantsTBD

The following built-in workflows will also be removed; Approvals, Collect Feedback, Collect Signatures, Classic pages publishing Approval, and Three-state.

How do you know which workflow engine your workflows are using? It doesn’t really matter. They’re both going away. They should both be replaced with Power Automate flows. If you’ve been putting it off, now is the time to get on it. You do, however, need to know where all of these workflows are in your tenant. Microsoft has a tool, the SharePoint modernization scanner, that will search out classic workflows, among other things. It’s pretty painful tool to use, so I wouldn’t break it out late in the afternoon on Halloween. If I’m feeling sadistic, I may make a walkthrough of it. Once you have a good handle on where the workflows are being used in your tenant you can decide which ones to jettison, and which ones get to be reborn into flows.

Let me know what you think about it. Let me know how this impacts you. The July 15th, 2020 episode of Ask Sympraxis will cover this topic. Join us. It’s free. It’ll be a hoot, and worth every penny you spend on it.

tk

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *