⚠BEFORE YOU READ FURTHER — TWO DATES THAT MATTER
May 18, 2026: Microsoft blocks all new and updated InfoPath form publishing tenant-wide. You cannot patch, update, or create a single InfoPath form after this date — even as a fallback.
July 14, 2026: Full retirement of InfoPath Forms Services in SharePoint Online. Every InfoPath form stops opening, submitting, and rendering. No extension. No exceptions. No automated migration tool provided.
Most IT Teams Are Planning for the Wrong Deadline
Ask an IT manager about the Microsoft InfoPath EOL and they will almost certainly tell you the date: July 14, 2026. That is the date Microsoft has communicated publicly and repeatedly — the hard retirement of InfoPath Forms Services in SharePoint Online.
What most IT teams do not know is that a second, earlier deadline lands eight weeks before that: May 18, 2026. On that date, Microsoft blocks all InfoPath form publishing tenant-wide. You cannot create a new form. You cannot update an existing one. You cannot patch a legacy form as a temporary fallback while you finish your migration. The safety net disappears on May 18 — not July 14.
If your organization still has active InfoPath forms in SharePoint Online — whether they are HR intake forms, IT service requests, compliance approvals, procurement workflows, or any other business-critical process — this post covers the official facts, what actually breaks, which environments are affected, and who is most at risk.
This is Part 1 of a 3-part series on the Microsoft InfoPath EOL. Part 2 covers the technical migration challenges and compliance risks. Part 3 walks through the step-by-step migration framework and your action checklist.
Not sure how many InfoPath forms are active in your environment? WME offers a free InfoPath Assessment — inventory your forms, classify risk, and get a migration roadmap.
What Is Microsoft InfoPath — and Why Does It Matter Now?
Microsoft InfoPath was a form-design and data-capture application first introduced as part of Microsoft Office 2003. For nearly two decades, it was the go-to tool for organizations building complex digital forms tightly integrated with SharePoint. Its WYSIWYG designer, XML-based data storage (.xsn file extension), and native SharePoint connectivity made it uniquely powerful for its era.
InfoPath forms became embedded in some of the most business-critical workflows across every industry: HR onboarding and benefits enrollment, IT service desk requests, expense and procurement approvals, compliance and audit documentation, project intake and routing, clinical documentation in healthcare, and regulated data collection in finance and government.
Microsoft effectively deprecated InfoPath in 2014, announcing no new versions would follow InfoPath 2013. Yet in 2026, thousands of organizations still run active InfoPath-based forms and legacy workflows. These forms became so deeply embedded in critical business processes that replacing them required Power Fx, Dataverse modeling, and Power Automate skills that most internal IT teams did not have in-house — so organizations delayed, carried the technical debt, and now face a hard binary cutoff with a shrinking window.
The result: the InfoPath EOL is not a future problem. It is an active operational and compliance risk right now.
The Official InfoPath EOL Timeline — Verified from Microsoft Sources
The following facts are sourced directly from Microsoft’s official communications, including Microsoft 365 Message Center MC616550 (originally June 2023, updated through April 20, 2026) and the Microsoft Tech Community SharePoint Blog. Use these as your definitive reference for stakeholder communications and migration planning.
Date / Event | What It Means for Your Organization |
July 13, 2021 | InfoPath 2013 mainstream support ended under the Microsoft Fixed Lifecycle Policy. |
May 18, 2026 ⚠FIRST DEADLINE | Microsoft blocks all InfoPath form publishing tenant-wide. No new forms. No updates to existing forms. No patches — even temporary fallback fixes are impossible after this date. This is eight weeks before the retirement date most articles reference. |
July 14, 2026 — FULL RETIREMENT | InfoPath Forms Services is fully retired in SharePoint Online. All forms stop opening, submitting, and rendering. InfoPath admin configuration entries are removed from the SharePoint Admin Center. This is a binary cutoff — not a gradual degradation. |
July 14, 2026 | InfoPath Client 2013 extended support ends per the Microsoft Lifecycle Policy (learn.microsoft.com/en-us/lifecycle/products/infopath-2013). |
July 14, 2026 | InfoPath Forms Services in SharePoint Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition loses vendor support on the same date — meaning no security patches and no fixes. |
October 1, 2026 | SharePoint Migration Assessment Tool (SMAT) itself reaches end of support. Organizations should complete their InfoPath inventory before this date. |
Source: Microsoft 365 Message Center MC616550; Microsoft Tech Community SharePoint Blog (techcommunity.microsoft.com/blog/spblog/support-update-for-infopath-forms-services-in-microsoft-365/3858190); Microsoft Learn Lifecycle Policy.
MICROSOFT’S EXACT WORDS — NO ROOM FOR INTERPRETATION
“Industry trends and feedback from our customers and partners make it clear that today’s businesses demand an intelligent, integrated forms experience that spans devices which InfoPath does not provide. Please plan appropriately as there will not be an option to extend InfoPath Form Services beyond the InfoPath retirement date of July 14, 2026.”
Source: Microsoft 365 Message Center MC616550 / Microsoft Tech Community SharePoint Blog
Which Environments Are Affected — And What No Longer Works
All Environments. No Exceptions.
One of the most important facts for IT teams managing government or regulated-industry environments: the retirement applies equally to all Microsoft 365 tenant types. There is no waiver, no extension path, and no special accommodation for any environment type.
Environment | Affected? |
Microsoft 365 Commercial tenants | Yes — full retirement July 14, 2026 |
Government Community Cloud (GCC) | Yes — full retirement July 14, 2026 |
GCC High | Yes — full retirement July 14, 2026 |
Department of Defense (DoD) | Yes — full retirement July 14, 2026 |
SharePoint Server 2016 (on-premises) | Yes — InfoPath Forms Services vendor support ends July 14, 2026 |
SharePoint Server 2019 (on-premises) | Yes — InfoPath Forms Services vendor support ends July 14, 2026 |
SharePoint Server Subscription Edition (on-premises) | Yes — InfoPath Forms Services vendor support ends July 14, 2026 |
What Technically Breaks on July 14, 2026
This is not a soft deprecation where things continue working in a degraded state. On July 15, 2026, the following will no longer function in your environment:
- InfoPath forms will not open, submit, or render in any SharePoint Online list, library, or content type.
- The InfoPath Designer and Publisher experience will be disallowed entirely — no creation, modification, or publishing by any user, admin, or maker.
- InfoPath admin-center configuration entries will be removed from the SharePoint Admin Center.
- Legacy approval workflows routed through InfoPath forms will break, disrupting any business continuity process that depends on them.
- Historical XML form data (.xsn and .xml files) remains in document libraries but is only viewable by downloading locally with InfoPath Client 2013 installed — a fragile, unsupported, and non-scalable fallback.
WHAT ABOUT SHAREPOINT SERVER ON-PREMISES?
Organizations running SharePoint Server 2016 or SharePoint Server 2019 on-premises face a compounded problem: both the InfoPath Forms Services support AND the SharePoint Server platform itself reach end of extended support on July 14, 2026.
After that date, any InfoPath-related issue on these platforms will receive no security patches and no fixes from Microsoft. Organizations in regulated industries (HIPAA, SOX, ISO 27001) cannot run unsupported infrastructure without creating documented compliance gaps.
SharePoint modernization — migrating from SharePoint Server to SharePoint Online — and InfoPath migration should be planned together, not sequentially.
Who Is Most at Risk — Industries and Use Cases
Microsoft has not disclosed precise tenant-level adoption figures, but the signal is clear: Microsoft built a dedicated InfoPath assessment module into the Microsoft 365 Assessment Tool (the open-source PnP project), indicating a non-trivial installed base requiring active remediation guidance. Microsoft Gold Partners including Compass365, Crow Canyon Software, Skybow, and Quisitive consistently describe thousands of organizations still running active InfoPath-based forms — many with dozens or even hundreds of forms in production.
Highest-Risk Industries
Industry | Why InfoPath Runs Deep Here | Risk Level |
Healthcare | EHR-integrated clinical forms, HIPAA-governed patient workflows, compliance documentation tied to ePHI data — breaking these forms creates immediate regulatory exposure. | Critical |
Finance & Banking | SOX 404 approval chains, expense and procurement approvals, audit trails and compliance forms tied to financially material processes. | Critical |
Government & Public Sector | State and local agency forms, regulatory submissions, inter-department approvals — particularly persistent in GCC and DoD environments despite the retirement applying equally. | High |
Legal | Matter intake, client onboarding, multi-step review and approval workflows built on SharePoint Designer and InfoPath combinations. | High |
Manufacturing & QA | Floor audit forms, inspection checklists, non-conformance reporting — often tied to ERP systems via InfoPath data connections. | High |
Pharma & Life Sciences | Regulated documentation, clinical trial data collection, compliance forms subject to FDA and ISO 27001 lifecycle controls. | Critical |
The Most Common Business-Critical InfoPath Use Cases
These are the workflows most likely to create operational disruption on July 15, 2026 if migration is not completed in time:
- HR forms — PTO requests, onboarding, benefits enrollment, performance reviews
- IT service desk requests — hardware requests, access provisioning, change management forms
- Expense and procurement approvals — multi-step routing through legacy SharePoint Designer workflows
- Compliance and audit documentation — ISO, SOX, HIPAA-controlled data capture tied to SharePoint document libraries
- Project intake and request routing — connected to CRM, ERP, or line-of-business systems via data connections
- Document routing and approval workflows — historically built on SharePoint Designer and InfoPath combinations
Clinical and regulated data collection — EHR integration, patient intake, clinical trial documentation
Why the May 18 Date Is the Real Operational Deadline
Here is the practical reality that most migration timelines miss: if your organization is still testing or partially migrating forms as May 18 approaches, you lose the ability to make any changes to your remaining InfoPath forms from that date forward. You cannot patch a broken rule. You cannot update a data connection. You cannot publish a corrected version of a form that was working yesterday.
This means that any InfoPath form still in production on May 18 is effectively frozen in its current state — and must survive untouched through the completion of your migration, or be accepted as broken until it is rebuilt.
For organizations with large InfoPath portfolios — 50, 100, or 200+ forms — the May 18 publishing block means that any form not already migrated by that date becomes a static liability. The only question is how many forms you can successfully migrate before May 18 makes the remaining ones immovable targets.
THE REALISTIC PLANNING MATH
If your organization has 50 active InfoPath forms and starts a migration project today, you have a matter of weeks to complete migration before the May 18 publishing block and the July 14 retirement.
Real-world data from Microsoft Partners shows that migrating 50+ forms with 100+ workflows takes 8 to 16 weeks of active project work — and that assumes a proper discovery and assessment phase has already been completed.
The organizations that will be caught in an emergency rebuild scenario in Q2 2026 are the ones reading this article for the first time today and assuming they still have time.
What Comes Next
Now that you understand the deadlines, what is affected, and who is most at risk — the next question is: why is InfoPath migration technically complex, and what are the compliance implications of missing this deadline?
Part 2 of this series — “Why InfoPath Migration Is Harder Than You Think” — covers the technical reasons no automated migration tool exists, the most common migration mistakes, and the specific HIPAA, SOX, and ISO 27001 compliance risks that regulated-industry IT teams need to understand.
Part 3 — “How to Migrate from InfoPath Before the Microsoft EOL” — walks through the full step-by-step migration framework, the Microsoft replacement tool decision guide, realistic cost and timeline ranges, and a 14-point action checklist for IT teams.
READ THE FULL SERIES
Part 1 (this post): Microsoft InfoPath EOL — Two Deadlines IT Teams Must Know Before July 14, 2026
Part 2: Why InfoPath Migration Is Harder Than You Think — Technical Risks, Compliance Exposure, and What to Do About It
Part 3: How to Migrate from InfoPath Before the Microsoft EOL — A Step-by-Step Guide for IT Teams
All three posts available at winmgmtexperts.com/blog
