SOLVED

Classic mode support timeline

%3CLINGO-SUB%20id%3D%22lingo-sub-3640%22%20slang%3D%22en-US%22%3EClassic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3640%22%20slang%3D%22en-US%22%3E%3CP%3EI%20love%20the%20new%20SharePoint%20experiences%20with%20the%20new%20document%20library%20and%20the%20new%20list.%20It%20needs%20some%20work%2C%20but%20I%20can%20see%20the%20advantages.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20a%20lot%20of%20companies%20have%20customized%20the%20classic%20experience%20and%20tailord%20it%20to%20their%20needs.%20A%20lot%20of%20the%20customizations%20are%20unspported%20in%20the%20new%20model%2C%20at%20least%20for%20now%20and%20some%20will%20stay%20unspported.%20And%20it's%20not%20that%20we%20knew%20we%20were%20doing%20unsupported%20customizations%2C%20as%20some%20of%20these%20were%20advised%20through%20PnP.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhich%20brings%20me%20to%20the%20question.%20What's%20the%20support%20timeline%20for%20classic%20mode%3F%20There%20have%20been%20several%20comments%20in%20the%20different%20networks%2C%20some%20by%20Microsoft%20people%2C%20that%20it's%20supported%20well%20into%202017.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20new%20framework%20will%20most%20likely%20be%20released%20during%20Ignite%20in%20preview%2C%20with%20a%20final%20release%20at%20the%20end%20of%20this%20year.%20If%20you%20combine%20these%20two%2C%20the%20conclusion%20is%2C%20you%20have%20less%20than%20a%20year%20to%20fix%20all%20your%20unsupported%20customizations.%20%26nbsp%3BWhich%20kind%20of%20scares%20me%2C%20and%20my%20customers.%20And%20we%20can't%20even%20really%20prepare%20today%20as%20a%20lot%20of%20the%20details%20are%20not%20know%20yet.%20Like%20the%20provisioning%20aspect.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20with%20that%2C%20InfoPath%20is%20supported%20till%202026%20if%20you%20run%20onpremises.%20For%20Office365%20this%20is%20'until%20further%20notice'.%20I'm%20guessing%20that%20InfoPath%26nbsp%3Bwill%20not%20work%20with%20these%20new%20experiences%20and%20thus%20will%20lose%20support%20when%20classic%20mode%20is%20not%20supported%20anymore.%20There%20has%20been%20a%20rumor%20that%20for%20Office365%20support%20will%20stop%20a%20year%20after%20SharePoint%202016%20is%20released.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAm%20I%20the%20only%20one%20that%20worries%20about%20Microsofts%20intentions%20to%20support%20classic%20mode%20and%20the%20lack%20of%20a%20timeline%20and%20communication%20from%20Microsoft%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3640%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExtensibility%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353675%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353675%22%20slang%3D%22en-US%22%3EThey%20are%20removing%20the%20tenant-level%20classic%20mode%20on%20March%2029th%20-%20Its%20downhill%20from%20here.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-SharePoint-Blog%2FDelivering-SharePoint-modern-experiences%2Fba-p%2F315023%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-SharePoint-Blog%2FDelivering-SharePoint-modern-experiences%2Fba-p%2F315023%3C%2FA%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-335111%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-335111%22%20slang%3D%22en-US%22%3E%3CP%3EI%20know%20the%20original%20post%20was%20made%20in%202016%2C%20but%20doesn't%20it%20just%20show%20how%20wrong%20it%20is%20to%20make%20a%20statement%20like%20this%20without%20the%20full%20facts.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20still%20use%20the%20classic%20sites%20in%20SPO%20and%20O365%20for%20the%202019%20version%20and%20there%20is%20no%20real%20timeline%20for%20when%20and%20if%20they%20will%20be%20depreciated%20or%20even%20removed%20completely.%3CBR%20%2F%3E%3CBR%20%2F%3EInfopath%20has%20been%20depreciated%20as%20of%20writing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297340%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297340%22%20slang%3D%22en-US%22%3E%3CP%3ESure.%20Question%20was%20based%20on%20this%20article%20really.%20Since%20it%20was%202016%20wondering%20an%20update%20on%20timeline.%3C%2FP%3E%3CP%3ELooks%20like%20no%20update%20on%20plans%20for%20end-of-support%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297039%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297039%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Thauja%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EClassic%20mode%20will%20be%20supported%20as%20log%20as%20customer%20have%20them.%20I%20do%20not%20see%20any%20plans%20from%20MS%26nbsp%3B%20to%20remove%20.%26nbsp%3B%20Please%26nbsp%3Bhave%20a%20look%20this%26nbsp%3B%26nbsp%3Barticle%20at%3C%2FSPAN%3E%3CA%20href%3D%22http%3A%2F%2Fdev.office.com%2Fblogs%2Fupdate-on-modern-document-libraries-and-extensiblity%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ehttp%3A%2F%2Fdev.office.com%2Fblogs%2Fupdate-on-modern-document-libraries-and-extensiblity%3C%2FA%3E%26nbsp%3B%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20let%20me%20know%20if%20that%20works%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EThuyavan%3C%2FP%3E%3CP%3E-----------------------------------------------------------------------------------------------------%3C%2FP%3E%3CP%3EYour%20feedback%20is%20very%20valuable%20and%20your%20%E2%80%9Clikes%E2%80%9D%20are%20energy%20boosters%20for%20us%20to%20keep%20blogging%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-296890%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-296890%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Wictor%20on%20the%20assurance%20of%20classic%20mode%20will%20supported%20indefinitely!%20Since%20we%20are%20now%20End%20of%202018%2C%20I%20hope%20the%20statement%20still%20stands!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-153890%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-153890%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20is%20Microsoft%20guideline%20for%20code%20sharing%20between%20classic%20and%20modern%20sites%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3691%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3691%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20are%20no%20plans%20to%20remove%20classic%20mode%20anytime%20soon.%26nbsp%3B%20For%20more%20details%2C%20see%20our%20post%20on%20modern%20extensibility%20at%3CA%20href%3D%22http%3A%2F%2Fdev.office.com%2Fblogs%2Fupdate-on-modern-document-libraries-and-extensiblity%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20http%3A%2F%2Fdev.office.com%2Fblogs%2Fupdate-on-modern-document-libraries-and-extensiblity%26nbsp%3B%3C%2FA%3E%26nbsp%3B%20Until%20we%20roll%20out%20the%20framework%26nbsp%3Band%20related%20patterns%20and%20practices%2C%20we%20havent%20earned%20the%20right%20to%20even%20talk%20about%20it.%26nbsp%3B%20But%20since%20you%20asked%2C%20any%20change%20to%20support%20would%20be%20communicated%20long%20in%20advance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3685%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3685%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F222%22%20target%3D%22_blank%22%3E%40Wictor%20Wilen%3C%2FA%3E%26nbsp%3Bthanks%20for%20the%20quote.%20There%20are%20just%20so%20many%20mixed%20communications%2C%20even%20from%20official%20Microsoft%20sources%2C%20that%20I%20would%20like%20to%20have%20a%20quote%20with%20a%20date%20where%20we%20can%20count%20on.%20And%20not%20'ample%20time'.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20do%20give%20these%20timelines%20on%20most%20things%20onpremises%20(e.g.%20InfoPath)%20and%20even%20for%20a%20product%20like%20Dynamics%20CRM%20online%20you%20know%20what%20to%20expect%20and%20for%20how%20long%20you%20can%20postpone%20updates.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20it's%20just%20guessing%20and%20hoping%20that%20Microsoft%20doesn't%20pull%20support%20too%20soon.%20You%20really%20get%20the%20feel%20from%20many%20comments%20that%20they%20want%20to%20stop%20support%20as%20soon%20as%20possible.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20a%20few%26nbsp%3Bofficial%20comments%20on%20blogs.office.com%20and%20by%26nbsp%3B%3CSPAN%20class%3D%22%20%22%3EChris%20McNulty.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblogs.office.com%2F2016%2F06%2F07%2Fmodern-document-libraries-in-sharepoint%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.office.com%2F2016%2F06%2F07%2Fmodern-document-libraries-in-sharepoint%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EQ.%20How%20long%20will%20classic%20mode%20be%20supported%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EA.%3C%2FSTRONG%3E%26nbsp%3BWe%20recognize%20the%20need%20to%20test%20and%20prepare%20for%20any%20disruption%20to%20user%20experiences%20such%20as%20document%20libraries.%20We%20expect%20to%20run%20the%20two%20modes%20in%20parallel%20into%202017.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FBlogs%2FModern-SharePoint-lists-are-here-Including-integration-with%22%20target%3D%22_self%22%3Ehttps%3A%2F%2Fnetwork.office.com%2Ft5%2FBlogs%2FModern-SharePoint-lists-are-here-Including-integration-with%3C%2FA%3E%3CBR%20%2F%3E%3CSPAN%3E%22Further%20customization%20options%20are%20dependent%20on%20the%20release%20of%20the%20SharePoint%20Framework%20by%20year%20end.%26nbsp%3B%20In%20the%20interim%2C%20classic%20mode%20remains%20fully%20supported.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EFrom%3A%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-ie%2Farticle%2FDifferences-between-the-new-document-library-experience-and-classic-mode-30e1aab0-a5cc-4363-b7f2-09e2ae07d4dc%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-ie%2Farticle%2FDifferences-between-the-new-document-library-experience-and-classic-mode-30e1aab0-a5cc-4363-b7f2-09e2ae07d4dc%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%22Note%20that%20we%20have%20no%20plans%20to%20remove%20classic%20mode.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAnd%20a%20non%20official%26nbsp%3Bquote%20from%20Marc%20Anderson%20(MVP)%20on%20the%20Yammer%20network%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%22One%20of%20the%20things%20that%20scare%20people%20the%20most%20is%20that%20you're%20going%20to%20turn%20of%20%22classic%22%20fast%20and%20without%20warning.%20There%20hasn't%20bee%20good%20communication%20about%20this%2C%20and%20the%20fact%20that%20someone%20in%20an%20official%20post%20I%20can't%20find%20said%20something%20like%20%22we'd%20like%20to%20turn%20off%20classic%20as%20quickly%20as%20possible%22%20make%20people%20very%20wary.%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3662%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3662%22%20slang%3D%22en-US%22%3E%3CP%3EClassic%20mode%20will%20be%20supported%20as%20long%20as%20there%20are%20customers%20using%20it.%20A%20recent%20post%20at%20Office%20Dev%20Center%20says%20that%20it's%20not%20going%20away%20for%20the%20%22forseeable%20future%22%2C%20%3CA%20href%3D%22http%3A%2F%2Fdev.office.com%2Fblogs%2Fupdate-on-modern-document-libraries-and-extensiblity%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fdev.office.com%2Fblogs%2Fupdate-on-modern-document-libraries-and-extensiblity%3C%2FA%3E.%20This%20statement%20should%20ease%20your%20mind%3A%3C%2FP%3E%3CP%3E%3CSTRONG%3E%22We%20will%20continue%20to%20support%20both%20of%20these%20mitigations%20until%20the%20modern%20library%20experience%20supports%20the%20same%20level%20of%20customization%20as%20the%20classic%20one%20and%20partners%20have%20had%20ample%20time%20to%20adapt%20their%20solutions%20to%20the%20new%20experience.%22%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1115017%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1115017%22%20slang%3D%22en-US%22%3E%3CP%3EHi%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%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20post%20dates%20from%202016%20but%20it%20is%20the%20most%20relevant%20when%20searching%20for%20%22SharePoint%20Online%20Classic%20End%20of%20Life%22.%20Has%20anything%20changed%20or%2C%20is%20there%20more%20clarity%20of%20the%20path%20moving%20forward%20as%20we%20are%20entering%202020%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20understand%20we%20should%20be%20working%20into%20moving%20to%20the%20modern%20experience%20but%20some%20things%20are%20still%20not%20there%20yet%2C%20and%20for%20some%20cases%20there%20is%20no%20path%20to%20get%20away%20from%20Classic%2C%20yet.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%2C%3C%2FP%3E%3CP%3EIgnacio%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1147952%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1147952%22%20slang%3D%22en-US%22%3E%3CP%3EHi%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%2C%20just%20to%20keep%20this%20alive.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThis%20post%20dates%20from%202016%20but%20it%20is%20the%20most%20relevant%20when%20searching%20for%20%22SharePoint%20Online%20Classic%20End%20of%20Life%22.%20Has%20anything%20changed%20or%2C%20is%20there%20more%20clarity%20of%20the%20path%20moving%20forward%20as%20we%20are%20entering%202020%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20understand%20we%20should%20be%20working%20into%20moving%20to%20the%20modern%20experience%20but%20some%20things%20are%20still%20not%20there%20yet%2C%20and%20for%20some%20cases%20there%20is%20no%20path%20to%20get%20away%20from%20Classic%2C%20yet.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%2C%3C%2FP%3E%3CP%3EIgnacio%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1153792%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1153792%22%20slang%3D%22en-US%22%3E%3CP%3ENow%20that%20we%20are%20in%202020%2C%20would%20like%20to%20know%20if%20things%20have%20changed.%20Is%20there%20a%20timeline%20for%20supporting%20classic%20mode.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1153888%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1153888%22%20slang%3D%22en-US%22%3ESince%20there%20isn't%20feature%20parity%20between%20Classic%2FModern%20is%20there%20any%20reason%20why%20you%20would%20think%20Classic%20mode%20must%20be%20deprecated%3F%20Would%20like%20to%20know%20if%20you%20have%20seen%20a%20statement%20from%20Microsoft%20regarding%20deprecation.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1153923%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1153923%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F42464%22%20target%3D%22_blank%22%3E%40James%20Boman%3C%2FA%3Ewe%20still%20use%20classic%20mode%20for%20few%20sites%20and%20I%20am%20just%20wondering%20if%20it%20is%20okay%20to%20continue%20or%20it%20would%20later%20be%20a%20redo%20work.%20I%20was%20reading%20this%20article%20-%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-sharepoint-blog%2Fwhat-is-modern-sharepoint-and-why-should-i-care%2Fba-p%2F161941%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-sharepoint-blog%2Fwhat-is-modern-sharepoint-and-why-should-i-care%2Fba-p%2F161941%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%2C%20refer%20to%20the%20section%20%2310%26nbsp%3B%20%22Future%20investment%22.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1156046%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1156046%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F42464%22%20target%3D%22_blank%22%3E%40James%20Boman%3C%2FA%3E%26nbsp%3Bit's%20exactly%20because%20of%20that%20that%20we%20are%20asking%20what's%20the%20path%20moving%20forward.%20The%20push%20for%20Modern%20is%20huge%20and%20in%20my%20world%2C%20MS%20has%20a%20rep%20for%20phasing%20stuff%20out.%20The%20idea%20is%20to%20be%20able%20to%20plan%20and%20future%20proof%2C%20to%20see%20where%20the%20efforts%20and%20investments%20should%20be%20headed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20are%202%20of%20these%20profiles%20so%20just%20in%20case%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F99%22%20target%3D%22_blank%22%3E%40Chris%20McNulty%3C%2FA%3E%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%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1157571%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1157571%22%20slang%3D%22en-US%22%3EGood%20to%20ask%20for%20clarification%20-%20In%20my%20world%2C%20Project%20Online%20still%20makes%20extensive%20use%20of%20Classic%20Webpart%20Pages%2C%20and%20subwebs%20based%20on%20Classic%20templates.%20As%20far%20as%20I%20know%20we%20should%20be%20okay%20until%20at%20least%202026.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1158663%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1158663%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F42464%22%20target%3D%22_blank%22%3E%40James%20Boman%3C%2FA%3E%26nbsp%3BOn%20regards%20to%20PWA%20that's%20one%20great%20example.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20noticed%20how%20they%20haven't%20enabled%20the%20setting%20toggle%20for%20Project%20Online%20permissions%20mode%20on%20the%20Modern%20SharePoint%20Admin%20panel%3F%20I%20was%20actually%20playing%20with%20this%20earlier%20on%20the%20week.%20I%20had%20to%20go%20to%20classic%20admin%20panel%20and%20refresh%20it%20at%20least%207%20times%20to%20get%20the%20selection%20and%20toggle%20working%20(Tried%20from%203%20different%20browsers%20and%20incognito%20sessions%20in%20case%20it%20was%20outdated%20cache%20files%2C%20the%20setting%20was%20simply%20not%20popping%20out%20and%20had%20to%20tab%20my%20way%20there).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1516858%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1516858%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F867%22%20target%3D%22_blank%22%3E%40Martijn%20Eikelenboom%3C%2FA%3E%26nbsp%3BLook%20at%20what%20is%20happening%20with%20Sharepoint%202010%20workflows%20in%20Office365.%20We%20are%20having%20to%20aks%20the%20question%2C%20can%20this%20platform%20really%20be%20trusted%20to%20give%20enough%20time%20to%20prepare%20(4%20months%20for%20SP2010%20workflows%20is%20not%20enough)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1526432%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1526432%22%20slang%3D%22en-US%22%3EYeah%20-%20I%20noticed%20that%2C%201st%20November%20is%20very%20aggressive%20timeline%20for%20a%20feature%20that%20has%20been%20in%20use%20for%20such%20a%20long%20time%20-%20and%20with%20no%20real%20migration%20options%20in%20a%20lot%20of%20cases.%20(E.g.%20workflows%20inside%20site%20templates%20)%3CBR%20%2F%3EConspiracy%20theory%20is%20this%20timeline%20is%20because%20the%20grandfathering%20of%20the%20premium%20http%20connector%20ends%20in%20November%20and%20they%20don't%20want%20people%20migrating%20flows%20to%202010%20workflows.%20%3Athinking_face%3A%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1561747%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20mode%20support%20timeline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1561747%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F222%22%20target%3D%22_blank%22%3E%40Wictor%20Wilen%3C%2FA%3E%26nbsp%3BAt%20present%202020%2C%3C%2FP%3E%3CP%3EIs%20Microsoft%20have%20any%20deadline%20to%20support%20classic%20SharePoint%20site%20%3F%3C%2FP%3E%3CP%3Eor%20any%20update%20on%20support%20for%20SharePoint%20classic%20sites%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

I love the new SharePoint experiences with the new document library and the new list. It needs some work, but I can see the advantages.

 

However, a lot of companies have customized the classic experience and tailord it to their needs. A lot of the customizations are unspported in the new model, at least for now and some will stay unspported. And it's not that we knew we were doing unsupported customizations, as some of these were advised through PnP.

 

Which brings me to the question. What's the support timeline for classic mode? There have been several comments in the different networks, some by Microsoft people, that it's supported well into 2017. 

 

The new framework will most likely be released during Ignite in preview, with a final release at the end of this year. If you combine these two, the conclusion is, you have less than a year to fix all your unsupported customizations.  Which kind of scares me, and my customers. And we can't even really prepare today as a lot of the details are not know yet. Like the provisioning aspect.

 

And with that, InfoPath is supported till 2026 if you run onpremises. For Office365 this is 'until further notice'. I'm guessing that InfoPath will not work with these new experiences and thus will lose support when classic mode is not supported anymore. There has been a rumor that for Office365 support will stop a year after SharePoint 2016 is released.

 

Am I the only one that worries about Microsofts intentions to support classic mode and the lack of a timeline and communication from Microsoft?

22 Replies

Classic mode will be supported as long as there are customers using it. A recent post at Office Dev Center says that it's not going away for the "forseeable future", http://dev.office.com/blogs/update-on-modern-document-libraries-and-extensiblity. This statement should ease your mind:

"We will continue to support both of these mitigations until the modern library experience supports the same level of customization as the classic one and partners have had ample time to adapt their solutions to the new experience."

 

@Wictor Wilen thanks for the quote. There are just so many mixed communications, even from official Microsoft sources, that I would like to have a quote with a date where we can count on. And not 'ample time'.

 

They do give these timelines on most things onpremises (e.g. InfoPath) and even for a product like Dynamics CRM online you know what to expect and for how long you can postpone updates.

 

Now it's just guessing and hoping that Microsoft doesn't pull support too soon. You really get the feel from many comments that they want to stop support as soon as possible.

 

Just a few official comments on blogs.office.com and by Chris McNulty.

 

From: https://blogs.office.com/2016/06/07/modern-document-libraries-in-sharepoint/

Q. How long will classic mode be supported?

A. We recognize the need to test and prepare for any disruption to user experiences such as document libraries. We expect to run the two modes in parallel into 2017.

 

From: https://network.office.com/t5/Blogs/Modern-SharePoint-lists-are-here-Including-integration-with
"Further customization options are dependent on the release of the SharePoint Framework by year end.  In the interim, classic mode remains fully supported."

 

From: https://support.office.com/en-ie/article/Differences-between-the-new-document-library-experience-and...

"Note that we have no plans to remove classic mode."

 

And a non official quote from Marc Anderson (MVP) on the Yammer network:

"One of the things that scare people the most is that you're going to turn of "classic" fast and without warning. There hasn't bee good communication about this, and the fact that someone in an official post I can't find said something like "we'd like to turn off classic as quickly as possible" make people very wary."

best response confirmed by Martijn Eikelenboom (Contributor)
Solution

There are no plans to remove classic mode anytime soon.  For more details, see our post on modern extensibility at http://dev.office.com/blogs/update-on-modern-document-libraries-and-extensiblity   Until we roll out the framework and related patterns and practices, we havent earned the right to even talk about it.  But since you asked, any change to support would be communicated long in advance.

What is Microsoft guideline for code sharing between classic and modern sites ?

Thanks Wictor on the assurance of classic mode will supported indefinitely! Since we are now End of 2018, I hope the statement still stands!

Hi Thauja,

 

Classic mode will be supported as log as customer have them. I do not see any plans from MS  to remove .  Please have a look this  article at http://dev.office.com/blogs/update-on-modern-document-libraries-and-extensiblity  

 

Please let me know if that works

Thanks,

Thuyavan

-----------------------------------------------------------------------------------------------------

Your feedback is very valuable and your “likes” are energy boosters for us to keep blogging

 

Sure. Question was based on this article really. Since it was 2016 wondering an update on timeline.

Looks like no update on plans for end-of-support

I know the original post was made in 2016, but doesn't it just show how wrong it is to make a statement like this without the full facts.

 

You can still use the classic sites in SPO and O365 for the 2019 version and there is no real timeline for when and if they will be depreciated or even removed completely.

Infopath has been depreciated as of writing.

They are removing the tenant-level classic mode on March 29th - Its downhill from here.

https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/Delivering-SharePoint-modern-experi...

Hi @Chris McNulty 

 

This post dates from 2016 but it is the most relevant when searching for "SharePoint Online Classic End of Life". Has anything changed or, is there more clarity of the path moving forward as we are entering 2020?

 

I understand we should be working into moving to the modern experience but some things are still not there yet, and for some cases there is no path to get away from Classic, yet.

 

Thank you,

Ignacio

Hi @Chris McNulty, just to keep this alive.


This post dates from 2016 but it is the most relevant when searching for "SharePoint Online Classic End of Life". Has anything changed or, is there more clarity of the path moving forward as we are entering 2020?

 

I understand we should be working into moving to the modern experience but some things are still not there yet, and for some cases there is no path to get away from Classic, yet.

 

Thank you,

Ignacio

Now that we are in 2020, would like to know if things have changed. Is there a timeline for supporting classic mode. 

Since there isn't feature parity between Classic/Modern is there any reason why you would think Classic mode must be deprecated? Would like to know if you have seen a statement from Microsoft regarding deprecation.

@James Bomanwe still use classic mode for few sites and I am just wondering if it is okay to continue or it would later be a redo work. I was reading this article - https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/what-is-modern-sharepoint-and-why-s... 

, refer to the section #10  "Future investment". 

@James Boman it's exactly because of that that we are asking what's the path moving forward. The push for Modern is huge and in my world, MS has a rep for phasing stuff out. The idea is to be able to plan and future proof, to see where the efforts and investments should be headed.

 

There are 2 of these profiles so just in case, @Chris McNulty @Chris McNulty 

Good to ask for clarification - In my world, Project Online still makes extensive use of Classic Webpart Pages, and subwebs based on Classic templates. As far as I know we should be okay until at least 2026.

@James Boman On regards to PWA that's one great example.

 

Have you noticed how they haven't enabled the setting toggle for Project Online permissions mode on the Modern SharePoint Admin panel? I was actually playing with this earlier on the week. I had to go to classic admin panel and refresh it at least 7 times to get the selection and toggle working (Tried from 3 different browsers and incognito sessions in case it was outdated cache files, the setting was simply not popping out and had to tab my way there).

@Martijn Eikelenboom Look at what is happening with Sharepoint 2010 workflows in Office365. We are having to aks the question, can this platform really be trusted to give enough time to prepare (4 months for SP2010 workflows is not enough)

Yeah - I noticed that, 1st November is very aggressive timeline for a feature that has been in use for such a long time - and with no real migration options in a lot of cases. (E.g. workflows inside site templates )
Conspiracy theory is this timeline is because the grandfathering of the premium http connector ends in November and they don't want people migrating flows to 2010 workflows. :thinking_face: