Retiring SharePoint 2010 Workflows

%3CLINGO-SUB%20id%3D%22lingo-sub-1511672%22%20slang%3D%22en-US%22%3ERetiring%20SharePoint%202010%20Workflows%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1511672%22%20slang%3D%22en-US%22%3E%3CP%3EI%20received%20the%20notification%20that%20MS%20is%20retiring%20workflows%20and%20pushing%20towards%20Power%20Automate.%26nbsp%3B%20Does%20anyone%20know%20if%20this%20change%20affects%20the%20content%20organizer%20rules%3F%26nbsp%3B%20We%20use%20them%20for%20document%20processing%20from%20a%20drop-off-library%20to%20the%20permanent%20library.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1511672%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1512019%22%20slang%3D%22en-US%22%3ERe%3A%20Retiring%20SharePoint%202010%20Workflows%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1512019%22%20slang%3D%22en-US%22%3EIt's%20affecting%20any%20declarative%20workflow%20based%20on%20the%20legacy%20SharePoint%202010%20WF%20engine...so%20it%20should%20not%20affect%20Content%20organizer%20that%20is%20not%20based%20on%20WF%20(If%20my%20mind%20serves%20me%20well)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1523218%22%20slang%3D%22en-US%22%3ERe%3A%20Retiring%20SharePoint%202010%20Workflows%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1523218%22%20slang%3D%22en-US%22%3EThank%20you%20for%20confirming%20this%20does%20not%20affect%20content%20organizer%20rules.%3C%2FLINGO-BODY%3E
New Contributor

I received the notification that MS is retiring workflows and pushing towards Power Automate.  Does anyone know if this change affects the content organizer rules?  We use them for document processing from a drop-off-library to the permanent library.

2 Replies
It's affecting any declarative workflow based on the legacy SharePoint 2010 WF engine...so it should not affect Content organizer that is not based on WF (If my mind serves me well)
Thank you for confirming this does not affect content organizer rules.