SOLVED

InfoPath support in SharePoint Online

%3CLINGO-SUB%20id%3D%22lingo-sub-96994%22%20slang%3D%22en-US%22%3EInfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-96994%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EWhile%20reviewing%20the%20settings%20on%20the%20InfoPath%20page%20in%20a%20SharePoint%20Online%20admin%20center%2C%20I%20saw%20the%20following%20warning.%26nbsp%3B%20Note%20that%20is%20says%20%3C%2FSPAN%3E%3CSPAN%3E2015.%20%3C%2FSPAN%3E%3CSPAN%3EHas%20MS%20already%20stopped%20support%20InfoPath%20in%20SPO%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F18735iBD62971E5E20F1B8%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22InfoPathSupport.png%22%20title%3D%22InfoPathSupport.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-96994%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-167494%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-167494%22%20slang%3D%22en-US%22%3E%3CP%3EI%20read%20the%20following%20in%20%3CA%20title%3D%22this%20redmondmag%20article%22%20href%3D%22https%3A%2F%2Fredmondmag.com%2Farticles%2F2017%2F10%2F03%2Fsharepoint-server-2019-infopath-support.aspx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethis%20redmondmag%20article%3C%2FA%3E%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThe%20idea%20that%20InfoPath%20will%20live%20on%20as%20a%20tool%20for%20SharePoint%20Server%202019%20also%20was%20affirmed%20by%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fwww.linkedin.com%2Fin%2Fvladcatrinescu%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EVlad%20Catrinescu%3C%2FA%3E%3CSPAN%3E%2C%20a%20Microsoft%20MVP%20and%20president%20of%20vNext%20Solutions%2C%20in%20an%20Oct.%202%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fwww.crowcanyon.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECrow%20Canyon%20Software%3C%2FA%3E%3CSPAN%3Etalk%2C%20which%20is%20available%20on%20demand%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dene7ynIpocM%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3CSPAN%3E.%20%3CSTRONG%3ECatrinescu%20said%20that%20while%20not%20much%20is%20known%20about%20SharePoint%20Server%202019%2C%20%22we%20know%20for%20sure%20that%20InfoPath%20will%20be%20back.%22%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EI%20can't%20see%20replicating%20what%20InfoPath%20can%20do%20using%20Flow%20and%20PowerApps%20(though%20I%20do%20see%20lots%20of%20great%20uses%20for%20those!)%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThere's%20hope%20yet!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-149407%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-149407%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20not%20creating%20anything%20new%20in%20InfoPath%20and%20we%20are%20advising%20our%20clients%20to%20use%20other%20technologies%20to%20create%20new%20forrms.%20It%20still%20works%20but%20there%20are%20so%20many%20limitations%20and%20better%20options%2C%20that%20I%20would%20be%20hard%20pressed%20to%20find%20a%20good%20scenario%20that%20would%20require%20its%20use.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-149184%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-149184%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20381px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F27478i736EB5CF85651C99%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22InfoPathMessage%20(2).png%22%20title%3D%22InfoPathMessage%20(2).png%22%20%2F%3E%3C%2FSPAN%3EI%20still%20see%20the%202015%20message%20in%20O365%20-%20SharePoint%20Admin%20center%20when%20enabling%20InfoPath.%20%3CBR%20%2F%3E%3CBR%20%2F%3EWill%20this%20eventually%20be%20updated%2C%20or%20did%20%22until%20further%20notice'%20end%20up%20being%202015%3F%3CBR%20%2F%3E%3CBR%20%2F%3EDoes%20anyone%20have%20any%20experiences%20they%20can%20share%20with%20enabling%2Fusing%26nbsp%3BInfoPath%20with%20SharePoint%20Online%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97876%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97876%22%20slang%3D%22en-US%22%3E%3CP%3EEverything%20you%20heard%20at%20Ignite%20is%20100%25%20correct.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20support%20cycle%20for%20InfoPath%20on%20SharePoint%202016%20is%20that%20it%20will%20run%20until%202026.%26nbsp%3B%20It%20bears%20repeating%2C%20however%2C%20that%20InfoPath%20is%20deprecated%20which%20also%20means%20that%20it%20can%20be%20removed%20from%20subsequent%20versions%20of%20the%20on%20premises%20product%2C%20vNext%20and%20beyond.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20is%20DIFFERENT%20governance%20for%20service%20removals%20in%20Office%20365.%20The%20strict%20guidance%20is%20that%20Microsoft%20will%20give%20at%20least%2030%20days%20notice%20when%20we've%20indiciated%20a%20replacement%20product%3B%20365%20days%20notice%20if%20there%20is%20no%20replacement%3B%20and%20that%20undocumented%2C%20unsupported%20features%20or%20risks%20which%20are%20found%20to%20compromise%20the%20security%20or%20platform%20integrity%20could%20be%20turned%20off%20immediately.%26nbsp%3B%20For%20example%2C%20if%20we%20found%20a%20huge%20security%20loophole%20in%20the%20%22Widget%22%20web%20part%2C%20for%20example%2C%20we%20might%20remove%20that%20web%20part%20immediately%20to%20protect%20our%20customers%20while%20we%20work%20on%20the%20issue.%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%202026%20date%20has%20no%20relationship%20to%20a%20%22date%22%20for%20Office%20365%2C%20because%20we%26nbsp%3Bconsciciously%20haven't%20published%20a%20timeline%20for%20taking%20that%20out%20of%20service.%26nbsp%3B%20That%20said%2C%20as%20we%20(me)%20also%20discussed%20at%20Ignite%20last%20year%2C%20we%20couldn't%26nbsp%3Bconsider%20taking%20IPFS%20out%20of%20service%20in%20Office%20365%20without%20significant%20lead%20time.%26nbsp%3B%20By%20precendent%20%2C%20even%20though%20we%20identified%20a%20replacement%20tech%20for%20Access%20Web%20Apps%20(PowerApps)%20we%20communicated%20that%20service%20removal%2015%20months%20in%20advance.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMoving%20forward%2C%20to%20be%20fair%2C%20I%20hope%20we've%20clearly%20indicated%20we%20see%20PowerApps%20as%20the%20eventual%20replacement%20for%20InfoPath.%26nbsp%3B%20InfoPath%20is%20deprecated%20which%20means%20it%20no%20longer%20gets%20invetment%20in%20new%20fearueres%20or%20scenarios.%20%26nbsp%3B%20Have%20we%20covered%20all%20the%20critical%20scenarios%20for%20PowerApps%20yet%3F%26nbsp%3B%20No%20-%20and%20that's%20why%20we%20also%20hope%20you%20let%20us%20know%20which%20InfoPath%20features%20are%20the%20most%20important%20to%20you%20at%20%3CA%20href%3D%22http%3A%2F%2FSharePoint.UserVoice.com.%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2FSharePoint.UserVoice.com.%26nbsp%3B%3C%2FA%3E%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97871%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97871%22%20slang%3D%22en-US%22%3E%3CP%3EHey%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F98%22%20target%3D%22_blank%22%3E%40Chris%20McNulty%3C%2FA%3E%26nbsp%3B-%20Just%20to%20confirm%20the%20date%3CA%20href%3D%22https%3A%2F%2Fblogs.office.com%2Fen-us%2F2016%2F01%2F20%2Fsharepoint-server-2016-and-project-server-2016-release-candidate-available%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%26nbsp%3Bfrom%20the%20blog%20post%20you%20referenced%3C%2FA%3E%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E----%3C%2FP%3E%3CP%3EAs%20we%20continue%20to%20evolve%2C%20we%20recognize%20the%20need%20for%20a%20long%20runway%20as%20we%20augment%20existing%20business%20app%20offerings%20with%20new%20tools%20and%20capabilities.%20As%20a%20result%2C%20we%E2%80%99re%20updating%20the%20support%20timelines%20in%20conjunction%20with%20SharePoint%20Server%202016%2C%20specifically%3A%3C%2FP%3E%3CUL%3E%3CLI%3ESharePoint%20Server%202016%20will%20include%20an%20ongoing%20capability%20to%20host%20InfoPath%20Forms%20Services.%20InfoPath%20Forms%20Services%20on%20SharePoint%202016%20will%20be%20supported%20for%20the%20duration%20of%20SharePoint%202016%E2%80%99s%20support%20lifecycle.%3C%2FLI%3E%3CLI%3EInfoPath%20Forms%20Services%20on%20Office%20365%20will%20continue%20to%20be%20supported.%3C%2FLI%3E%3CLI%3EInfoPath%202013%20and%20SharePoint%20Designer%202013%20will%20be%20the%20last%20versions%20of%20those%20products.%20SharePoint%20Designer%20is%20not%20being%20re-released%20with%20SharePoint%20Server%202016%2C%20although%20we%20will%20continue%20to%20support%20custom%20workflows%20built%20with%20SharePoint%20Designer%20and%20hosted%20on%20SharePoint%20Server%202016%20and%20Office%20365.%20Support%20for%20InfoPath%202013%20and%20SharePoint%20Designer%202013%20will%20match%20the%20support%20lifecycle%20for%20SharePoint%20Server%202016%2C%20running%20until%202026.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E----%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20that%20last%20point%20trying%20to%20state%20that%20InfoPath%20forms%20and%20SharePoint%20Designer%20workflows%20will%20continue%20to%20function%20in%20Office%20365%20until%202026%3F%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20ask%20because%20every%20time%20I%20heard%20a%20Microsoft%20person%20answer%20this%20question%20at%20Ignite%202016%2C%20the%20answer%20was%20%22Microsoft%20will%20support%20Designer%20as%20long%20as%20we%20need%20to%20in%20SharePoint%20Online%22%20and%20the%202026%20date%20was%20only%20applicable%20to%20SharePoint%20Server%202016.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97091%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97091%22%20slang%3D%22en-US%22%3EBill%20and%20i%20are%20tracking%20the%20source%20down...it%20is%20NOT%20accurate%2C%20as%20you%20noted.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97089%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97089%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F98%22%20target%3D%22_blank%22%3E%40Chris%20McNulty%3C%2FA%3Ethanks%20for%20the%20response%20and%20the%20link%20to%20the%20information%20that%20I%20remembered%20seeing%2C%20but%20could%20not%20find.%20Given%20that%20the%20popup%20message%20mentions%202015%20and%20is%20not%20consistent%20with%20the%20message%20from%20January%202016%2C%20I%20have%20to%20assume%20that%20it%20is%20a%20mistake.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20please%20make%20sure%20that%20it%20gets%20corrected%20so%20that%20others%20are%20not%20confused%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97082%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97082%22%20slang%3D%22en-US%22%3Eslip%20of%20the%20finger%20sorry%2C%202025%20I%20meant.%3CBR%20%2F%3E%3CBR%20%2F%3EWith%20all%20due%20respect%2C%20what%20Microsoft%20says%20they%20will%20do%2C%20and%20what%20Microsoft%20actually%20does%20are%20two%20completely%20different%20things%20(yes%20a%20generalization%2C%20Microsoft%20are%20generally%20pretty%20good%20with%20it)%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97081%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97081%22%20slang%3D%22en-US%22%3EI'm%20not%20sure%20what%202015%20has%20to%20do%20with%20this.%20%3CBR%20%2F%3E%3CBR%20%2F%3EWith%20all%20due%20respect%20to%20our%20friends%20on%20the%20Cloudshow%2C%20they%20are%20not%20up%20to%20speed%20with%20the%20way%20we%20deprecate%20features%20on%20line.%20I%20discussed%20this%20at%20length%20during%20the%20ignite%20conference%20last%20year.%3CBR%20%2F%3E%3CBR%20%2F%3E%20it%20is%20our%20general%20rule%20to%20announce%20replacement%20technology%20at%20the%20time%20of%20deprecation%20and%20then%20provide%20at%20least%20a%20years%20notice%2C%20if%20not%20longer.%20Of%20course%2C%20we%20always%20act%20to%20assure%20stability%20and%20security%20of%20the%20service.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97078%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97078%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20mentioned%20in%20the%20MS%20Cloud%20show%2C%20I%20feel%20this%20will%20be%20the%20same%20case%20as%20Sandbox%20web%20parts%2C%20%3CSTRIKE%3E2015%3C%2FSTRIKE%3E%26nbsp%3B2025%20they%20will%20just%20stop%20working%2C%20and%20it%20will%20be%20you've%20had%207%20years%20to%20migrated%20away%20from%20using%20them.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97044%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97044%22%20slang%3D%22en-US%22%3EWe%20announced%20last%20year%20that%20the%20support%20was%20extended%20to%202026.%20%3CA%20href%3D%22https%3A%2F%2Fblogs.office.com%2Fen-us%2F2016%2F01%2F20%2Fsharepoint-server-2016-and-project-server-2016-release-candidate-available%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.office.com%2Fen-us%2F2016%2F01%2F20%2Fsharepoint-server-2016-and-project-server-2016-release-candidate-available%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97030%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97030%22%20slang%3D%22en-US%22%3E%3CP%3EThe%202022%2F2023%20date%20was%20for%20SharePoint%20Server%20though%2C%20right%3F%20It%20seemed%20less%20certain%20than%20that%20for%20Online%20tenants.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97028%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97028%22%20slang%3D%22en-US%22%3E%3CP%3EAFAIK%2C%20InfoPath%20support%20will%20end%20in%202022%20as%20stated%20by%20Microsoft%20at%20Ignite%202015...I'm%20not%20aware%20of%20any%20change%20in%20this%20statement%20cc%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F98%22%20target%3D%22_blank%22%3E%40Chris%20McNulty%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97013%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20support%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97013%22%20slang%3D%22en-US%22%3E%3CP%3EBest%20I%20could%20find%20on%20InfoPath%20Form%20Services%20for%20Office%20365%20was%20%22supported%20until%20further%20notice.%22%20I%20haven't%20seen%2Ffound%20anything%20from%20any%20source%20that%20directly%20states%20when%20support%20for%20InfoPath%20in%20SharePoint%20Online%20is%2Fwas%20stopping%20aside%20from%20what%20was%20stated%20at%20aka.ms%2Fipfs.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Respected Contributor

While reviewing the settings on the InfoPath page in a SharePoint Online admin center, I saw the following warning.  Note that is says 2015. Has MS already stopped support InfoPath in SPO?

InfoPathSupport.png

14 Replies
Highlighted

Best I could find on InfoPath Form Services for Office 365 was "supported until further notice." I haven't seen/found anything from any source that directly states when support for InfoPath in SharePoint Online is/was stopping aside from what was stated at aka.ms/ipfs.

Highlighted

AFAIK, InfoPath support will end in 2022 as stated by Microsoft at Ignite 2015...I'm not aware of any change in this statement cc @Chris McNulty

Highlighted

The 2022/2023 date was for SharePoint Server though, right? It seemed less certain than that for Online tenants.

Highlighted
Highlighted

As mentioned in the MS Cloud show, I feel this will be the same case as Sandbox web parts, 2015 2025 they will just stop working, and it will be you've had 7 years to migrated away from using them.

Highlighted
I'm not sure what 2015 has to do with this.

With all due respect to our friends on the Cloudshow, they are not up to speed with the way we deprecate features on line. I discussed this at length during the ignite conference last year.

it is our general rule to announce replacement technology at the time of deprecation and then provide at least a years notice, if not longer. Of course, we always act to assure stability and security of the service.
Highlighted
slip of the finger sorry, 2025 I meant.

With all due respect, what Microsoft says they will do, and what Microsoft actually does are two completely different things (yes a generalization, Microsoft are generally pretty good with it) :)
Highlighted

@Chris McNultythanks for the response and the link to the information that I remembered seeing, but could not find. Given that the popup message mentions 2015 and is not consistent with the message from January 2016, I have to assume that it is a mistake.

 

Can you please make sure that it gets corrected so that others are not confused?

Highlighted
Best Response confirmed by Dean Gross (Respected Contributor)
Solution
Bill and i are tracking the source down...it is NOT accurate, as you noted.
Highlighted

Hey @Chris McNulty - Just to confirm the date from the blog post you referenced:

 

----

As we continue to evolve, we recognize the need for a long runway as we augment existing business app offerings with new tools and capabilities. As a result, we’re updating the support timelines in conjunction with SharePoint Server 2016, specifically:

  • SharePoint Server 2016 will include an ongoing capability to host InfoPath Forms Services. InfoPath Forms Services on SharePoint 2016 will be supported for the duration of SharePoint 2016’s support lifecycle.
  • InfoPath Forms Services on Office 365 will continue to be supported.
  • InfoPath 2013 and SharePoint Designer 2013 will be the last versions of those products. SharePoint Designer is not being re-released with SharePoint Server 2016, although we will continue to support custom workflows built with SharePoint Designer and hosted on SharePoint Server 2016 and Office 365. Support for InfoPath 2013 and SharePoint Designer 2013 will match the support lifecycle for SharePoint Server 2016, running until 2026.

----

 

Is that last point trying to state that InfoPath forms and SharePoint Designer workflows will continue to function in Office 365 until 2026?  

 

I ask because every time I heard a Microsoft person answer this question at Ignite 2016, the answer was "Microsoft will support Designer as long as we need to in SharePoint Online" and the 2026 date was only applicable to SharePoint Server 2016.

Highlighted

Everything you heard at Ignite is 100% correct.

 

The support cycle for InfoPath on SharePoint 2016 is that it will run until 2026.  It bears repeating, however, that InfoPath is deprecated which also means that it can be removed from subsequent versions of the on premises product, vNext and beyond.

 

There is DIFFERENT governance for service removals in Office 365. The strict guidance is that Microsoft will give at least 30 days notice when we've indiciated a replacement product; 365 days notice if there is no replacement; and that undocumented, unsupported features or risks which are found to compromise the security or platform integrity could be turned off immediately.  For example, if we found a huge security loophole in the "Widget" web part, for example, we might remove that web part immediately to protect our customers while we work on the issue.  

 

The 2026 date has no relationship to a "date" for Office 365, because we consciciously haven't published a timeline for taking that out of service.  That said, as we (me) also discussed at Ignite last year, we couldn't consider taking IPFS out of service in Office 365 without significant lead time.  By precendent , even though we identified a replacement tech for Access Web Apps (PowerApps) we communicated that service removal 15 months in advance.

 

Moving forward, to be fair, I hope we've clearly indicated we see PowerApps as the eventual replacement for InfoPath.  InfoPath is deprecated which means it no longer gets invetment in new fearueres or scenarios.   Have we covered all the critical scenarios for PowerApps yet?  No - and that's why we also hope you let us know which InfoPath features are the most important to you at http://SharePoint.UserVoice.com.  Thanks.

Highlighted

InfoPathMessage (2).pngI still see the 2015 message in O365 - SharePoint Admin center when enabling InfoPath.

Will this eventually be updated, or did "until further notice' end up being 2015?

Does anyone have any experiences they can share with enabling/using InfoPath with SharePoint Online?

Highlighted

I am not creating anything new in InfoPath and we are advising our clients to use other technologies to create new forrms. It still works but there are so many limitations and better options, that I would be hard pressed to find a good scenario that would require its use. 

Highlighted

I read the following in this redmondmag article:

 

The idea that InfoPath will live on as a tool for SharePoint Server 2019 also was affirmed by Vlad Catrinescu, a Microsoft MVP and president of vNext Solutions, in an Oct. 2 Crow Canyon Softwaretalk, which is available on demand here. Catrinescu said that while not much is known about SharePoint Server 2019, "we know for sure that InfoPath will be back."

 

I can't see replicating what InfoPath can do using Flow and PowerApps (though I do see lots of great uses for those!)

 

There's hope yet!