SharePoint  

InfoPath Retirement: What IT Professionals Need to Know

Microsoft InfoPath Retirement: What Organizations Must Know Before July 2026

Microsoft InfoPath, a forms solution 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 that still rely on InfoPath must understand the timeline and begin planning their transition.

The Retirement Timeline

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

  • InfoPath Client 2013 reaches end of extended support on the same date

On-Premises Environments

InfoPath support depends on SharePoint Server version:

  • SharePoint Server 2016 – Support ends July 14, 2026

  • SharePoint Server 2019 – Support ends July 14, 2026

  • SharePoint Server Subscription Edition – Support ends July 14, 2026

Important: No extended support beyond this date will be provided for on-premises environments.

Configuration Changes Already in Effect

Microsoft has already begun limiting 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?

For End Users

  • Unable to submit new InfoPath form responses

  • Cannot fill out InfoPath forms via web browser

  • Existing form data remains stored in SharePoint lists

  • Templates (.xsn) and XML data can still be downloaded for archival purposes

For Designers and Publishers

  • Cannot create, modify, or publish InfoPath templates

  • All design capabilities removed from SharePoint Online

  • No updates to existing forms permitted

For Business Processes

  • Workflows dependent on InfoPath will stop functioning

  • Data collection processes will halt

  • Approval processes will break

  • System integrations relying on InfoPath data may fail

What Remains Accessible

  • Historical data in SharePoint lists

  • Downloadable .xsn template files

  • Raw XML submission data

Why There Will Be No Extension

Microsoft has clearly stated there will be no extension beyond July 14, 2026.

Key reasons include:

  • InfoPath was last updated in 2013

  • It does not support modern mobile or cloud-native experiences

  • Microsoft has invested heavily in Power Platform

  • Legacy infrastructure introduces security and compliance risks

  • Modern businesses require integrated digital form experiences

The Migration Challenge

There is no automated migration tool from InfoPath to Power Apps.

Each form must be:

  • Analyzed for functionality and logic

  • Manually rebuilt

  • Thoroughly tested

  • Validated with stakeholders

Organizations with large numbers of forms should anticipate substantial effort and planning.

Immediate Actions for IT Teams

This Week

  • Run Microsoft 365 Assessment Tool

  • Generate Power BI InfoPath usage reports

  • Identify all InfoPath forms across sites

  • Determine usage volume and recency

  • Identify business owners

  • Categorize forms by criticality

This Month

  • Prioritize migrations

  • Identify forms that can be retired

  • Assess Power Apps licensing needs

  • Determine external support requirements

  • Create migration timeline

Within 90 Days

  • Begin rebuilding high-priority forms

  • Establish Power Apps governance standards

  • Pilot with small user groups

  • Document migration patterns

  • Train key users

Microsoft’s Recommended Alternatives

Microsoft Forms

Best for:

  • Simple surveys

  • Polls and quizzes

  • Basic data collection

Strengths:

  • Fast deployment

  • Built-in analytics

  • Excel integration

Limitations:

  • Limited customization

  • No complex logic

Power Apps

Best for:

  • Complex forms

  • Advanced validation

  • Multi-source data connections

Capabilities:

  • 1,000+ connectors

  • Offline support

  • Enterprise integration

Official successor to InfoPath.

Power Automate

Use for:

  • Workflow automation

  • Approval flows

  • Notifications

Often replaces SharePoint Designer workflows.

Common Migration Patterns

  • Simple data collection → Microsoft Forms

  • Complex forms → Power Apps

  • Forms + workflows → Power Apps + Power Automate

  • Multi-source integration → Power Apps with connectors

Migration Reality and Planning Expectations

Timeline Considerations

  • Discovery often reveals more forms than expected

  • Complex forms may require weeks to rebuild

  • Testing and training add time

  • 50+ forms may require 6–12 months

Resource Requirements

  • IT training in Power Apps

  • User training

  • Potential partner support

  • Budget planning for Premium licensing

Common Pitfalls

  • Underestimating form volume

  • Delaying until 2025

  • Ignoring business stakeholder input

  • Treating migration as purely technical

  • Missing modernization opportunities

Why You Cannot Wait

Risks of Delay

  • Consultant shortages near deadline

  • Rushed migrations increase failure risk

  • Immediate business disruption on July 15, 2026

  • No grace period

Benefits of Early Action

  • Time to modernize

  • Opportunity to consolidate forms

  • Proper training

  • Avoid emergency scenarios

  • Better vendor negotiation opportunities

The Bottom Line

July 14, 2026 is a firm, non-negotiable deadline.

InfoPath forms will stop functioning in Microsoft 365 on July 15, 2026.

Organizations that delay planning risk business disruption. Those who begin early gain the opportunity to modernize, improve user experience, and transition to supported, actively developed Microsoft platforms.

Now is the time to assess, plan, and beg