Todd Klindt's Office 365 Admin Blog

Quick Launch

All Site Content

Todd Klindt's home page > Todd Klindt's Office 365 Admin Blog > Posts > SharePoint 2010 and 2013 Workflows Kaput in Office 365

July 06

SharePoint 2010 and 2013 Workflows Kaput in Office 365

by Todd O. Klindt

on 7/6/2020 9:37 PM

Category: Office 365; SharePoint

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 tenants	August 1, 2020
SharePoint 2010 workflow turned off for ALL tenants	November 1, 2020
SharePoint 2013 workflow turned off for new tenants	November 1, 2020
SharePoint 2013 workflow turned off for ALL tenants	TBD

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.

https://www.toddklindt.com/SP2010Workflows

4 Comment(s)

Comments

Test

Just testing to see if this blog still uses a SP2010 workflow for comment notifications. ;-)

Thanks for the heads up Todd!

on 7/7/2020 10:11 AM

Power Automate on-premise?

I agree the on-premise workflows are not working so well. Could I expect in SP2022 there will be replacement for workflow manager?

on 7/7/2020 8:24 PM

Re: Test

I can block you from this blog, Jeremy! :)

tk

Todd O. Klindt

on 7/9/2020 4:25 PM

Re: Power Automate on-premise?`

I don't think any more work will be put into on-prem workflow. The answer will always be "move to the cloud." That might mean using the on-prem data gateway.

tk

Todd O. Klindt

on 7/9/2020 4:26 PM

How to best stop the bleeding

Hi Todd,
First, thanks for picking up the slack for Microsoft and putting this together. I also watched the two Ask Sympraxis sessions on this topic and have a couple questions about your guidance to disable SharePoint Designer and Infopath: What is the best way to do that and what are the potential impacts to existing functionality built with SPD or InfoPath? I feel a little silly asking this because it seems like it should be obvious but am hoping you can clarify nonetheless....Thanks!

on 8/29/2020 4:50 PM