Microsoft will remove SharePoint 2010 workflows and InfoPath Forms Services from SharePoint Server Subscription Edition in the update scheduled for July 13, 2027. Once you install this update or any later one, workflows and forms that depend on these features will stop working. If you still use them, decide how to handle requests that are still awaiting approval and how users will access previously submitted forms before you install the update. Microsoft Support – KB5002945
What changes with the July update?
Support for both features ended on July 14, 2026. The September update turned them off by default. During this transition, you can still enable SharePoint 2010 workflows for a specific site collection with Enable-SPLegacyWorkflow. For InfoPath Forms Services, Microsoft documents how to set the DisableInfoPathRetirement (5023) farm flag and enable browser form rendering and activation. Microsoft Support – September KB5002908 · Microsoft Support – November KB5002945
The July update will remove both features from the farm, ending the option to re-enable them. All later cumulative updates will include the same change. Microsoft Support – KB5002945
Where should you look for dependencies in your farm?
Use Get-SPLegacyWorkflowEnabledSites to see which site collections have the SharePoint 2010 workflow platform enabled. In those collections, review the lists and libraries where people approve documents or process requests. Check site workflows and any custom solutions that start them as well. For each important process, identify the workflow it uses, what starts it and who is responsible for seeing it through. Microsoft Support – KB5002908
If you use SharePoint 2013 workflows, check for the Start a List Workflow and Start a Site Workflow actions. The 2013 platform runs on SharePoint Workflow Manager and will still be available. If either action starts a SharePoint 2010 workflow, that step can fail after the update. Microsoft Learn – workflow actions reference
For InfoPath, check customized list forms, form libraries and workflow task forms. Can a user submit a new request? Can they open last year’s request? For form libraries in particular, check how you’ll make the data in saved .xml files and any attachments available after the update. A new form can handle incoming requests. Older records may need their own way to be viewed. Microsoft Support – InfoPath form templates and saved forms
What can replace the workflows and forms?
If your automation needs to stay on-premises, SharePoint 2013 workflows on SharePoint Workflow Manager are one option. Review the original workflow logic and check how you’ll replace the actions it uses. Support for SharePoint Designer 2013 has ended. You can use Visual Studio to create and edit SharePoint 2013 workflows. How to deploy and update SharePoint Workflow Manager
If cloud services are an option, Microsoft recommends evaluating Power Automate for workflows and Power Apps for forms. For an on-premises farm, check whether the connector supports your SharePoint version, the actions and triggers you need, and connectivity through the on-premises data gateway. Check the licensing requirements separately. The connector documentation explicitly lists SharePoint 2016 and 2019 for on-premises farms. For Subscription Edition, confirm support for your specific scenario, especially if the new form needs to run directly inside a list. Microsoft Learn – recommended alternatives · Microsoft Learn – SharePoint connector
What should you test before deploying the update?
In a test farm, run through the whole process using regular user accounts. Submit a request, send it for approval, return it for more information, and open an older approved record with an attachment. For requests that will still be open at cutover, decide which you’ll finish in the existing workflow and which the new solution will take over.
Plan to finish the migration before deploying the July update or a later one. Delaying the update also delays security fixes for the rest of the farm. Microsoft Learn – SharePoint Server Subscription Edition servicing policy


