Skip to content

Add notes about SharePoint Workflows deprecation schedules #10978

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
andrewconnell merged 3 commits into from
Aug 5, 2026
Merged

Add notes about SharePoint Workflows deprecation schedules #10978

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bcf5463
Add notes about SharePoint Workflows deprecation schedules
danthemango Aug 4, 2026
bfb1560
docs: update wording and tense for SharePoint workflows retirement
andrewconnell Aug 5, 2026
1d150e4
docs: update wording and tense for SharePoint workflows retirement
andrewconnell Aug 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/general-development/develop-sharepoint-workflows-using-visual-studio.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,10 @@ ms.localizationpriority: high
SharePoint supports two primary workflow development environments for authoring workflows: SharePoint Designer and Visual Studio. This article summarizes both and discusses the advantages and disadvantages of each.

> [!NOTE]
> SharePoint 2010 workflows have been retired since August 1, 2020 for new tenants and removed from existing tenants on November 1, 2020. If you’re using SharePoint 2010 workflows, we recommend migrating to Power Automate or other supported solutions. For more info, see [SharePoint 2010 workflow retirement](https://support.microsoft.com/office/sharepoint-2010-workflow-retirement-1ca3fff8-9985-410a-85aa-8120f626965f).
> SharePoint 2010 workflows were retired on August 1, 2020 for new tenants on SharePoint Online and were removed from existing tenants on November 1, 2020. If you’re using SharePoint 2010 workflows, we recommend migrating to Power Automate or other supported solutions. For more information, see [SharePoint 2010 workflow retirement](https://support.microsoft.com/office/sharepoint-2010-workflow-retirement-1ca3fff8-9985-410a-85aa-8120f626965f).

> [!NOTE]
> SharePoint 2013 workflows were retired on April 2, 2026. For more information, see: [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e).

## Authoring basics for SharePoint workflows

Expand Down Expand Up @@ -39,7 +42,6 @@ Both of these workflow authoring environments—SharePoint Designer and Visual S
- **Target users:** Information workers, business analysts, SharePoint developers.
- **Difficulty level:** Familiarity with SharePoint Designer, including the core workflow components, such as stages, gates, actions, conditions, and loops.


With SharePoint Designer, users can create a workflow that is attached to a list, library, or site using a no-code, text-based designer. Or, they can use the new visual design environment in which graphical elements are arranged on a design surface to represent the logical flow of a business process. SharePoint Designer excels at enabling rapid workflow development by non-technical workers.

### Using Visual Studio
Expand Down