Microsoft InfoPath, a forms tool that has been in use for over two decades, is officially retiring. With InfoPath Forms Services scheduled to be removed from Microsoft 365 in July 2026, organizations still relying on InfoPath forms need to understand the timeline and prepare for transition.
The Retirement Timeline
Here are the critical dates for InfoPath retirement:
Microsoft 365 (Cloud) Environments
- July
14, 2026: InfoPath Forms Services completely removed from SharePoint
Online
- Applies
to all Microsoft 365 tenants (Commercial, GCC, GCC High, DoD)
- No
extensions or exceptions will be granted by Microsoft
- InfoPath
Client 2013 reaches end of extended support on the same date
On-Premises Environments
InfoPath support varies by SharePoint Server version:
- SharePoint
Server 2016: InfoPath Forms Services support ends July 14, 2026
- SharePoint
Server 2019: InfoPath Forms Services support ends July 14, 2026
- SharePoint
Server Subscription Edition: InfoPath Forms Services support ends July
14, 2026
Important note: Unlike some other Microsoft products,
on-premises environments receive no extended support beyond this date for
InfoPath.
Configuration Changes Already in Effect
Microsoft has already begun restricting InfoPath
capabilities:
- Creating
new custom InfoPath forms in SharePoint Online is being phased out
- Configuration
options are being removed from the SharePoint Admin Center
- New
tenants created after the retirement announcement have limited InfoPath
functionality
What Happens on July 15, 2026?
Understanding the immediate impact is critical for planning:
For End Users:
- Will
be completely unable to submit new form responses using InfoPath service
- Cannot
fill out InfoPath forms through web browsers
- Existing
form data remains in SharePoint lists but forms become non-functional
- Can
download InfoPath templates (.xsn) or form data (.xml) to view with
InfoPath Client 2013 (if they have file permissions)
For Designers/Publishers:
- Completely
disallowed from creating, modifying, or publishing InfoPath templates
- Cannot
make any changes to existing InfoPath forms
- All
form design capabilities removed from SharePoint Online
For Business Processes:
- Critical
workflows dependent on InfoPath forms will immediately break
- Data
collection processes (surveys, requests, intake forms) will halt
- Approval
processes using InfoPath will stop functioning
- Integration
with other systems relying on InfoPath data will fail
What Remains:
- Historical
form data stored in SharePoint lists persists
- Form
templates (.xsn files) can be downloaded for archival purposes
- Raw
XML data from submitted forms remains accessible
Why There's No Extension Coming
Microsoft has explicitly stated there will not be an option
to extend InfoPath Forms Services in SharePoint Online beyond July 14, 2026.
The reasons are clear:
- InfoPath
was last updated in 2013—over a decade ago with no new features
- The
technology doesn't support modern requirements for mobile, cross-platform,
or cloud-native experiences
- Microsoft
has invested heavily in Power Apps as the official successor
- Maintaining
legacy infrastructure creates security and compliance risks
- Industry
feedback indicates businesses need integrated forms experiences that
InfoPath cannot provide
The Migration Challenge
Unlike some Microsoft migrations, there is no automated
migration tool for InfoPath to Power Apps. Every InfoPath form must be:
- Analyzed
for functionality, data connections, and business logic
- Manually
rebuilt in the new platform (typically Power Apps)
- Tested
thoroughly before deployment
- Validated
with end users and business owners
This reality makes early planning essential. Organizations
with dozens or hundreds of InfoPath forms face months of migration work.
Immediate Actions for IT Teams
If your organization still uses InfoPath forms, take these
steps immediately:
This week:
- Run
the Microsoft 365 Assessment Tool to scan your tenant for all InfoPath
usage
- Generate
the Power BI InfoPath Report to identify:
- All
InfoPath forms across site collections and sites
- Recency
and volume of form usage
- Lists,
libraries, and content types using InfoPath
- Identify
business owners for each form
- Categorize
forms by business criticality
This month:
- Prioritize
forms for migration based on business impact
- Assess
which forms can be retired instead of migrated
- Evaluate
Power Apps licensing requirements for your organization
- Determine
if you need external consulting assistance
- Create
a detailed migration timeline working backward from July 2026
Within 90 days:
- Begin
rebuilding your highest-priority forms in Power Apps
- Establish
design patterns and governance for new Power Apps forms
- Pilot
migrated forms with small user groups
- Document
standard approaches for common form patterns
- Train
power users and form designers on Power Apps
Microsoft's Recommended Alternatives
Microsoft suggests migrating to their modern Power Platform
tools based on your specific scenarios:
Microsoft Forms:
- Best
for: Simple surveys, polls, quizzes, and basic data collection
- Key
capabilities: Quick deployment, built-in analytics, automatic Excel
integration
- Limitations:
Limited customization, basic data connections, no complex business logic
Power Apps:
- Best
for: Complex forms with business logic, data connections, and
integration requirements
- Key
capabilities: Full customization, connects to 1,000+ data sources,
advanced validation, offline capability
- Microsoft's
official recommendation: Primary successor to InfoPath
- Consideration:
Requires learning curve and potentially Premium licensing for advanced
features
Power Automate (complementary):
- Use
case: Automate workflows triggered by form submissions
- Integration:
Works seamlessly with both Forms and Power Apps
- Replaces:
SharePoint Designer workflows often paired with InfoPath
Common migration patterns:
- Simple
data collection: InfoPath → Microsoft Forms
- Complex
business forms: InfoPath → Power Apps
- Forms
+ workflows: InfoPath + SharePoint Designer → Power Apps + Power
Automate
- Multi-source
data: InfoPath with data connections → Power Apps with connectors
Common InfoPath Form Scenarios and Solutions
To help plan your migration, here are typical InfoPath use
cases and their modern equivalents:
Scenario 1: Employee Onboarding Forms
- Legacy:
InfoPath form collecting employee information
- Modern:
Power Apps form with data connections to HR systems, automated workflows
via Power Automate
Scenario 2: IT Service Request Forms
- Legacy:
InfoPath form for help desk requests
- Modern:
Power Apps integrated with Microsoft Teams, automated ticket creation in
service management system
Scenario 3: Approval Workflows (PO approvals, time-off
requests)
- Legacy:
InfoPath form + SharePoint Designer workflow
- Modern:
Power Apps form + Power Automate approval flows with email/Teams
notifications
Scenario 4: Survey or Feedback Collection
- Legacy:
InfoPath form for simple surveys
- Modern:
Microsoft Forms (for basic needs) or Power Apps (for complex scenarios)
Scenario 5: Multi-Source Data Integration
- Legacy:
InfoPath with data connections to SQL, SharePoint lists, web services
- Modern:
Power Apps with connectors to databases, SharePoint, APIs, and 1,000+
other sources
The Reality of InfoPath Migration
Based on lessons learned from other Microsoft retirements,
organizations should expect:
Timeline considerations:
- Discovery
phase often reveals more forms than initially known
- Each
complex form can take days or weeks to rebuild and test
- User
acceptance testing and training add significant time
- Organizations
with 50+ forms should plan 6-12 months for complete migration
Resource requirements:
- Internal
IT staff need training on Power Apps development
- Business
users need training on using and managing new forms
- Consider
Microsoft partners for large-scale migrations
- Budget
for Power Apps Premium licensing if advanced features are needed
Common pitfalls:
- Underestimating
the number of forms in use
- Attempting
last-minute migrations in late 2025/early 2026
- Not
involving business owners early in the process
- Treating
migration as purely technical rather than business transformation
- Ignoring
the opportunity to modernize and improve forms during migration
Why You Can't Wait
The July 2026 deadline may seem distant, but successful
InfoPath migrations are complex and time-intensive:
Risk of delay:
- High
demand for migration resources as deadline approaches (expect consultant
scarcity in 2025-2026)
- Rushed
migrations lead to errors and business disruptions
- Missing
the deadline means immediate business process failures
- Forms
stop working mid-process with no warning or grace period
Opportunity of early action:
- Time
to modernize processes, not just replicate old forms
- Ability
to consolidate redundant forms
- Properly
train users on new tools
- Avoid
emergency mode and last-minute workarounds
- Negotiate
better rates with consultants before market demand peaks
The Bottom Line
July 14, 2026 is a firm deadline with no extensions.
InfoPath forms will completely stop functioning in Microsoft 365 on July 15,
2026. Organizations waiting until 2025 to begin planning face serious risks of
business disruption.
The transition from InfoPath to Power Apps isn't just about
maintaining existing functionality—it's an opportunity to modernize your forms,
improve user experience, and build on a platform that Microsoft is actively
developing and supporting.
Start your InfoPath assessment and migration planning now.
The organizations that begin early will have time to do it right, while those
who wait will face costly emergency migrations.
Resources:
