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.
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.
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.
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.
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 sandbox 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?
A recent post from #Microsoft in the office dev center shows that clearly, we are not the only ones who are a little surprised/annoyed at Microsoft. See normally you have the option of migrating when you want to. But under the new rapid deployment and in place feature enhancements Microsoft has implemented with the onset of the cloud and Office 365. If you’re fully invested in the Office 365 boat, you don’t have a choice but to face the situation now because Microsoft is forcing the issue. I understand their side of the story as well. I understand that they are trying to innovate, fix security issues, and stabilize the platform for the greater good of the ecosystem. But, it’s definitely something to consider before migrating to the cloud as I am sure other issues such as this will arise as time goes on and Office 365 and Microsoft’s’ other cloud offerings evolve and grow.
Moving forward, we’ll also continue to support a portfolio of methods to deliver all manner of business applications and customizations in SharePoint Online.
We know migration from legacy solutions can be disruptive, and we’re committed to partnering with you on this journey. Our Product and Customer Support teams are ready to help you in this journey with advice and guidance to move your solutions forward. We’ve collected our existing set of guidance on add-ins and solution development for SharePoint Online below. We’ll continue to listen to feedback and develop more guidance to help customers as needed.
In the coming weeks, running code-based sandbox solutions in SharePoint Online multi-tenant environments also will be disabled. Customers with these solutions should watch the Message Center and Service Health Dashboard (SHD) for details, timelines, and exception processes.
or pure client-side development, which provide highly-scalable, cloud-first approaches to extending SharePoint. Since then, many customers have transitioned full-trust and sandboxed solutions to the add-in model, and their success and experiences are reflected in the samples and guidance of our