Back
InfoPath

Update on InfoPath and SharePoint Forms

Customers have been asking us about the future of InfoPath and SharePoint forms, and today we’re ready to share some information on the next generation of Office forms.

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. We are looking to make investments that allow you to easily design, deploy, and use intelligent, integrated forms across Office clients, servers, and services—forms that everyone can use on their PC, tablet, or phone. Our goal is to deliver tools that are flexible and agile, so you can quickly connect to your data and processes in new and exciting ways.

So how are we evolving our forms technology? In an effort to streamline our investments and deliver a more integrated Office forms user experience, we’re retiring InfoPath and investing in new forms technology across SharePoint, Access, and Word. This means that InfoPath 2013 is the last release of the desktop client, and InfoPath Forms Services in SharePoint Server 2013 is the last release of InfoPath Forms Services. The InfoPath Forms Services technology within Office 365 will be maintained and it will function until further notice.

If you’re an InfoPath customer, we want to reassure you that we’re working on migration guidance in parallel as we’re building our next generation of forms technology. Until we have more detailed technology roadmap and guidance to share with you, we encourage you to continue using InfoPath tools. We also want to remind you that the InfoPath 2013 desktop client and InfoPath Forms Services for SharePoint Server 2013 will continue to be supported through 2023 as part of our Lifecycle support policy.

We’ll provide more details on the future of Office forms later this year. If you’re attending the SharePoint Conference in March, you can get a sneak peek of what we’re building in “InfoPath and SharePoint Forms Roadmap” session. If you can’t attend or you want to review or share the information later, you’ll be able to view this session online after the conference.

InfoPath frequently asked questions

1.  Will Microsoft be shipping another version of InfoPath?
No, there will not be another version of the InfoPath desktop client or InfoPath Forms Services. We are focusing all of our investments on new intelligent, integrated forms experiences across Office technology.

2.  How long will InfoPath be supported?

  • The InfoPath 2013 client will be supported through April 2023.
  • InfoPath Forms Services for SharePoint Server 2013 will be supported until April 2023.
  • InfoPath Forms Services in Office 365 will be supported until further notice.

For more information on InfoPath Forms Services support in Office 365, please review our Online Services Support Lifecycle Policy.

3.  What should I use to build and complete forms?
You should continue to use InfoPath technology.

4.  Will there be a migration tool or process for the next generation of forms technology?
We’ll provide more details on migration scenarios and guidance in Q4 of CY 2014.

5.  What will the new forms capabilities be in SharePoint, Access, and Word? When will they be available?
We’ll be sharing updates throughout the year, with a sneak peek in March at the SharePoint Conference.

Join the conversation

5 comments
  1. PLEASE with the new forms version, and SharePoint, PLEASE PLEASE! allow Enterprise Keywords / Terms to be used, that’s one thing I HATED was not available in InfoPath, I love being able to use Enterprise Keywords in SharePoint 2013 and would love to do so in the new forms and new forms integration with SharePoint! Thank you!

  2. Seems no-one likes InfoPath going by the significant absence of reaction across the web – what a shame a great product has been laid to rest! As a SharePoint developer who has invested heavily in InfoPath for data collection and workflow I can say that the replacement better be extremely good to even come close to replacing it.

    InfoPath Filller as a Windows 8 app would have been a killer enterprise option for Surface RT – in the absence of this why wasn’t the work to port InfoPath to Windows RT completed? The desktop filler on Surface RT with the Designer as a free product (as SharePoint Designer is) would have been a satisfactory alternative to a full metro version and either option might have sold a lot more businesses on Surface RT.

  3. I didn’t like InfoPath when it was first released, but over the years I have really come to value it, mainly for its versatility and integration with SharePoint.

    I am not surprised to see it being retired though as, with the exception of a minor tweak in color, there was not a single change in InfoPath 2013.

    Whenever we do an InfoPath project we always recommend our customer to archive forms in MS-Word or PDF format. We have used the Mohimbi PDF Converter for SharePoint to automate this process, it does a pretty good job when converting InfoPath forms and attachments. They have a blog post up at http://blog.muhimbi.com/2012/02/convert-infopath-to-ms-word-excel-xps.html

    Keeping my fingers crossed that there will indeed be a robust upgrade path from InfoPath to whatever tool will replace it. I am not holding my breath, but one can have hope.

  4. I have been developing applications using InfoPath, SharePoint & Nintex for five years now. I always thought that InfoPath’s integration with SharePoint considerably reduced development time and made it for rich robust applications.

    Feel sorry to see it being retired. I hope the new technology can perform as better as InfoPath has regarding it’s integration with SharePoint.

  5. Finally. Now lets see some web standards used.

Comments are closed.