Removing Code Based Sandbox Solutions in SharePoint Online

%3CLINGO-SUB%20id%3D%22lingo-sub-3965%22%20slang%3D%22en-US%22%3ERemoving%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3965%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20below%20was%20just%20published%20in%20our%20message%20center.%20%26nbsp%3BHow%20did%20we%20go%20from%20a%20vaguely%20worded%20blog%20post%20from%20two%20years%20ago%20(%22%3CSPAN%3EWe%20realize%20that%20our%20customers%20have%20made%20investments%20in%20coded%20sandboxed%20solutions%20and%20we%20will%20phase%20them%20out%20responsibly.%22)%20to%20(%22%3CSTRONG%3EIn%20approximately%2030%20days%2C%20currently%20running%2C%20code-based%20sandbox%20solutions%20in%20the%20SharePoint%20Online%20environment%20will%20be%20disabled%3C%2FSTRONG%3E%3CSPAN%3E.%22).%20%26nbsp%3BThat's%20a%20responsible%20way%20to%20phase%20out%20sandbox%20solutions%3F%20%26nbsp%3BWhat%20happened%20to%20the%20one%20year%20notice%20for%20disruptive%20change%3F%20Did%20I%20miss%20something%3F%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%3EHere's%20the%20full%20notice%20in%20the%20message%20center%3A%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22font-medium%20mc.fnt-fmly-sl%20f-txtalgn-jstfy%20f-pad-top-20px%20f-pad-btm-40px%20mc-msg-clr%22%3EWe%E2%80%99ve%20detected%20that%20you%20are%20using%20a%20code-based%20sandbox%20solution%20with%20your%20tenant%20account.%20Please%20be%20advised%20that%20we%E2%80%99ve%20moved%20forward%20on%20our%20plans%20to%20remove%20code-based%20sandbox%20solutions%20as%20previously%20announced%20in%202014%2C%20which%20can%20be%20seen%20here%3A%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fsandboxcode%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fsandboxcode%3C%2FA%3EPlease%20note%20that%20declarative%20(no-code)%20sandbox%20solutions%20are%20still%20fully%20supported.%3C%2FDIV%3E%3CDIV%20class%3D%22font-medium%20mc.fnt-fmly-sl%20f-txtalgn-jstfy%20f-pad-top-20px%20f-pad-btm-40px%20mc-msg-clr%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22f-pad-btm-40px%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22font-largeplus%20mc-msg-cl%20f-pad-top-5px%20f-pad-btm-20px%22%3E%3CEM%3EHow%20does%20this%20affect%20me%3F%3C%2FEM%3E%3C%2FDIV%3E%3CDIV%20class%3D%22font-medium%20mc.fnt-fmly-sl%20f-txtalgn-jstfy%20mc-msg-clr%20mc-pad-btm-10px%22%3EAs%20part%20of%20the%20removal%20process%2C%20activation%20of%20new%20code-based%20sandboxed%20solutions%2C%20as%20well%20as%20updates%20of%20existing%20solutions%20are%20no%20longer%20available.%3CSTRONG%3E%20In%20approximately%2030%20days%2C%20currently%20running%2C%20code-based%20sandbox%20solutions%20in%20the%20SharePoint%20Online%20environment%20will%20be%20disabled%3C%2FSTRONG%3E.%20If%20you%20have%20an%20extenuating%20circumstance%2C%20please%20contact%20us%20as%20our%20Product%20and%20Customer%20Support%20teams%20are%20ready%20to%20support%20you%20during%20this%20transition.%3C%2FDIV%3E%3CDIV%20class%3D%22font-medium%20mc.fnt-fmly-sl%20f-txtalgn-jstfy%20mc-msg-clr%20mc-pad-btm-10px%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22font-largeplus%20mc-msg-cl%20f-pad-top-5px%20f-pad-btm-20px%22%3E%3CEM%3EWhat%20action%20do%20I%20need%20to%20take%3F%3C%2FEM%3E%3C%2FDIV%3E%3CDIV%20class%3D%22font-medium%20mc.fnt-fmly-sl%20f-txtalgn-jstfy%20mc-msg-clr%20mc-pad-btm-10px%22%3EWe%20continue%20to%20recommend%20that%20customers%20transition%20their%20solution(s)%20to%20the%20add-in%20model%20or%20pure%20client-side%20development%2C%20which%20provide%20high-performance%2C%20cloud-first%20approaches%20to%20extending%20SharePoint.%20More%20information%20on%20SharePoint%20add-ins%20can%20be%20seen%20here%3A%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fadd-ins%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fadd-ins%3C%2FA%3EOur%20Product%20and%20Customer%20Support%20teams%20are%20ready%20to%20support%20you%20with%20guidance%20and%20additional%20assistance%20as%20needed.%20Below%20is%20a%20list%20of%20guidance%20and%20resources%20for%20solution%20development%20for%20SharePoint%20Online%3A%20-%20SharePoint%20Add-in%20Documentation%3A%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fadd-ins%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fadd-ins%3C%2FA%3E-%20Patterns%20and%20Practices%20for%20SharePoint%20Add-ins%3A%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fpatternspractices%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fpatternspractices%3C%2FA%3E-%20Plan%20customizations%2C%20solutions%2C%20and%20apps%20for%20SharePoint%20Online%3A%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fplancustom%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fplancustom%3C%2FA%3E-%20General%20SharePoint%20Development%20Documentation%3A%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2FSharePointDevelopment%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2FSharePointDevelopment%3C%2FA%3E-%20Office%20Developer%20Center%20Home%3A%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2FOfficeDevCenterHome%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2FOfficeDevCenterHome%3C%2FA%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52913%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52913%22%20slang%3D%22en-US%22%3E%3CP%3EHope%20people%20are%20given%20more%20time%2C%20certain%20migartion%20tools%20also%20make%20use%20of%20sandbox%20to%20move%20content%20to%20O365%20and%20they%20must%20be%20whitelisted%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-5281%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-5281%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20Kelly%20Jones%20for%20pushing%20for%20an%20answer%20%26nbsp%3Band%20posting%20your%20findings.%20%26nbsp%3BThis%20is%20exteremely%20disruptive%20change%20and%20MS%20should%20realise%20how%20much%20time%20and%20efforts%20it%20takes%20to%20undestand%20what%20happening%20and%20what%20to%20do.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E6%20months%20should%20be%20minimum%20(%20as%20promised%20in%20the%20past).%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-5257%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-5257%22%20slang%3D%22en-US%22%3E%3CP%3EThrough%20our%20MS%20Support%20ticket%2C%20we%20learned%20some%20more%20details%20about%20what%20will%20happen%20when%20the%20deadline%20(approximately%2030%20days%20from%20July%2029)%20hits%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20remaining%20Sandbox%20solutions%2C%20any%20server%20side%20code%20will%20stop%20working%20at%20the%20end%20of%20the%20month.%20For%20example%2C%20if%20you%20have%20a%20sandbox%20solution%20that%20uses%20event%20receivers%20to%20perform%20an%20action%20upon%20site%20creation%2C%20the%20new%20site%20will%20still%20be%20provisioned%20but%20the%20actions%20that%20would%20have%20been%20triggered%20by%20the%20event%20receiver%20will%20not%20occur.%20If%20any%20of%20the%20other%20WSPs%20are%20declarative%20%E2%80%93%20meaning%20they%20are%20wsp%20file%20but%20they%20do%20not%20use%20server%20side%20code%20%E2%80%93%20the%20wsp%20file%20can%20be%20recompiled%20without%20the%20assembly%20references%20and%20it%20will%20continue%20to%20work%3A%20%3CA%20href%3D%22https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__support.microsoft.com_en-2Dus_kb_3183084%26amp%3Bd%3DCwMFAg%26amp%3Bc%3D5MrMVID9Pd61bTJfp9wNBTxRZN_CiHJui8q3SJEDr28%26amp%3Br%3DrH_5r9pqFASPwvQ9kq1liWACr8zlp6n51XJP9I6B6Z7qBlsKWel3cAuOanDPJLfw%26amp%3Bm%3D2QP8Z4-SK3oSZgHa4tI8CuXrbCc3ouMF4Hz0I_xLy_Q%26amp%3Bs%3DX2YT6D7vbxLcVJryub4c2PjQUc3G4ywGFmKohMQiHJs%26amp%3Be%3D%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fkb%2F3183084%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-5228%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-5228%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1614%22%20target%3D%22_blank%22%3E%40Chirag%20Patel%3C%2FA%3E%26nbsp%3B!%20%26nbsp%3BThat%20tool%20sounds%20great.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EQuick%20update%20for%20those%20following%20this%20story%3A%20Working%20through%20Premier%20Support%2C%20we%20were%20able%20to%20get%20an%20extended%20deadline%20for%20our%20WSP.%20%26nbsp%3BWe%20had%20to%20send%20them%20the%20WSP%20and%20they%20%22whitelisted%22%20it%20within%20our%20tenant.%20%26nbsp%3BWe%20can%20now%20activate%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20we%20had%20another%20WSP%20that%20we%20didn't%20submit%20and%20I%20tried%20activating%20it%2C%20and%20while%20the%20activate%20button%20is%20enabled%20for%20this%20second%20WSP%20(non%20whitelisted)%2C%20I%20get%20an%20error%20when%20I%20click%20the%20activate%20button.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-5226%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-5226%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20folks%20at%20Rencore%20have%20released%20a%20free%20tool%20%22Sandbox%20Solutions%20Inspector%22%20that%26nbsp%3B%3CSPAN%3Eidentifies%20sandbox%20use%20with%20SharePoint%20Online%20tenants%26nbsp%3Band%20also%26nbsp%3Bthe%20use%20of%20active%20code%2C%20showing%20which%20site%20elements%20are%20involved.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.spcaf.com%2Fblog%2Fintroducing-sharepoint-sandboxed-solutions-inspector%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.spcaf.com%2Fblog%2Fintroducing-sharepoint-sandboxed-solutions-inspector%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehope%20this%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4995%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4995%22%20slang%3D%22en-US%22%3EThank%20you%20very%20much.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4875%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4875%22%20slang%3D%22en-US%22%3EWhat%20you%20need%20to%20learn%20is%20what%20elements%20can%20be%20provisioned%20in%20the%20Sandbox%20and%20requieres%20an%20assembly%20behind%20the%20scenes%20and%20which%20ones%20no.%20In%20the%20Sandbox%20you%20can%20provision%20the%20following%20elements%20that%20usally%20contains%20an%20assembly%3A%20Web%20Parts%2C%20Visual%20Web%20Parts%2C%20Event%20Receivers%2C%20Workflows%20(SP%202010%20ones)%2C%20InfoPath%20Forms%20with%20code%20behind.%20So%20in%20your%20case%20your%20two%20hits%20imply%20that%20you%20have%20to%20look%20for%20an%20alternative%20for%20both%20the%20WebPart%20and%20the%20InfoPath%20Forms.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4855%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4855%22%20slang%3D%22en-US%22%3E%3CP%3EI%20appreciate%20the%20link%20to%20the%20powershell%20script.%20I%20ran%20it%20and%20had%20a%20couple%20of%20hits.%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1273%22%20target%3D%22_blank%22%3E%40Kelly%20Jones%3C%2FA%3Ewhen%20you%20mentioned%20analysing%20the%20results%20to%20see%20which%20actually%20include%20managed%20code%2C%20could%20you%20help%20me%20understand%20that%26nbsp%3B%20a%20little%3F%20Our%20SPO%20site%20is%20pretty%20new%20and%20was%20handed%20over%20to%20us%20by%20a%20consultant%20and%20I'm%20still%20learning%20how%20all%20the%20pieces%20work%20together.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20have%20a%20webpart%20in%20the%20script%20that%20is%20marked%20Activated%20and%20HasAssemblies%2C%20is%20this%20is%20a%20definite%20that%20it%20is%20a%20sandboxed%20solution%20that%20needs%20to%20be%20dealt%20with%3F%20Or%20how%20do%20I%20know%20for%20sure%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20we%20had%20a%20couple%20hits%20on%20InfoPath%20forms%20that%20others%20in%20the%20company%20have%20created.%20Do%20those%20forms%20fall%20under%20sandboxed%20solutions%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20appreciate%20the%20help%20as%20I%20untangle%20this%20web.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4722%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4722%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20would%20be%20ideal%2C%20maybe%20by%20then%20some%20more%20definitive%20details%20will%20be%20out%20for%20the%20SharePoint%20Framework.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20going%20to%20have%20to%20bump%20a%20few%20things%20from%20Sandbox%20Solutions%20over%20to%20UserCustomActions%20and%20then%20will%20subsequently%20have%20to%20bump%20those%20over%20to%20the%20new%26nbsp%3BSharePoint%20Framework%20(I%20hope).%20%26nbsp%3BNot%20thrilled%20about%20rearchitecting%20stuff%20twice.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4690%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4690%22%20slang%3D%22en-US%22%3E%2B%201%20to%20this%20request%2C%20the%20November%2030%20deadline%20should%20apply%20for%20all%20SPO%20customers%20WW%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4687%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4687%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F197%22%20target%3D%22_blank%22%3E%40Adam%20Harmetz%3C%2FA%3E%26nbsp%3BAny%20chance%20that%20the%20November%2030%202016%20deadline%20can%20be%20the%20default%20deadline%20for%20all%3F%20%26nbsp%3BInstead%20of%20only%20for%20customers%20that%20push%20through%20the%20support%20process%20to%20have%20it%20manually%20extended%3F%20%26nbsp%3BThis%20would%20atleast%20be%20seen%20as%20a%20big%20step%20in%20resolving%20the%20timing%20issue%2C%20giving%20us%203%20months%20plus%20instead%20of%2030%20days%20(which%20is%20not%20practical%20at%20all).%20%26nbsp%3BSurely%20at%20this%20point%20in%20the%20aftermath%20it%20should%20be%20clear%20that%20many%20users%2Fpartners%2Fcustomers%20are%20negatively%20impacted%20by%20this%20disruptive%20change.%20%26nbsp%3BDeprecated%20solution%20debates%20aside%2C%20this%20should%20be%20the%20defacto%20way%20any%20technology%20is%20completely%20shut%20down.%20%26nbsp%3BIf%20you%20allow%20people%20to%20use%20the%20technology%20(even%20if%20they%20are%20encouraged%20not%20to)%20you%20have%20a%20responsibility%20to%20those%20users.%20%26nbsp%3BDon't%20even%20get%20me%20started%20if%20this%20were%20to%20happen%20for%20SharePoint%20Designer%2C%20InfoPath%2C%20SOAP%20Web%20Services%2C%20etc.%20%26nbsp%3BChange%20is%20great%2C%20but%20change%20must%20be%20managed.%20%26nbsp%3BMany%20companies%20(myself%20included)%20invested%20heavily%20in%20Microsoft%20SharePoint%20(and%20other%20Microsoft%20Technologies).%20%26nbsp%3BPlease%20don't%20make%20us%20regret%20our%20investment%20and%20add%20fear%20and%20uncertaintly%20to%20our%20future%20investments.%20%26nbsp%3BWe%20are%20all%20in%20the%20same%20boat%2C%20lets%20not%20forget%20that.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4405%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4405%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F197%22%20target%3D%22_blank%22%3E%40Adam%20Harmetz%3C%2FA%3E%26nbsp%3B-%20Thanks%20for%20the%20additional%20info%20and%20it's%20great%20to%20see%20Microsoft%20responding%2C%20but%20I%20really%20want%20to%20know%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1)%20Why%20was%20this%20disabled%20with%20no%20notice%3F%20(7%2F22%2F2016)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2)%20Why%20wasn't%26nbsp%3Bthis%20considered%20a%20%22disruptive%20change%22%20and%20given%20a%20firm%20one%20year%20deadline%3F%20(Like%20the%20dropping%20of%20support%20for%20IE8%2C%20IE10%2C%20etc.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E3)%20Will%20dropping%20support%20for%20InfoPath%20and%20SharePoint%20Designer%20be%20considered%20a%20disruptive%20change%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E4)%20What%20exactly%20will%20happen%20to%20deployed%20sandbox%20solutions%20with%20managed%20code%20%22in%20approximately%2030%20days%22%3F%20Will%20they%20be%20deactivated%2Funinstalled%3F%20Or%20will%20their%20managed%20code%20simply%20cease%20to%20execute%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4371%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4371%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20Adam%20from%20the%20SharePoint%20engineering%20team.%26nbsp%3B%20Thank%20you%20all%20for%20sharing%20your%20stories%20and%20comments%3B%20it%20has%20a%20real%20impact%20as%20we%20work%20with%20customers%20to%20move%20to%20a%20model%20we%20can%20carry%20forward.%26nbsp%3B%20We%20do%20hear%20loud%20and%20clear%20the%20feedback%20about%20the%20short%20notice.%20%26nbsp%3BAs%20an%20engineering%20team%2C%20we%20know%20technology%20deprecations%20are%20some%20of%20the%20toughest%20challenges%20to%20navigate%2C%20with%20customers%20being%20impacted%20in%20many%20different%20ways.%20Hearing%20from%20you%20is%20critical%20%E2%80%93%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FOfficeDev%2FPnP-Tools%2Ftree%2Fmaster%2FScripts%2FSharePoint.Sandbox.ListSolutionsFromTenant%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ethe%20content%20developed%20by%20PNP%3C%2FA%3Ereferenced%20above%20in%20the%20thread%20came%20about%20from%20early%20customer%20feedback.%26nbsp%3B%20So%20did%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fkb%2F3183084%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ethis%20article%3C%2FA%3Ethat%20talks%20about%20how%20to%20remove%20assemblies%20from%20no-code%20solutions%20created%20in%20Visual%20Studio.%26nbsp%3BWe%E2%80%99re%20rapidly%20developing%20more%20guidance%20for%20you%20and%20want%20to%20partner%20with%20you%20to%20make%20sure%20those%20who%20are%20impacted%20get%20the%20help%20they%20need.%20(And%20yes%2C%20I%20agree%2C%20Vesa%20and%20the%20PNP%20team%20are%20awesome!)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20we%E2%80%99ve%20put%20a%20process%20in%20place%20to%20work%20with%20customers%20and%20partners%20%E2%80%93%20especially%20those%20of%20you%20who%20may%20need%20more%20time%20for%20the%20transition.%20Through%20our%20support%20channels%2C%20we%E2%80%99ll%20work%20with%20you%20to%20understand%20your%20existing%20solutions%2C%20so%20we%20can%20help%20ensure%20they%26nbsp%3Bwill%20function%2C%20uninterrupted%2C%20during%20the%20transition.%20This%20support-led%20process%20can%20extend%20the%20time%20your%20solutions%20can%20run%20from%20August%2031%2C%202016%20to%20November%2030%2C%202016.%26nbsp%3B%20I%20see%20some%20people%20on%20this%20thread%20who%20didn%E2%80%99t%20receive%20the%20level%20of%20support%20they%20expected%20from%20us.%20And%2C%20we%20took%20that%20feedback%20and%20are%20making%20sure%20all%20parts%20of%20the%20team%20are%20well%20aware%20of%20the%20process%20and%20the%20impact%20to%20you.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20do%20contact%20support%20if%20you%20need%20help%20through%20the%20transition.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EAdam%20Harmetz%3C%2FP%3E%3CP%3EGroup%20Program%20Manager%2C%20SharePoint%20Experiences%20and%20Developer%20Platform%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4366%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4366%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20adding%20my%20voice%20to%20this%20thread%20and%20the%20ridiculous%20situation%20Microsoft%20has%20put%20us%20all%20in%2C%20their%20loyal%20customers%20and%20partners!%20I%26nbsp%3Bhave%20a%20commercial%20sandbox%20solution%20that%20contains%20remote%20event%20handlers%2C%20I%20dont%20think%20the%20in-app%20model%20will%20work%20for%20this%2C%20and%20I'm%20thinking%20of%20porting%20my%20code%20to%20work%20with%20Azure%20for%20hosting.%20But%20I%20can't%20get%20any%20help%20from%20anyone%20at%20Microsoft%20on%20this.%20I've%20contacted%20support%20repeatedly%20just%20to%20get%20the%20'Standard%20list'%20of%20documents%20and%20how-to's%2C%20none%20of%20which%20actually%20provides%20any%20relevant%20insight.%20And%26nbsp%3Bto%20top%20this%20off%20-%20I%20have%20less%20than%2030%20days%20to%20architect%2C%20code%2C%20test%20and%20deploy%20this%20fairly-major%26nbsp%3Bredesign!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%2C%20how%20can%20you%20pass%20this%20off%20as%20an%20enterprise%20solution%3F%20Is%20this%20how%20you%20hope%20to%20get%20developers%20engaged%20in%20your%20ecosystem%2C%20building%20and%20offering%20solutions%3F%3C%2FP%3E%3CP%3ECopying%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F209%22%20target%3D%22_blank%22%3E%40Brian%20Levenson%3C%2FA%3E%2C%20since%20he's%20the%20only%20one%20who%20seems%20to%20be%20responding%20and%2For%20caring%20about%20customers...%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4274%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4274%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Message%20Center%20is%20a%20component%20of%20the%20O365%20Admin%20portal%20where%20messages%20are%20sent%20to%20your%20O365%20tenant%20about%20upcoming%20changes%2C%20alerts%2C%20or%20items%20such%20as%20this%20one%20where%20you%20have%20an%20issue%20that%20needs%20to%20be%20fixed%20by%20a%20certain%20date.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4273%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4273%22%20slang%3D%22en-US%22%3EBrian%20Levenson%2C%20at%20the%20risk%20of%20sounding%20uninformed%2C%20what%20is%20this%20message%20center%20of%20which%20you%20speak%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4260%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4260%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20having%20a%20script%20to%20inventory%20the%20sandbox%20solutions%20is%20helpful.%26nbsp%3B%20We%20were%20already%20closely%20monitoring%20that%2C%20but%20this%20will%20let%20us%20confirm%20that%20we%20didn't%20miss%20any.%26nbsp%3B%20We'll%20still%20need%20to%20analyse%20each%20one%20to%20determine%20if%20it%20includes%20managed%20code%20or%20not.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4257%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4257%22%20slang%3D%22en-US%22%3EI%20do%20wonder%20if%20the%20abrupt%20change%20has%20anything%20to%20do%20with%20the%20recent%20sandbox%20vulnerability.%20I%20can't%20reason%20this%20type%20of%20change%20in%20any%20other%20way%20that%20makes%20sense.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4254%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4254%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EThe%20Office%20Dev%20PnP%20group%20has%20just%20posted%20a%20PS%20script%20to%20identify%20sandbox%20solutions...%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20title%3D%22Generate%20list%20of%20sandbox%20solutions%20from%20SPO%20tenant%22%20href%3D%22https%3A%2F%2Fgithub.com%2FOfficeDev%2FPnP-Tools%2Ftree%2Fmaster%2FScripts%2FSharePoint.Sandbox.ListSolutionsFromTenant%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EGenerate%20list%20of%20sandbox%20solutions%20from%20SPO%20tenant%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20%40VesaJuvonen%20and%20the%20rest%20of%20the%20PnP%20group!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E(I'm%20still%20not%20happy%20with%20the%20abrupt%20change%20byt%20Microsoft%2C%20but%20at%20least%20the%20PnP%20group%20is%20responsive%20to%20helping%20us%20deal%20with%20it)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4253%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4253%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20been%20working%20extensively%20with%20my%20local%20Microsoft%20team%20and%20the%20further%20we%20get%20into%20this%2C%20it%20is%20shocking%20how%20absolutely%20unprepared%20Microsoft%20was%20for%20this.%26nbsp%3B%20Not%20only%20did%20the%20team%20implementing%20this%20change%20not%20communicate%20with%20customers%2C%20but%20they%20apparently%20didn't%20communicate%20with%20anyone%20inside%20Microsoft%20either.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20longer%20this%20goes%20without%20a%20public%20acknowledgement%20that%20this%20was%20horribly%20executed%20and%20will%20be%20post%20poned%20until%20a%20future%20date%2C%20the%20more%20concerned%20I'll%20be%20about%20relying%20on%20Office%20365%20for%20critical%20busines%20applications.%26nbsp%3B%20The%2030%20day%20time%20bomb%20is%20ticking.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4204%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4204%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20looping%20me%20in!%26nbsp%3B%20I%20have%20been%20following%20this%20discussion%20and%20topic%20but%20haven't%20chimed%20in%20because%20I%20don't%20have%20much%20to%20contribute%20yet.%26nbsp%3B%20I%20am%20seeking%20a%20formal%20response%20to%20share%2C%20and%20I'd%20encourage%20everyone%20to%20submit%20feedback%20within%20the%20Message%20Center.%26nbsp%3B%20Using%20the%20like%20-%20or%20in%20this%20case%2C%20dislike%20-%20button%20and%20including%20comments%20routes%20your%20feedback%20directly%20to%20the%20product%20team%20and%20communication%20submitter.%26nbsp%3B%20This%20is%20the%20best%20way%20to%20communicate%20to%20the%20owner.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4202%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4202%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20affecting%20us%20now%2C%20we've%20put%20a%20holt%20on%20any%20new%20sites%20to%20be%20migrated%20as%20the%20sandbox%20solution%20relied%20upon%20to%20ensure%20all%20metadata%20is%20migrated%20can't%20be%20activated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReally%20hoping%20Microsoft%20allow%20a%20whitelisting%20to%20allow%20us%20to%20continue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4198%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4198%22%20slang%3D%22en-US%22%3E%3CP%3EBrian%20does%20seem%20very%20quite%20on%20this%20new%20Change%20Management%20strategy%20they%20are%20going%20with...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4164%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4164%22%20slang%3D%22en-US%22%3E%3CP%3EThats%20the%20real%20crux%20of%20the%20matter.%20%26nbsp%3BI%20share%20the%20same%20concern%20regarding%20UserCustomActons%2FScriptLinks%20now%20(didnt%20before).%20%26nbsp%3BI%20know%20they%20are%20going%20away%20in%20modern%20SharePoint%2C%20but%20are%20they%20just%20all%20gonna%20up%20and%20stop%20working%20one%20day%3F%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEpic%20change%20management%20fail%3A%20CC%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F209%22%20target%3D%22_blank%22%3E%40Brian%20Levenson%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4153%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4153%22%20slang%3D%22en-US%22%3E%3CP%3EWell%20no%2C%20they'd%20never%20do%20anything%20like%20that....%20wait%2C%20Infopath%20is%20gone%20now%20too%3F%20%26nbsp%3BUh%20oh.............%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20Microsoft's%20defense%20(only%20sort%20of)%2C%20they%20did%20push%20everyone%20towards%20the%20app%20model%20and%20have%20said%20that%20sandbox%20solutions%20have%20been%20deprecated%20for%20a%20while%20now.%20%26nbsp%3BThat%20said%2C%20to%20pull%20the%20plug%20this%20suddenly%20is%20just%20craziness.%20%26nbsp%3BSandbox%20solutions%20were%20the%20gateway%20to%20filling%20quite%20a%20few%20gaps%20in%20Sharepoint.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4146%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4146%22%20slang%3D%22en-US%22%3EThis%20really%20has%20me%20worried%20for%20those%20other%20deprecated%20technologies%3A%20InfoPath%2C%20SharePoint%20Designer%20(workflows!)%2C%20SOAP%20web%20services%2C%20etc.%3CBR%20%2F%3E%3CBR%20%2F%3EWill%20the%20ability%20to%20create%20new%20InfoPath%20forms%20suddenly%20disappear%20and%20then%20a%20message%20be%20published%20a%20weekly%20stating%20that%20InfoPath%20is%20dead%20in%2030%20days%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4135%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4135%22%20slang%3D%22en-US%22%3EI%20too%20am%20impacted%2C%20having%20many%20Sandbox%20Solutions%20with%20Code%20sold%20to%20clients%20over%20the%20years%20and%20recently%20that%20are%20heavily%20used.%20This%20isn't%20just%20going%20to%20affect%20my%20profits%20from%20selling%20existing%20products%20(web%20parts)%20but%20what%20do%20the%20SharePoint%20users%20do%20when%20the%20product%20they%20purchased%20and%20loaded%20all%20throughout%20their%20farms%2C%20site%20collections%2C%20sites%2C%20etc%20suddenly%20stop%20working.%20They%20are%20using%20these%20types%20of%20web%20parts%20for%20navigation%20and%20other%20critical%20purposes%20in%20their%20sites.%20Its%20crazy%20that%2030%20days%20or%20less%20is%20viewed%20as%20a%20%22responsible%22%20amount%20of%20time%20for%20clients%20to%20develop%20an%20alternative%20solution!%20Add-Ins%2C%20client%20side%20only%20components%2C%20etc%20are%20not%20practical%20to%20be%20built%20and%20tested%20in%20less%20than%2030%20days%20and%20distributed%20to%20all%20impacted%20users%2C%20in%20August%20of%20all%20times%2C%20with%20no%20advanced%20warning%20of%20the%20shutdown!%20We%20know%20they%20are%20%22deprecated%22%2C%20but%20that's%20not%20the%20point.%20SOAP%20Web%20Services%20are%20deprecated%20for%20even%20longer%20and%20they%20are%20still%20critical%20to%20SharePoint%2C%20SP%20Designer%2C%20etc.%20Shutting%20down%20Sandbox%20Code%20solutions%20in%20such%20a%20short%20time%20span%20is%20a%20huge%20error%20and%20shows%20poor%20planning%20and%20judgement.%20And%20its%20another%20reason%20to%20suspect%20any%20solution%20strategy%20can%20go%20the%20way%20of%20the%20Dodo%2C%20thus%20negating%20years%20of%20investment%20and%20impacting%20live%20MS%20users.%20This%20decision%20would%20only%20drive%20users%20away%20from%20Microsoft%20and%20SharePoint.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4131%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4131%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EI%20also%20think%20that%20ISV's%20should%20get%20the%20chance%20to%20migrate%20the%20sandboxed%20solutions%20to%20the%20forthcoming%20SharePoint%20Framework%20(keeping%20the%20Sandbox%20alive%20until%20then)%20instead%20of%20having%20to%20create%20Add-in's%20in%20a%20hurry%20and%20then%20a%20few%20weeks%20later%20migrate%20the%20Add-in's%20to%20the%20new%20Framework.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4126%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4126%22%20slang%3D%22en-US%22%3EMy%20memory%20is%20not%20what%20it%20once%20was%2C%20well%2C%20really%20it%20was%20never%20very%20good%2C%20however%20two%20months%20ago%20Microsoft%20did%20a%20big%20presentation%20on%20the%20future%20of%20SharePoint%20and%20they%20announced%20many%20things%20giving%20them%20a%20Q2%20or%202H2016%20timeframe.%20I%20do%20not%20recall%20final%20deprecation%20of%20Sandbox%20coded%20solutions%20on%20there.%20That%20would%20have%20been%20appropriate%20timing%20and%20gotten%20to%20the%20audience%20that%20needed%20to%20know.%3CBR%20%2F%3E%3CBR%20%2F%3EOr%20maybe%20I%20just%20forgot%20they%20said%20it...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4122%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4122%22%20slang%3D%22en-US%22%3EI've%20stood%20by%20Microsoft%20on%20many%20occasions%20and%20even%20applauded%20their%20recent%20fast%20paced%20rolloutso%20often%2C%20but%20this%20one%20is%20very%20rough%20and%20hard%20to%20swallow.%20Sandbox%20solutions%20were%20the%20lifeblood%20for%20many%20workarounds%20to%20functionality%20that%20made%20sharepoint%20be%20able%20to%20do%20anything.%20Months%20of%20testing%2C%20development%20and%20more%20were%20put%20into%20filling%20in%20the%20cracks%20and%20now%20it's%20a%20madifferent%20rush%20to%20redo%20it%20and%20hope%20the%20functionality%20that%20was%20stripped%20away%20is%20still%20achievable%20in%20a%20very%20short%20time%20frame.%20Better%20communication%20Microsoft.....%20come%20on%20now.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4120%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4120%22%20slang%3D%22en-US%22%3EUnfortunately%2C%20some%20of%20us%20weren't%20using%20SharePoint%202%20years%20ago%20and%20even%20contracted%20a%203rd%20party%20vendor%20for%20a%20solution%20in%20our%20SP%20that%20just%20released%20in%20a%20few%20site%20collections%20and%20is%20now%20disabled%20for%20us%20to%20continue%20releasing%20to%20the%20other%20site%20collections%20AND%20figure%20out%20how%20we're%20supposed%20to%20fix%20this.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4115%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4115%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20change%20probably%20was%20a%20very%20rude%20awakening%20for%20most%20of%20the%20organizations%2C%20and%20I%20find%2030-day%20eviction%20notice%20very%20short.%20Now%20we%20can't%20even%20activate%20new%20solutions%2C%20so%20it%20has%20been%20practically%20half%20turned%20off%20already.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'd%20have%20expected%20at%20least%20a%26nbsp%3BT-90%20day%20annoucement%20to%20communicate%20turn%20off%20plans%20detailing%20timeline.%20T-60%20to%20stop%20activating%20new%20solutions%2C%26nbsp%3BT-30%20day%20reminder%20that%20it%20will%20be%20all%20gone.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4095%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4095%22%20slang%3D%22en-US%22%3EYeap...and%20this%20could%20also%20affect%20to%20the%20ones%20migrating%20from%20OnPremises%20to%20SPO%20using%20Sharegate%20since%20in%20some%20scenarios%20it's%20required%20to%20use%20a%20Sandbox%20solution%20provided%20by%20Sharegate%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4091%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4091%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20it%20is%20a%20to%20quick%20move%20i%20only%20have%20a%20few%20customers%20who%20still%20have%20Sandboxes%20and%203%20are%20busy%20with%20upgrading%20the%20box%20to%20PNP%20or%20other%20solutions.%20But%20timeing%20is%20a%20bit%20strange.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4070%22%20slang%3D%22en-US%22%3ERE%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4070%22%20slang%3D%22en-US%22%3EAgain%2C%20to%20me%20we%20are%20under%20a%20situation%20not%20well%20communicated...we%20all%20knew%20that%20Sanbox%20coded%20solutions%20were%20deprecated%202%20years%20ago%20and%20also%20that%20this%20moment%20would%20come...but%20I%20also%20would%20expect%20a%20reasonable%20time%20window%20so%20customers%20and%20partners%20can%20be%20ready%20for%20this%20change.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4029%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4029%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3E%22If%20you%20have%20an%20extenuating%20circumstance%2C%20please%20contact%20us%20as%20our%20Product%20and%20Customer%20Support%20teams%20are%20ready%20to%20support%20you%20during%20this%20transition.%22%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EDon't%20bother%2C%20I%20already%20did!%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EAfter%20having%20first%20level%20support%20simply%20feed%20me%20the%20same%20reply%2010x%20like%20a%20broken%20record%2C%20I%20finally%20got%20to%20speak%20to%20a%20manager%20who%20(par%20for%20the%20course)%20had%20nothing%20useful%20to%20say.%3C%2FP%3E%3CP%3EThe%20%22extenuating%20circumstance%22%20that%20they%20are%20referring%20to%20apparently%20is%20only%20for%20users%20who%20have%20a%20managed%20code%20sandbox%20solution%20that%20is%20already%20disabled%20-%20which%20should%20just%20be%20an%20issue%20considering%20they're%20supposed%20to%20have%20until%20Aug%2028.%20Customers%20with%20this%20issue%20will%20have%20to%20fill%20out%20a%20questionnaire%20on%20why%20they%20need%20this%20restored%20before%20Microsoft%20chooses%20whether%20or%20not%20to%20do%20so.%20IS%20THIS%20NOT%26nbsp%3BMORE%20WORK%20FOR%20MICROSOFT%20THAN%20JUST%20EXTENDING%20THE%20AVAILABILITY%20WITH%20FORMAL%20NOTICE%3F!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIronic%20that%20the%20linked%20article%20starts%20out%20with%2C%20%22Our%20bad%22!%20Yeah%20Microsoft%2C%20your%20bad%20-%20%3CSTRONG%3E*you're*%3C%2FSTRONG%3Ebad!%3C%2FP%3E%3CP%3E%3CU%3EYou're%20bad%3C%2FU%3Eat%20planning!%3C%2FP%3E%3CP%3E%3CU%3EYou're%20bad%3C%2FU%3Eat%20communicating!%3C%2FP%3E%3CP%3E%3CU%3EYou're%20bad%3C%2FU%3E%26nbsp%3Bat%20understanding%20your%20customers!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20insulting%20to%20customers%20that%20Microsoft%20would%20stop%20functionality%20on%2030%20days%20notice%2C%20and%20it%20is%20extremely%20insulting%20to%20partners%20that%20Microsoft%20would%20not%20communicate%20a%20time%20frame%26nbsp%3Bfor%20when%20they%20are%20going%20to%20chop%20an%20entire%20development%20platform.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20fact%20that%20they%20use%20that%20linked%20article%20would%20be%20laughable%20except%20it%20isn't%20funny%20-%20it%20literally%20hurts%20their%20partners%20business!%20That%20article%3A%26nbsp%3B%3C%2FP%3E%3CP%3Ea.%20Starts%20with%2C%20%22Our%20bad.%22%20%26lt%3B-%20%3F%3F%3F%20Seriously%3F!%20Don't%20try%20to%20be%20hip%20Microsoft!%20We%20deserve%20a%20real%20apology%2C%20not%20some%20teeny-bopper%20text%20quip!%3C%2FP%3E%3CP%3Eb.%20Gives%20NO%20TIMELINE!%20Congratulations%20Microsoft%20-%20you%20told%20people%20that%20one%20day%20you're%20going%20to%20do%20something%20that%20is%20going%20to%20make%20people%20really%20mad%20(in%20fact%20it%20already%20had)%2C%20but%20you%20achieved%20EPIC%20FAIL%20status%20when%20you%20never%20gave%20people%20a%20date%20until%20you%20accidentally%20did%20it%20two%20years%20later.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGlad%20to%20know%20that%20partners%20get%20no%20better%20support%20than%20an%2011%20year%20old%20calling%20for%20Xbox%20support!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4021%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4021%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20totally%20irresponsible%20on%20the%20part%20of%20the%20product%20team.%26nbsp%3B%20This%20will%20impact%201000s%20of%20SharePoint%20Online%20customers.%26nbsp%3B%20We%20at%20SP%20Marketplace%20have%20moved%20away%20from%20code%20based%20sandbox%20solutions%20over%20the%20last%2018%20months%2C%20but%20many%20of%20our%20over%20700%2B%20Office%20365%20SharePoint%20Online%20business%20application%26nbsp%3Bcustomers%20still%20run%20older%20versions%20of%20our%20products%20or%20have%20added%20the%20many%20available%20third%20party%20web%20parts%20in%20their%20overall%20business%20solutions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20no%20issue%20with%20the%20change%20given%20sufficient%20notice%2C%20but%20it%20is%20%3CU%3Eapparent%20the%20product%20team%20is%20really%20out%20of%20touch%26nbsp%3B%20with%20how%20customers%20are%20using%20SharePoint%20Online%3C%2FU%3E.%26nbsp%3B%20WE%20NEED%20AT%20LEAST%20SIX%20MONTHS%20FOLKS!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4016%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4016%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20had%20this%20issue%20for%20over%20a%20week.%20It%20was%20reported%20in%20the%20Message%20Center%20as%20an%20outage%20until%20Friday%2C%20then%20it%20was%20changed.%26nbsp%3B%20It%20looks%20like%20%3CSTRONG%3Ethey%20removed%20the%20ability%20to%20activate%20code%20based%20sandbox%20solutions%20on%207%2F22%2F2016%3C%2FSTRONG%3E.%26nbsp%3B%20Whoever%20flipped%20that%20switch%20didn't%20tell%20anyone%20(apparently)%20because%20the%20issue%20showed%20up%20in%20the%20message%20center.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20updated%20it%20on%20Friday%20as%20%22service%20restored%22%20which%20is%20laughable%20since%20they%20literally%20didn't%20restore%20anything.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere's%20the%20notice%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3EService%20restored%20-%20Jul%2029%2C%202016%205%3A54%20PM%3C%2FDIV%3E%3CP%3E%3CBR%20%2F%3E%3C!--%20%20%20ngRepeat%3A%20line%20in%20history.MessageLines%20%20%20--%3E%3C%2FP%3E%3CDIV%3E%3C!--%20%20%20ngIf%3A%20%24index%20!%3D%200%20%20%20--%3EFinal%20Status%3A%20After%20further%20review%2C%20this%20incident%20has%20been%20correlated%20to%20deprecated%20code-based%20Sandbox%20solutions.%20Detailed%20guidance%20on%20available%20options%20can%20be%20found%20in%20Message%20Center%20post%20MC73347.%3C%2FDIV%3E%3CP%3E%3C!--%20%20%20end%20ngRepeat%3A%20line%20in%20history.MessageLines%20%20%20--%3E%3C%2FP%3E%3CDIV%3E%3C!--%20%20%20ngIf%3A%20%24index%20!%3D%200%20%20%20--%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C!--%20%20%20end%20ngIf%3A%20%24index%20!%3D%200%20%20%20--%3E%3C%2FDIV%3E%3CP%3E%3C!--%20%20%20end%20ngRepeat%3A%20line%20in%20history.MessageLines%20%20%20--%3E%3C%2FP%3E%3CDIV%3E%3C!--%20%20%20ngIf%3A%20%24index%20!%3D%200%20%20%20--%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C!--%20%20%20end%20ngIf%3A%20%24index%20!%3D%200%20%20%20--%3EUser%20Impact%3A%3CSTRONG%3EUsers%20may%20be%20unable%20to%20activate%20or%20use%20SharePoint%20Online%20Sandbox%20Solutions%3C%2FSTRONG%3E.%20This%20may%20include%20event%20receivers%2C%20workflows%2C%20web%20parts%2C%20feature%20receivers%2C%20and%20InfoPath%20forms.%3C%2FDIV%3E%3CP%3E%3C!--%20%20%20end%20ngRepeat%3A%20line%20in%20history.MessageLines%20%20%20--%3E%3C%2FP%3E%3CDIV%3E%3C!--%20%20%20ngIf%3A%20%24index%20!%3D%200%20%20%20--%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C!--%20%20%20end%20ngIf%3A%20%24index%20!%3D%200%20%20%20--%3EScope%20of%20Impact%3A%20Your%20organization%20is%20affected%20by%20this%20event.%3C%2FDIV%3E%3CP%3E%3C!--%20%20%20end%20ngRepeat%3A%20line%20in%20history.MessageLines%20%20%20--%3E%3C%2FP%3E%3CDIV%3E%3C!--%20%20%20ngIf%3A%20%24index%20!%3D%200%20%20%20--%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C!--%20%20%20end%20ngIf%3A%20%24index%20!%3D%200%20%20%20--%3EThis%20is%20the%20final%20update%20for%20the%20event.%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4012%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4012%22%20slang%3D%22en-US%22%3EOne%20of%20our%20admins%20removed%20a%20solution%20over%20the%20weekend%20trying%20to%20troubleshoot%20it.%20To%20his%20shock%20he%20can%20no%20longer%20add%20it%20again.%20So%20basically%20we%20just%20lose%20that%20app%20now%20and%20all%20its%20functionality.%20Not%20good.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3986%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3986%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20they%20could%20have%20said%20in%20January%20of%202016%20that%20Sandbox%20Solutions%20with%20Managed%20Code%20will%20be%20disabled%20come%20December%2031%2C%20then%20I%20would%20have%20no%20issue.%26nbsp%3B%20However%2C%20getting%20this%20message%20now%20means%20I%20have%20to%20scramble%20to%20identify%20and%20remediate%20these%20solutions%20in%2030%20days.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3970%22%20slang%3D%22en-US%22%3ERe%3A%20Removing%20Code%20Based%20Sandbox%20Solutions%20in%20SharePoint%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3970%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20the%20timing%20should%20at%20a%20minimum%20wait%20until%20the%20SharePoint%20Framework%20is%20fully%20rolled%20out%20and%20available%2C%20and%20enough%20people%20have%20been%20given%20the%20opportunity%20to%20transition%20their%20stuff%20into%20THAT%20framework.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

The below was just published in our message center.  How did we go from a vaguely worded blog post from two years ago ("We realize that our customers have made investments in coded sandboxed solutions and we will phase them out responsibly.") to ("In approximately 30 days, currently running, code-based sandbox solutions in the SharePoint Online environment will be disabled.").  That's a responsible way to phase out sandbox solutions?  What happened to the one year notice for disruptive change? Did I miss something?

 

Here's the full notice in the message center:

 

We’ve detected that you are using a code-based sandbox solution with your tenant account. Please be advised that we’ve moved forward on our plans to remove code-based sandbox solutions as previously announced in 2014, which can be seen here: http://aka.ms/sandboxcode Please note that declarative (no-code) sandbox solutions are still fully supported.
 
How does this affect me?
As part of the removal process, activation of new code-based sandboxed solutions, as well as updates of existing solutions are no longer available. In approximately 30 days, currently running, code-based sandbox solutions in the SharePoint Online environment will be disabled. If you have an extenuating circumstance, please contact us as our Product and Customer Support teams are ready to support you during this transition.
 
What action do I need to take?
We continue to recommend that customers transition their solution(s) to the add-in model or pure client-side development, which provide high-performance, cloud-first approaches to extending SharePoint. More information on SharePoint add-ins can be seen here: http://aka.ms/add-ins Our Product and Customer Support teams are ready to support you with guidance and additional assistance as needed. Below is a list of guidance and resources for solution development for SharePoint Online: - SharePoint Add-in Documentation: http://aka.ms/add-ins - Patterns and Practices for SharePoint Add-ins: http://aka.ms/patternspractices - Plan customizations, solutions, and apps for SharePoint Online: http://aka.ms/plancustom - General SharePoint Development Documentation: http://aka.ms/SharePointDevelopment - Office Developer Center Home: http://aka.ms/OfficeDevCenterHome
41 Replies
Highlighted

I think the timing should at a minimum wait until the SharePoint Framework is fully rolled out and available, and enough people have been given the opportunity to transition their stuff into THAT framework.

Highlighted

If they could have said in January of 2016 that Sandbox Solutions with Managed Code will be disabled come December 31, then I would have no issue.  However, getting this message now means I have to scramble to identify and remediate these solutions in 30 days.

Highlighted
One of our admins removed a solution over the weekend trying to troubleshoot it. To his shock he can no longer add it again. So basically we just lose that app now and all its functionality. Not good.
Highlighted

We've had this issue for over a week. It was reported in the Message Center as an outage until Friday, then it was changed.  It looks like they removed the ability to activate code based sandbox solutions on 7/22/2016.  Whoever flipped that switch didn't tell anyone (apparently) because the issue showed up in the message center.

 

They updated it on Friday as "service restored" which is laughable since they literally didn't restore anything.

 

Here's the notice:

 

Service restored - Jul 29, 2016 5:54 PM


Final Status: After further review, this incident has been correlated to deprecated code-based Sandbox solutions. Detailed guidance on available options can be found in Message Center post MC73347.

 

 
User Impact: Users may be unable to activate or use SharePoint Online Sandbox Solutions. This may include event receivers, workflows, web parts, feature receivers, and InfoPath forms.

 
Scope of Impact: Your organization is affected by this event.

 
This is the final update for the event.
Highlighted

This is totally irresponsible on the part of the product team.  This will impact 1000s of SharePoint Online customers.  We at SP Marketplace have moved away from code based sandbox solutions over the last 18 months, but many of our over 700+ Office 365 SharePoint Online business application customers still run older versions of our products or have added the many available third party web parts in their overall business solutions.

 

I have no issue with the change given sufficient notice, but it is apparent the product team is really out of touch  with how customers are using SharePoint Online.  WE NEED AT LEAST SIX MONTHS FOLKS!

Highlighted

"If you have an extenuating circumstance, please contact us as our Product and Customer Support teams are ready to support you during this transition."

 

Don't bother, I already did!

After having first level support simply feed me the same reply 10x like a broken record, I finally got to speak to a manager who (par for the course) had nothing useful to say.

The "extenuating circumstance" that they are referring to apparently is only for users who have a managed code sandbox solution that is already disabled - which should just be an issue considering they're supposed to have until Aug 28. Customers with this issue will have to fill out a questionnaire on why they need this restored before Microsoft chooses whether or not to do so. IS THIS NOT MORE WORK FOR MICROSOFT THAN JUST EXTENDING THE AVAILABILITY WITH FORMAL NOTICE?!

 

Ironic that the linked article starts out with, "Our bad"! Yeah Microsoft, your bad - *you're* bad!

You're bad at planning!

You're bad at communicating!

You're bad at understanding your customers!

 

It is insulting to customers that Microsoft would stop functionality on 30 days notice, and it is extremely insulting to partners that Microsoft would not communicate a time frame for when they are going to chop an entire development platform. 

 

The fact that they use that linked article would be laughable except it isn't funny - it literally hurts their partners business! That article: 

a. Starts with, "Our bad." <- ??? Seriously?! Don't try to be hip Microsoft! We deserve a real apology, not some teeny-bopper text quip!

b. Gives NO TIMELINE! Congratulations Microsoft - you told people that one day you're going to do something that is going to make people really mad (in fact it already had), but you achieved EPIC FAIL status when you never gave people a date until you accidentally did it two years later. 

 

Glad to know that partners get no better support than an 11 year old calling for Xbox support!

Highlighted
Again, to me we are under a situation not well communicated...we all knew that Sanbox coded solutions were deprecated 2 years ago and also that this moment would come...but I also would expect a reasonable time window so customers and partners can be ready for this change.
Highlighted

I think it is a to quick move i only have a few customers who still have Sandboxes and 3 are busy with upgrading the box to PNP or other solutions. But timeing is a bit strange.

Highlighted
Yeap...and this could also affect to the ones migrating from OnPremises to SPO using Sharegate since in some scenarios it's required to use a Sandbox solution provided by Sharegate
Highlighted

This change probably was a very rude awakening for most of the organizations, and I find 30-day eviction notice very short. Now we can't even activate new solutions, so it has been practically half turned off already.

 

I'd have expected at least a T-90 day annoucement to communicate turn off plans detailing timeline. T-60 to stop activating new solutions, T-30 day reminder that it will be all gone.

Unfortunately, some of us weren't using SharePoint 2 years ago and even contracted a 3rd party vendor for a solution in our SP that just released in a few site collections and is now disabled for us to continue releasing to the other site collections AND figure out how we're supposed to fix this.
Highlighted
I've stood by Microsoft on many occasions and even applauded their recent fast paced rolloutso often, but this one is very rough and hard to swallow. Sandbox solutions were the lifeblood for many workarounds to functionality that made sharepoint be able to do anything. Months of testing, development and more were put into filling in the cracks and now it's a madifferent rush to redo it and hope the functionality that was stripped away is still achievable in a very short time frame. Better communication Microsoft..... come on now.
Highlighted
My memory is not what it once was, well, really it was never very good, however two months ago Microsoft did a big presentation on the future of SharePoint and they announced many things giving them a Q2 or 2H2016 timeframe. I do not recall final deprecation of Sandbox coded solutions on there. That would have been appropriate timing and gotten to the audience that needed to know.

Or maybe I just forgot they said it...
Highlighted

I also think that ISV's should get the chance to migrate the sandboxed solutions to the forthcoming SharePoint Framework (keeping the Sandbox alive until then) instead of having to create Add-in's in a hurry and then a few weeks later migrate the Add-in's to the new Framework.

Highlighted
I too am impacted, having many Sandbox Solutions with Code sold to clients over the years and recently that are heavily used. This isn't just going to affect my profits from selling existing products (web parts) but what do the SharePoint users do when the product they purchased and loaded all throughout their farms, site collections, sites, etc suddenly stop working. They are using these types of web parts for navigation and other critical purposes in their sites. Its crazy that 30 days or less is viewed as a "responsible" amount of time for clients to develop an alternative solution! Add-Ins, client side only components, etc are not practical to be built and tested in less than 30 days and distributed to all impacted users, in August of all times, with no advanced warning of the shutdown! We know they are "deprecated", but that's not the point. SOAP Web Services are deprecated for even longer and they are still critical to SharePoint, SP Designer, etc. Shutting down Sandbox Code solutions in such a short time span is a huge error and shows poor planning and judgement. And its another reason to suspect any solution strategy can go the way of the Dodo, thus negating years of investment and impacting live MS users. This decision would only drive users away from Microsoft and SharePoint.
Highlighted
This really has me worried for those other deprecated technologies: InfoPath, SharePoint Designer (workflows!), SOAP web services, etc.

Will the ability to create new InfoPath forms suddenly disappear and then a message be published a weekly stating that InfoPath is dead in 30 days?
Highlighted

Well no, they'd never do anything like that.... wait, Infopath is gone now too?  Uh oh.............

 

In Microsoft's defense (only sort of), they did push everyone towards the app model and have said that sandbox solutions have been deprecated for a while now.  That said, to pull the plug this suddenly is just craziness.  Sandbox solutions were the gateway to filling quite a few gaps in Sharepoint.

Highlighted

Thats the real crux of the matter.  I share the same concern regarding UserCustomActons/ScriptLinks now (didnt before).  I know they are going away in modern SharePoint, but are they just all gonna up and stop working one day?  

 

Epic change management fail: CC @Brian Levenson

Highlighted

Brian does seem very quite on this new Change Management strategy they are going with...