Microsoft has officially entered the final chapter of SharePoint 2013 workflows, and for many organizations, this update is more than just another lifecycle announcement — it’s a wake-up call. The retirement of SharePoint 2013 workflows in SharePoint Online marks a decisive shift away from legacy automation toward modern, cloud-first workflow platforms.
For businesses that still rely on approval flows, notifications, and automated processes built years ago, the message is clear: those workflows will stop working, and planning can no longer be postponed.
This updated news article explains what the retirement means, what changes technically after the deadline, and — most importantly — how organizations can migrate and modernize their workflows step by step.
The Updated Retirement Timeline
Microsoft has confirmed a two-phase retirement plan for SharePoint 2013 workflows in SharePoint Online.
- April 2, 2024: SharePoint 2013 workflows were disabled for newly created Microsoft 365 tenants. Any new tenant created after this date cannot create or run these workflows.
- April 2, 2026: SharePoint 2013 workflows will be fully retired for all existing tenants. After this date, workflows will no longer run, cannot be edited, and will be unsupported.
This retirement applies across all Microsoft 365 environments, including commercial, government, and specialized cloud tenants.
There will be no extensions and no exceptions.
What Exactly Is Being Retired?
The retirement affects all workflows built using the SharePoint 2013 workflow engine, regardless of how they were created. This includes:
- Workflows created in SharePoint Designer 2013
- Workflows developed using Visual Studio
- Reusable workflows, list workflows, and site workflows
- Workflows triggered automatically or manually
Once retired, these workflows will still technically exist in the system, but only as read-only XML definitions. They will not execute, trigger, or process any logic.
Why Microsoft Is Moving Away from SharePoint 2013 Workflows
From a technical perspective, SharePoint 2013 workflows rely on architecture that no longer aligns with Microsoft’s cloud strategy. They depend on legacy workflow services that were designed before modern APIs, connectors, and event-driven automation became standard.
Microsoft’s current automation strategy centers on Power Automate, which offers:
- Cloud-native execution
- Better performance and scalability
- Built-in monitoring and error handling
- Integration with hundreds of services beyond SharePoint
- Stronger security and compliance controls
Maintaining the old workflow engine alongside modern services increases complexity and technical debt — something Microsoft is actively reducing across Microsoft 365.
What Will Happen If You Do Nothing?
Organizations that do not migrate before April 2026 will face immediate operational risks:
- Approval processes will stop without warning
- Automated notifications will fail silently
- Compliance and audit workflows may break
- Business users will lose visibility into task assignments
- IT teams will be unable to troubleshoot or fix broken workflows
Because these workflows often run in the background, many businesses won’t notice the problem until something critical fails.
Supporting Your Workflow Transition with a Structured Governance System
As organizations prepare for the retirement of legacy SharePoint 2013 workflows, many teams quickly realize that migration is only part of the challenge. The greater risk lies in undocumented logic, unclear ownership, hidden dependencies, and the uncontrolled growth of new workflows across platforms like Power Automate and custom automation solutions.
To help address both immediate retirement planning and long-term governance, a dedicated Workflow Governance & Migration Tracker Notion Template has been developed and is available on Etsy.
This template was specifically designed to support:
- Discovery and inventory of legacy and active workflows
- Structured logic and dependency documentation
- Risk and business criticality assessment
- Migration tracking and retirement confirmation
- Ongoing governance of newly created workflows
Rather than functioning as a one-time migration checklist, the system provides a full workflow lifecycle framework. It enables organizations to move from reactive remediation toward proactive governance — ensuring every workflow has ownership, documentation, and visibility.
Key capabilities include:
- Executive dashboard for leadership visibility
- Centralized workflow inventory database
- Detailed workflow logic analysis pages
- Migration and retirement status tracking
- Continuous intake and governance for new workflows
For IT administrators, project managers, and digital transformation teams, the goal is not simply to retire outdated workflows — it is to establish sustainable control over automation moving forward.
Organizations that treat workflow retirement as a one-off task often find themselves facing similar governance gaps in the future. Implementing a structured lifecycle management approach helps ensure that automation remains aligned with business objectives, compliance requirements, and operational stability.
As workflow ecosystems continue to expand, having a centralized, structured governance model becomes not just helpful — but essential.
Template Link:
Notion Template to help migration
Technical Preparation: Step-by-Step Approach
Below is a practical, technical roadmap organizations can follow to prepare for the retirement
Step 1: Discover and Inventory Existing Workflows
The first technical task is identifying where SharePoint 2013 workflows are being used.
Actions:
- Scan all SharePoint Online site collections.
- Identify:
- List workflows
- Site workflows
- Reusable workflows
- Document:
- Workflow name
- Trigger type (manual, item created, item changed)
- Associated lists or libraries
- Business owner
- Complexity level (simple, moderate, complex)
Tip:
Many environments contain workflows that are no longer used. Flag unused workflows early to avoid unnecessary migration work.
Step 2: Analyze Workflow Logic and Dependencies
Each workflow should be reviewed technically to understand what it does.
Key questions to answer:
- What triggers the workflow?
- Does it use conditions or loops?
- Does it create tasks or approval steps?
- Does it send emails?
- Does it update SharePoint fields?
- Does it integrate with external systems?
Common dependencies to note:
- Custom columns
- Lookup fields
- Managed metadata
- Calculated fields
- Custom task lists
- Custom permissions logic
This analysis determines how complex the migration will be.
Step 3: Decide the Replacement Strategy
Not every workflow needs a one-to-one rebuild.
Typical options:
- Power Automate cloud flows (recommended for most scenarios)
- Power Automate with approvals
- Azure Logic Apps (for advanced or high-volume workflows)
- Custom development using APIs (for complex logic)
Simple approval and notification workflows almost always map cleanly to Power Automate.
Step 4: Rebuild Workflows in Power Automate (Technical Steps)
Here’s a simplified technical example of rebuilding a SharePoint 2013 workflow in Power Automate.
Example Scenario:
“When an item is created, send it for approval and update status.”
Power Automate Steps:
- Create a new Automated Cloud Flow
- Select trigger:
- “When an item is created” (SharePoint)
- Configure:
- Site address
- List name
- Add action:
- “Start and wait for an approval”
- Configure approval:
- Approval type (Approve/Reject)
- Assigned approvers
- Add condition:
- If outcome equals “Approve”
- Update item:
- Set Status = Approved
- Else:
- Set Status = Rejected
- Add notifications if required
This approach replaces many classic workflows with clearer logic and better tracking.
Step 5: Handle Advanced Workflow Scenarios
Some SharePoint 2013 workflows include complex features that require special handling.
Common challenges:
- Nested loops
- Impersonation steps
- Custom task forms
- Long-running workflows
- High-volume list processing
Recommended solutions:
- Break large workflows into smaller modular flows
- Use parallel branches where possible
- Store state in SharePoint or Dataverse
- Use error handling scopes for retries and failures
- Leverage child flows for reusability
Testing is critical for these scenarios.
Step 6: Validate and Test Thoroughly
Before disabling old workflows:
Testing checklist:
- Validate triggers fire correctly
- Confirm data updates as expected
- Test approvals with multiple users
- Simulate failure scenarios
- Review run history and logs
- Confirm permissions behave correctly
Run both old and new workflows in parallel (if possible) to compare results.
Step 7: Decommission Legacy Workflows
Once migration is complete:
- Disable SharePoint 2013 workflows
- Remove SharePoint Designer access if no longer needed
- Update documentation
- Inform business users of the new workflow behavior
This reduces confusion and prevents accidental reliance on unsupported technology.
Organizational Impact and Skills Shift
Beyond the technical work, the retirement changes how teams build automation:
- Less reliance on desktop tools
- More cloud-based design
- Increased collaboration between IT and business users
- Stronger governance and monitoring
Training teams on Power Automate is now essential, not optional.
A Necessary but Manageable Transition
The updated retirement of SharePoint 2013 workflows is a clear signal that legacy automation has reached its end. While the transition requires effort, it also offers an opportunity to modernize processes, improve visibility, and reduce long-term technical debt.
Organizations that act early will avoid last-minute pressure and gain more stable, scalable automation platforms in the process.
April 2026 may seem far away — but in enterprise IT terms, it’s right around the corner.
