Home > Work > Code based Sandbox solutions finally on their way out in #O365 MT

Code based Sandbox solutions finally on their way out in #O365 MT

This is just a short post to remind myself later when this occured.

From speaking to colleagues etc. advise from Microsoft went out to customers a couple of weeks ago and recently this article was published.

Link: https://dev.office.com/blogs/removing-code-based-sandbox-solutions-in-sharepoint-online

In particular, this should be noted:

Detailed below are recent actions taken and what to expect next:

  • As part of the removal process, activation of new code-based sandbox solutions, as well as updates of existing solutions are no longer available.
  • 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.

And more importantly for No Code Sandbox Solutions

    Note that currently, we do not plan to deprecate or remove support for declarative (no-code) sandboxed solutions. 

Sandbox Solutions have been deprecated (code based ones at least) for a long time now.

Relevant article from 2014:

Sympmarc.com provides guidance on the usage of the PowerShell script from the PnP including installation of the right modules (Azure, O365 etc.) for Windows…

More info is available here:

And lastly, Rencore also have a free tool to help you find those solutions (I haven’t tried this however):

    They state that as of today (10th August), Code based Sandbox Solutions will not be allowed within 21 days…


Keep SharePointin’

  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: