Skip to content
Lacambra Web Portal Services
← 2026, week by week
Software · Week 29, 13 to 19 July 2026

SharePoint 2016, 2019 and InfoPath reach end of support

SharePoint Server 2016 and 2019, SQL Server 2016 and InfoPath 2013 lost support on 14 July 2026. What it means for the approval forms built on them.

An old beige tower server on a wooden pallet in an empty storeroom, wrapped in a grey moving blanket and strapped for removal, its power cable coiled on top.

On 14 July 2026, SharePoint Server 2016 and 2019, SQL Server 2016 and InfoPath 2013 reached the end of Microsoft support, along with SharePoint Designer 2013 and Project Server 2016 and 2019. The same day, its monthly security release fixed a SharePoint Server flaw that attackers were already exploiting, with updates for SharePoint 2016 and 2019 among the rest. One more followed on 11 August, for flaws found before support ended, and Microsoft's update guide lists none for those versions since. SQL Server 2016 now gets security fixes only through paid Extended Security Updates, sold until July 2029. Any office whose approvals still run on InfoPath forms is now running forms Microsoft no longer supports, whichever version of SharePoint sits under them.

What ended, and what was patched that day

The same lifecycle list takes in Dynamics GP 2016 and the second year of extended security updates for SQL Server 2014. The monthly release was enormous: Dustin Childs of the Zero Day Initiative counted 621 Microsoft vulnerabilities, besides about 480 in Chromium and Edge, and called the month record-breaking. Two were listed as under attack that day. One, CVE-2026-56164, is a SharePoint Server flaw an attacker can reach over the network without signing in, which, Childs notes, matters more than its moderate score of 5.3 suggests. The release also fixed a critical SharePoint flaw, CVE-2026-50522, scored 9.8, and disclosed a second, CVE-2026-58644, also 9.8, whose fix had shipped quietly in June. A day later Microsoft marked that one as exploited too.

InfoPath had been given notice. In 2023 Microsoft said it would remove InfoPath Forms Services from SharePoint Online after 14 July 2026, with no option to extend, and that support for the same service in SharePoint Server 2016, 2019 and Subscription Edition would end then too. It described what customers used InfoPath for: "collecting information, connecting data from diverse sources, and automating workflow." In an office, that often means a request form, a route through the people who approve it, and a library of every request ever made.

Why the forms are the hard part

Moving to a newer SharePoint does not solve InfoPath, because the forms service is unsupported on every version. Microsoft points customers to Power Apps, Power Automate, Microsoft Forms or custom code, which means each form is rebuilt somewhere. And the forms are only half of it. Each submitted form is a record of who asked for what, who approved it, and when. A move that rebuilds the forms but leaves that history behind loses the very record an auditor will ask for.

Approval workflows and getting off a dead system are two of the things I focus on, and they meet here. An approval system I build keeps a record of who held each request and for how long, and moving one means accounting for every record in writing, including the ones that do not move and why. That second list is the argument of Report what did not move. Unfinished drafts need the same care: they are somebody's half-done work and the easiest thing to drop. An InfoPath library deserves the same accounting, form by form.

Five steps for an office still on InfoPath

  • List what runs on the unsupported versions: every SharePoint site with InfoPath forms, every workflow built in SharePoint Designer, and the SQL Server 2016 databases underneath. On SharePoint Online, Microsoft's assessment tool can find InfoPath forms for you.
  • Make sure the August 2026 updates are installed: KB5002905 and KB5002906 for SharePoint 2016, KB5002894 and KB5002896 for 2019. Microsoft has listed none since.
  • Take these servers off the open internet, or put them behind a VPN, until they are replaced.
  • For each form, write down who fills it in, who approves it, and what happens when an approver is away. That is the specification for whatever replaces it, and the decisions in it are yours to make.
  • Decide what happens to the history before anything moves: which records go to the new system, which are kept read-only, and the reason for each, in writing.

Getting off a system like this is what Move it is for. It starts with a two-week trial run: a rehearsal on a copy, with your live data never touched. The fit check is the first step.

Sources

  1. Microsoft Learn, Ending Support in 2026
  2. Microsoft Tech Community, Support update for InfoPath Forms Services in Microsoft 365, 30 June 2023
  3. Zero Day Initiative, The July 2026 Security Update Review, 14 July 2026
  4. Microsoft Security Response Center, CVE-2026-56164: Microsoft SharePoint Server Elevation of Privilege Vulnerability, 14 July 2026
  5. Microsoft Support, Description of the security update for SharePoint Server 2016: August 11, 2026 (KB5002905), 11 August 2026
  6. Microsoft Learn, SQL Server 2016: Microsoft Lifecycle

Enrique Lacambra III builds internal business systems from Cainta, Rizal.

Email me← All writing

Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.