Here is a quick summary of the major SharePoint and Project Server components that reach end of support today, July 15, 2026, along with the recommended upgrade or replacement path:
| Product, Feature or Component | Upgrade Path/Alternative |
|---|---|
| SharePoint Server 2016 | SharePoint Server Subscription Edition |
| SharePoint Server 2019 | SharePoint Server Subscription Edition |
| Project Server 2016 | Project Server Subscription Edition |
| Project Server 2019 | Project Server Subscription Edition |
| SharePoint 2010 workflows (including 3rd party workflows building on top of these like Nintex and similar) | upgrade to SharePoint 2013 workflows, PowerApps or 3rd party products |
| Basic Authentication | replace with a supported authentication method |
| SharePoint Designer 2013 | use Visual Studio 2022 to create Workflows |
| Classic Microsoft Workflow Manager | SharePoint Workflow Manager |
| Infopath Forms Services | replace with PowerApps or 3rd party solutions |
Permalink
Hi, thanks for the info.
When SharePoint 2010 workflows will be completely removed from Sharepoint SE?
Thx
Permalink
Hi Matej,
it will be unsupported starting today – not necessarily removed.
But latest when the next security vulnerability is identified in this functionality there is a good chance that it will be removed without further notice.
Cheers,
Stefan
Permalink
So no indication prior at all?
Permalink
Copilot said: Potentially not.
However, because SharePoint updates cannot be uninstalled, every cumulative update should be thoroughly validated in a test environment against all business-critical functionality before being deployed to production to ensure that unexpected side effects in fixes cannot impact your business operations.
This validation would allow you to notice it if the feature has been removed.
Cheers,
Stefan
Permalink
Thanks Stefan!
What articles explain how to setup/use Visual Studio for workflows? If you have a test farm with more than one server, which one should VS be installed on?
Permalink
Hi Marlene,
I would use this as a starting point:
https://learn.microsoft.com/en-us/sharepoint/dev/general-development/develop-sharepoint-workflows-using-visual-studio
Cheers,
Stefan
Permalink
RIP SharePoint 2016 & 2019 🕯️🕯️
Permalink
Hello Stefan, thanks for the reminder.
I also found a mention that “Beginning with Visual Studio 2026, SharePoint Workflow development in Visual Studio is deprecated and will be removed in a future release.”
is mentioned in https://learn.microsoft.com/en-us/sharepoint/dev/general-development/how-to-create-sharepoint-workflows-using-visual-studio
Can you tell me if the “future release” means Visual Studio 2030, or a future patch of 2026?
Permalink
Hi Daniel,
I doubt it will be a future patch of 2026 as VS 2026 goes out of support next year:
https://learn.microsoft.com/en-us/lifecycle/products/visual-studio-2026
The recommended Visual Studio version for SharePoint Workflow Development is Visual Studio 2022 which will be supported till 2032:
https://learn.microsoft.com/en-us/lifecycle/products/visual-studio-2022
Cheers,
Stefan
Permalink
Hello,
I have completed a migration to SharePoint Subscription Edition.
AD LDS is used as the account repository. I exported the data from the old environment and imported it into the new AD LDS instance; the accounts were imported successfully and appear to be correct.
However, users are currently unable to sign in through the Internet-facing web application that uses Forms-Based Authentication (FBA).
In the SharePoint logs, I can see the following error: :”SetupUserValidationType: Cookie validation failed. Defaulting to sign-in operation. Username: ‘sa-admin’.
Token Handler: Claims Forms Sign-In: Membership Provider ‘ADProvider’ username-password check for user ‘sa_admin’ failed.
Throwing token issuance failure exception. ErrorCode: FailedToValidateUserNamePassword
STS Call: Failed to issue new security token with sign-in exception. Exception: ‘System.ServiceModel.FaultException: ID3035: The request was not valid or is malformed. ”
I have already configured Central Administration, the Security Token Service, and the web application correctly. Do you have any suggestions?
Permalink
Bonjour,
Voici les actions qui ont permis de résoudre le problème dans mon environnement :
1. Vérifier la configuration du fournisseur LDAP
Contrôler que la configuration du fichier web.config des Web Applications ainsi que celle du web.config du STS ressemble à ceci :
Dans mon cas, j’ai dû créer un compte de service dans AD LDS avec des droits de lecture sur l’annuaire, puis l’utiliser dans les paramètres connectionUsername et connectionPassword.
J’ai également dû utiliser le port 636 avec LDAPS (SSL/TLS) pour que l’authentification fonctionne correctement.
2. Configurer le certificat SSL
J’ai généré un certificat pour l’instance AD LDS et l’ai déployé dans le magasin Personal de l’instance.
Je crois également qu’il doit être ajouté au magasin de certificats de l’ordinateur afin que la connexion LDAPS fonctionne correctement.
3. Vérifier les autorisations sur le certificat
Les droits de lecture sur la clé privée du certificat ont également été accordés au compte Service Réseau (Network Service) utilisé par l’instance AD LDS.
Ces différentes actions ont permis de faire fonctionner l’authentification LDAP sur mon environnement. J’espère que cela pourra vous aider.
Permalink
Translating to english as curtesy for our global community:
Hello,
The following actions helped resolve the issue in my environment:
Check that the configuration in the web.config files of the Web Applications and the STS web.config is similar to the following:
(configuration example here)
In my case, I had to create a service account in AD LDS with read permissions on the directory, and then use this account in the connectionUsername and connectionPassword settings.
I also had to use port 636 with LDAPS (SSL/TLS) to ensure that authentication worked properly.
Configure the SSL Certificate
I generated a certificate for the AD LDS instance and deployed it to the instance’s Personal certificate store.
I also believe that the certificate must be added to the local computer certificate store to allow the LDAPS connection to function correctly.
Verify Certificate Permissions
Read permissions on the certificate’s private key were also granted to the Network Service account used by the AD LDS instance.
These actions allowed LDAP authentication to function successfully in my environment.
I hope this information helps you resolve the issue in your environment.
Permalink
Hi Stefan,
Many customers still have existing SharePoint Designer 2013 workflows that require ongoing maintenance. Can Visual Studio actually open and modify existing SharePoint Designer workflows, or is it only intended for creating new Visual Studio-based workflows?
As far as I understand, Visual Studio workflows require solution packaging and deployment, resulting in a completely different and more complex development and deployment model than SharePoint Designer workflows. Is that really Microsoft’s recommended approach for maintaining existing SPD workflows?
Permalink
Hi Max,
no, this is not possible. You need to create new workflows in Visual Studio.
And yes – you are correct about the different way how to deploy them.
Cheers,
Stefan
Permalink
So how are customers expected to maintain existing SharePoint 2013 workflows going forward?
Following Microsoft’s recommendation, we migrated all our SharePoint 2010 workflows to SharePoint 2013 workflows – using SharePoint Designer… Now SharePoint Designer is no longer available for download from Microsoft, and the recommended approach seems to be creating workflow solutions using a legacy development model that Microsoft has been moving away from for years?
For organizations that must remain on SharePoint Server and cannot use Microsoft Power Platform, what is the recommended long-term strategy for workflows? Microsoft’s guidance feels very, very unclear on this matter.
Permalink
Hi Max,
there are different options:
1) use SP2013 workflows with Visual Studio package
2) continue to use SPD even that it is unsupported and might stop working in the future
3) If Internet Connection is possible migrate to Microsoft Flow
Alternatively there is the option to migrate to a 3rd party product
Cheers,
Stefan
Permalink
Why can’t Microsoft give us a hard date when 2010 workflows will break in SharePoint Subscription Edition? If we can’t connect to Power Automate (via On-prem Data Gateway), for example on farms that can’t get to the Internet, what is the solution for ongoing workflows?
Permalink
Hi Vin,
in this case your options are
– SP2013 workflows
– 3rd party workflow solutions
Cheers,
Stefan
Permalink
Hello,
why are there still cumulative updates to sharepoint 2019 when it is unsupported as of july? for how long will there be updates and will critical issues still be fixed?
thank you very much.
gerald
Permalink
Hi Gerald,
The reason is the large number of security fixes that needed to be shipped for issues identified before the product reached end of support.
Based on the information I have received, the August CU is expected to be the final cumulative update.
Cheers,
Stefan