'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
SharePoint Custom Script Turns Off After 24 Hours: Causes and Solutions
Question details
Administrators are finding that the custom script setting in SharePoint Online automatically disables itself 24 hours after being enabled, regardless of whether scheduled PowerShell commands are used to keep it active.
- Product
- SharePoint Online
- Device & OS
- not provided
- Scenario
- Enabling custom scripts for SharePoint sites to support customized workflows or web parts, with the expectation that the setting remains active.
- Observed behavior
- SharePoint Online overrides administrative configurations and automatically reverts the custom script setting back to disabled after exactly 24 hours.
Ensure you have global or SharePoint Administrator privileges to review current site settings and evaluate alternative development frameworks for your tenant.
Migrate to Supported Developer Alternatives
Since Microsoft intentionally enforces a 24-hour reset policy on custom scripts for security reasons, the permanent solution is transitioning to modern SharePoint development frameworks.
SharePoint Online does not provide a permanent setting to keep the legacy custom script feature enabled. Microsoft automatically disables it after 24 hours to protect tenants from malicious script execution and cross-site scripting (XSS) vulnerabilities.
Instead of relying on unsupported workarounds like scheduled PowerShell scripts, administrators should plan a transition to modern, supported development models that do not require custom scripts to be enabled.
Review your SharePoint environment to identify which sites, pages, or web parts are currently failing due to the disabled custom script setting.
Transition your legacy custom functionalities to the SharePoint Framework (SPFx). SPFx is Microsoft's fully supported modern development model that operates securely without needing custom scripts enabled.
If your organization has business-critical legacy applications that cannot be immediately migrated, submit a feature request or support ticket through the Microsoft 365 Admin Center to request extended guidance.
Try WPS Office for Seamless Document Collaboration
While navigating SharePoint's administrative limitations, ensure your team has a reliable and lightweight document editor. WPS Office offers excellent compatibility with Microsoft formats without the complex administrative overhead.
- 1. Download WPS Office: Visit the official WPS website to download the free, lightweight installation package.
- 2. Install the Application: Run the installer and follow the simple on-screen instructions to set up WPS Office on your computer.
- 3. Open and Edit Documents: Launch WPS Office and open your existing .docx, .xlsx, or .pptx files directly, enjoying full format compatibility.
Frequently Asked Questions
Can I use a scheduled PowerShell task to keep SharePoint custom scripts enabled?
While some administrators attempt to use scheduled PowerShell scripts to re-enable custom scripts every 24 hours, Microsoft does not officially support this workaround. It may eventually be blocked or cause performance throttling.
Why does Microsoft disable custom scripts in SharePoint Online?
Microsoft disables the custom script feature by default and forces a 24-hour reset as a strict security measure. This protects SharePoint environments from vulnerabilities such as unauthorized code execution and cross-site scripting.
What are the alternatives to using custom scripts in SharePoint?
The recommended alternative is migrating to the SharePoint Framework (SPFx). SPFx provides a secure, modern, and fully supported way to build custom web parts and extensions without relying on legacy custom script settings.
Does this 24-hour rule apply to SharePoint Server (on-premises)?
No, the automatic 24-hour reset policy is specific to SharePoint Online (Microsoft 365). On-premises SharePoint Server environments still allow administrators to permanently configure and retain custom script settings.
