Microsoft has announced that the Custom Script setting in SharePoint and OneDrive will be removed by early June 2024. Administrators will no longer be able to control default behavior on self-service-created sites or personal sites. However, customers can still temporarily enable custom scripts using PowerShell. Existing scripts in OneDrive and SharePoint sites will not be affected. In this blog post, we'll delve into the details of these changes, their implications, and how you can prepare your organization.
Why Custom Script Settings Are Changing
Custom scripts in SharePoint Online have long provided users with the flexibility to customize their sites and add advanced functionality. However, this flexibility comes with several challenges:
•Security Risks: Custom scripts can introduce vulnerabilities that may be exploited by malicious actors.
•Compliance Concerns: Ensuring that custom scripts comply with organizational policies and industry regulations can be difficult.
•Performance Issues: Uncontrolled custom scripts can negatively impact site performance and reliability.
To address these challenges, Microsoft is implementing changes to the Custom Script settings in SharePoint Online.
What is changing?
The Custom Script setting, which allows users to execute custom scripts on personal sites and self-service created sites, will be removed. This setting is currently found in the SharePoint Admin Center under Settings -> Classic Settings.
A new PowerShell command, "DelayDenyAddAndCustomizePagesEnforcement"has been introduced. Available in SharePoint Online Management Shell version 16.0.24524.12000 or higher, this command allows you to delay the enforcement of changes to custom scripts on the Tenant until mid-November 2024.
There will not be an option to enable custom script on OneDrive sites once the delay set using DelayDenyAddAndCustomizePagesEnforcement ends in mid-November 2024.
The NoScriptSite setting will be configured to True for all existing SharePoint sites and OneDrive sites except for the below-mentioned site templates.
•BLANKINTERNETCONTAINER#0 = Classic Publishing Portal site
•CMSPUBLISHING#0 = Publishing Site
•BLANKINTERNET#0 = Publishing Site
•APPCATALOG#0 = App Catalog
•CSPCONTAINER#0 = CSP Container
The execution of existing scripts in OneDrive and SharePoint sites will not be impacted.
Customers will retain the ability to permit the execution of custom scripts on specific SharePoint sites using the Set-SPOSite <SiteURL> -DenyAddAndCustomizePages PowerShell command Or from the Active sites page in the SharePoint Admin Center.
Any modifications made to a site will automatically revert to False status within 24 hours, unless the new PowerShell command “DelayDenyAddAndCustomizePagesEnforcement” is used before mid-November 2024. After mid-November 2024, the 24-hour reversion will occur regardless.
How does this impact Intranet Enterprise (Wizdom)
Based on our team’s recent investigation, we have identified the following impacts resulting from the removal of the custom script option in a SharePoint Online tenant.
All Wizdom classic sites are created from the Classic Publishing Portal site template, and as per the above communication “NoScriptSite” will be false by default for sites created with this kind of site.
The functionality of all existing classic web parts added to existing pages will be unimpacted.
For adding new web parts on new or existing pages we need to make sure users have either of the below permission.
Full Control permissions

Should have “Add and Customize Pages” custom permission.

Impacted Sites
Customers with Intranet Enterprise (Wizdom) installed on Classic Team Sites will be impacted by this change. It is crucial to identify all Classic Team Sites with Intranet Enterprise (Wizdom) installations.
What does this mean
To begin with, if you are using Wizdom's modern setup, this change will not impact you. However, if you are using classic team sites, you will need to confirm which templates you are utilizing, as these sites are affected. While your intranet will continue to function normally, you may experience issues when updating existing pages or Wizdom web parts. As a temporary solution, you can enable custom scripts, but please note that this setting will automatically reset after 24 hours.
Recommended Actions
To mitigate the impact of this change, we recommend that you perform the following step to identify any sites on your intranet that may be impacted:
Identify Affected Sites: Determine which of your sites are Classic Team Sites with Intranet Enterprise (Wizdom) installed. You can head over to the O365 Admin Center -> Select Sharepoint-> Active Sites. On the far right click all sites and filter on Classic sites. In the Search tab you can input "STS#0". This should further filter to only display Teams Classic sites. You can confirm by clicking on a site and on the template section, in the bottom left it should display: Team site (classic experience).
Unaffected Sites
Please note that Modern Sites and Classic Publishing Sites will not be affected by this change.
We appreciate your attention to this matter and encourage you to take the necessary steps to ensure a smooth transition. If you have any questions or need further assistance, please do not hesitate to contact our support team.
Comments
0 comments
Article is closed for comments.