On April 2, 2026 SharePoint 2013 workflows will be completely retired meaning there will be a full removal from all tenants, including Government and DoD with no extensions granted. As of July 2025, this retirement is now merely 10 months away and legacy workflows will stop running next spring.

Why this matters

SharePoint 2013 workflows will cease functioning in SharePoint Online past April 2, 2026. Microsoft will halt patches, support, and the ability to create or run these workflows. Even custom workflows developed in Visual Studio using SP 2013 APIs depend on Workflow Manager, so they’ll be impacted too.

What to do next

Discover your current usage

Use the Microsoft 365 Assessment Tool and its Power BI Workflow Report to identify all active SharePoint 2013 workflows. It shows usage metrics and migration readiness.

Prevent new dependency

Disable creation of new 2013 workflows via PowerShell:

Connect-SPOService -Url https://<tenant>-admin.sharepoint.com

Set-SPOTenant -StopNew2013Workflows $true

Existing workflows will still run, and reversing this flag is possible, though Microsoft advises transitioning entirely to modern tools.

Plan your migration

Evaluate each workflow for complexity, third-party integration and business impact. Explore your migration paths:

  • Microsoft’s Power Automate connects to 700+ services
  • ISV alternatives

Train and notify stakeholders

  • Inform IT teams, developers, site owners, and help desk about the timeline.
  • Update operational documentation and user-facing materials.
  • Begin transition well ahead of April 2026 to include time for testing and adoption.

On-premises SharePoint users: A separate situation

Workflows deployed on SharePoint Server 2016, 2019, or Subscription Edition remain supported as long as those platforms are supported. If you are running SharePoint Server 2016 or 2019 that means you will have until their end of support which is July 14, 2026 and you should be working on your migration or upgrade.

Why migrate now?

  • Security & compliance — No patches or support for SP2013 workflows post-retirement.
  • Future-proofing — Modern tools like Power Automate offer deeper integration, extensible connectors, better monitoring, and overall longevity.
  • Avoid last-minute rush — Migrations can be complex; starting early reduces risk of disruption next spring.

Get expert help migrating your SharePoint 2013 workflows to Power Automate

SharePoint 2013 workflows have served many organizations well, but with retirement already scheduled, it’s time to modernize. By beginning your migration effort now, you’ll be able to leverage advanced tools, maintain compliance, and ensure continuity.

Need help navigating this transition? As a Microsoft Solutions Partner, we are helping customers migrate to Power Automate, much as we did for the SharePoint 2010 workflow retirement, and are currently doing for InfoPath. Contact us today to schedule a free strategy session.