SharePoint 2010 workflows are being retired in Microsoft 365

Microsoft have announced that SharePoint 2010 workflows will be retired in Microsoft 365 (Office365).

Based on the feedback I have received and seen today in various blogs there are a large number of organisations that are still using SharePoint 2010 workflows and this change will have a significant impact at time when IT departments are already stretched.

The key dates for SharePoint 2010 workflow retirement are

Starting 1st August, 2020 SharePoint 2010 workflows will be turned off for newly created tenants.

Starting November 1st, 2020 Microsoft will begin to remove the ability to run or create SharePoint 2010 in existing tenants.

Starting November 2020 SharePoint 2013 workflows will be switched off by default for new tenants. SharePoint 2013 workflows will continue to be supported although deprecated.


The change means that business processes that have been implemented or migrated to Microsoft 365 that have been built by end-users and IT departments that use SharePoint 2010 workflows will stop working until they are either upgraded or replaced.

To understand the impact on your tenancy you can run the SharePoint Modernisation Scanner, more details can be found here.

This will provide you with a workflow report that will provide you with an overview of

  • Distribution of legacy workflows across SharePoint 2010 and SharePoint 2013 workflows
  • Distribution of out of the box and custom legacy workflow usage
  • Which sites and lists use legacy workflows
  • Power Automate upgradability score indicating how well the detected actions are upgradable to flows with Power Automate

I’m already seeing customers identifying issues they hadn’t realised they were exposed to.

The main issues that are being highlighted are

  • Legacy 3rd party tools using SharePoint 2010 Workflows
  • Undocumented workflows created by long departed developers
  • Poorly documented processes that will need to be recreated in PowerApps and PowerAutomate
  • Developers creating custom workflows using SharePoint Designer or Visual Studio that need to be migrated
  • Workflows are responsible for permission management in a number of SharePoint solutions
  • End-users that have created workflows around lists and document libraries
  • SharePoint 2010 workflows that have been integrated with line of business systems

Next steps

With a change such as this the first step is to work out how much of an impact there is on your services. Running the Modernisation Scanner is a key first step.

Engagement and communications with end users is very important. Informing the users now that their business processes built in Office365 may need to be migrated will allow them to plan what to do next.

Once you have identified any workflows that will be impacted you can work with the users to plan for migration.

More information

For more information about the impact of this change and how it may affect your organisation please do not hesitate to contact me.

Telephone: + 44 (0)7515 969630

Leave a Reply