Postope Designer 2010 Workflow Engine Retirement
On 6th July 2020, it was suddenly announced that SharePoint 2010 workflow engine is going to stop working by November 2020.
For at least a few of my clients it will represent a catastrophe.
Our suggestion is to push back the retirement date to a more reasonable date. For example, match if with SharePoint Designer 2013 support lifecycle or with InfoPath support lifecycle.
Large organizations depend on clear sunsetting timelines. Announcement that leaves them only four months to react is completely unrealistic. Organizations need to plan resources, budget, hire SharePoint SME’s and involve business owners that rely on these workflows and much more.
Reasons for postponement:
- The clients were not properly warned about the Workflows retirement.
- There are SPO tenants with thousands SharePoint 2010 Workflows running with no direct path of quick replacement.
- Not all Workflow 2010 can be replaced with Workflow 2013 engine or Power Automate because of features differences.
- Many Clients do not have enough time and resources to replace the existing workflows.
- Pandemic is still not over and this announcement feels very out of place.
Denis Molodtsov
shared this idea
AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, Microsoft SharePoint)
responded
We’ve been working one on one with customers deeply impacted by this change and encourage people to reach out to support if they have special circumstances. However, we wanted to provide clarity that our policy will not be changing and our previously communicated timelines will continue. In that regard, we will be retiring 2010 Workflows on November 1st, 2020 in SharePoint Online. After November 1st, 2020, while existing 2010 workflows will stop to run, users can still open and view their workflows in SharePoint Designer. Please visit the following link to get the latest updates about the 2010 Workflows retirement: https://aka.ms/sp-workflows-support.
181 comments
Comments are closed-
Mark
commented
Much more time needed. 4 months is way too little time to do this. Very unprofessional of them to do this
-
Clarelle Charles
commented
Will definitely need more than 4 months!
-
Clarelle Charles
commented
We will definitely need more than 4 months! Don't set us up for failure.
-
Reina Rosen
commented
This is not enough time. My group uses 2010 workflows in direct support to product sales. We need to be able to appropriately plan for this.
-
Devin
commented
Yes. four months is not acceptable, especially when expecting a 2026 sunset.
-
Anonymous
commented
Denis - Don't worry about the spelling. This is great that you kicked this off, I've also reached out to our TAM to pass the message up the chain at Microsoft.
-
Anonymous
commented
if you are doing this, at least make a way to convert them to 2013
-
Jordan B
commented
This is not enough time, I have always been told by MS support that there was no immediate plan to remove 2010 workflows. 4 months is not enough time to remake all these workflows
-
Anouk Bastien
commented
Impossible for large organisation to move away from SharePoint 2010 Workflows with such short notice. We are heavy users of SharePoint 2010 Workflows in the Production and it will negatively impact our enterprise business.
-
Dominique Tremblay
commented
Too tight as a deadline for large companies! This will delay our migration process from SP2013 on premise to M365 :(
-
Very angry paying customer
commented
So in the middle of a pandemic where IT admins are already stretched thin with various other tasks, you decide that it is a good time to give everyone 4 months to completely re-architect and setup workflows across their entire tenant… Some of those workflows took months to plan, create, and test alone… On top of that, your solution going forward doesn’t even cover all the needs that were possible in 2010 workflows!?
This decision is going to cause severe disruptions in business processes which are critical during the pandemic for companies that are doing critical work for the nation. What happened to the support until 2026? What happened to common sense and respect for your customers?
-
Robin George
commented
It's not a possible for us (enterprises org) to move away from SharePoint 2010 Workflows with such short notice as we are heavily using SharePoint 2010 Workflows in the Production and it will drastically impact our enterprise business. Request you to postpone this plan at least another 6 months. Meanwhile, we'll develop the alternate solution for all our business units. Remember, it’s a COVID-19 situation and summer time.
-
JeanneE
commented
Microsoft needs to allow much more time for this change. We have over 2,000 workflows in our environment, to notify our developers of the workflows and ask them to drop everything to make this change in the time frame they gave us is unacceptable.
-
Khha
commented
Please give us more time
-
Veronique Palmer
commented
Microsoft destabilizing companies again. The world is already in chaos because of Covid and companies are struggling to survive - so this is Microsoft's answer to helping people........ #Fail
-
Ondřej Veselý
commented
You can agree or disagree with this move... But I think we can all agree on the fact that this timeline is completely detached from the reality. Companies need clear timelines for years ahead, not 4 months ahead....
-
Rajesh
commented
With timeline as short as this, its going to be chaos in large organizations
-
Ashutosh Agarwal
commented
Microsoft is forcing us to use power automate and we are ready to do so but Microsoft should give us proper time and also give more understanding towards the pricing model as it is very confusing and difficult to understand
-
Rod
commented
SP Designer as an app that includes 2010 and 2013 workflows were supposed to be supported for a few more years. Instead we only have 4 months. This pretty much shows a disconnect with your partners and the software we use for mission critical needs. Many of our workflows are complex and some solutions have multiple workflows. And we have multiple solutions. it's not like nobody is using them. The timeline is totally unrealistic and will create a hardship for many many.
-
Denis Molodtsov
commented
Suggestion to myself: check the spelling of the suggestion title...
