SharePoint Custom Scripting Retirement: What Do You Need to Know?
Microsoft has recently announced that beginning March 1, 2027, Microsoft will disable the ability to add or update custom scripts by default for tenants created. As a part of its SharePoint custom scripting retirement plan, after October 1, 2028, the same restriction will extend to existing tenants. The `DenyAddAndCustomizePages` setting will be enforced as `True` and cannot be changed.
So, what does this mean for your business?
If your SharePoint environment has been around for years, there is a good chance that some of its functionality depends on custom JavaScript, Script Editor Web Parts, custom HTML, SharePoint Designer or other legacy customizations.
Now, the change doesn’t mean Microsoft is immediately deleting your existing scripts. What this means is legacy custom scripting is practically becoming a dead-end architecture.
Therefore, if your business-critical SharePoint processes depend on it, now is the time to identify those dependencies and decide what should be replaced, rebuilt or retired. In this article, we will discover how you can plan around it.
Discover More Opportunities to Improve Your SharePoint Experience
What Is Custom Scripting in SharePoint?
Before we explore the impact of SharePoint custom scripting retirement, let us first understand what custom scripting really is. Custom scripting allows you to modify SharePoint pages and sites using code, provided that you have the right permissions.
Most older SharePoint environments, use it for aspects commonly use it for
- JavaScript functions
- Script Editor Web Parts
- Content Editor Web Parts
- Custom HTML
- Custom CSS
- Page-level customizations
- Custom actions
- SharePoint Designer solutions
- Other legacy modifications
Now, the thing is that this custom code can operate with the permissions of the user to view the page. This creates security and governance challenges. This is one of the reasons Microsoft is moving organizations toward more controlled extensibility models.
Discover More About Custom SharePoint Development
Find out how we help you customize SharePoint experience, tailored to your specific needs.
What Is the Timeline for Microsoft SharePoint Custom Scripting Retirement?
There are two important dates.
March 1, 2027
For new Microsoft 365 tenants created on or after March 1, 2027:
- You can’t create new classic pages.
- Adding or updating custom scripts is disabled by default.
- `DenyAddAndCustomizePages` is enforced as `True`.
So, if you are an existing tenant, this phase primarily means that you will not be able to create new classic publishing sites and activate classic publishing features.
October 1, 2028
The restrictions extend to remaining existing tenants.
At this point:
- Users can’t add or update custom scripts by default.
- `DenyAddAndCustomizePages` is enforced as `True`.
- Classic user-created pages become read-only.
It is important to note that existing classic pages are not automatically deleted. You can continue to view them after the applicable phase takes effect.
Read More: The Complete Guide to SharePoint Classic Retirement
What Happens to Your Existing Scripts?
Your existing classic pages will remain accessible for viewing. However, the ability to maintain affected custom scripting becomes restricted.
I think it will be clear if we take an example. Imagine you have a 2019 SharePoint operations portal which contains:
- Custom JavaScript
- A Script Editor Web Part
- A custom approval interface
- Links to an ERP system
- Custom formatting
Now, such a page might continue working today. But if your business requirement changes in 2028, you may no longer be able to modify the underlying script-based customization.
What Should You Replace Custom Scripts With?
At Evolvous, our SharePoint custom dev consultants recommend that you take the following approach
| Legacy Customization | Possible Replacement |
| Custom JavaScript | SPFx |
| Script Editor Web Part | SPFx / modern Web Part |
| Custom business form | Power Apps |
| SharePoint Designer workflow | Power Automate |
| Custom dashboard | Power BI / modern Web Parts |
| Custom navigation | Modern SharePoint navigation |
| Custom page layout | Modern page sections/Web Parts |
Get Complete Support to Replace Your Custom Scripts
Connect with our team today and get the right support to replace your SharePoint custom scripts before the deadline.
Plan Your SharePoint Modernization
How to Audit Your SharePoint Environment?
We recommend that before you rebuild anything, it is important to create an inventory.
| Aspect | What You Need to Identify |
| Location | Site, library, page or Web Part |
| Technology | JavaScript, ASPX, Designer, Web Part, etc. |
| Owner | Business and technical owner |
| Usage | Who uses it and how often |
| Business impact | What happens if it stops working? |
Once, you have done that you will need to prioritize which customizations to modernize:
High priority
Your business-critical customizations that you are actively using
Medium priority
Frequently used customizations with manageable complexity.
Low priority
Unused, duplicate or obsolete customizations.
We find this approach to be much more effective than attempting an all-at-one-go migration of every piece of legacy code.
How Evolvous Can Help?
At Evolvous, we approach SharePoint custom scripting retirement as a modernization and architecture exercise. So, with us you are not just changing things because you have a deadline. You are enhancing the overall performance of the system.
We can help you:
- Discover legacy SharePoint customizations
- Identify script-dependent business processes
- Assess security and governance risks
- Map legacy functionality to modern Microsoft 365 capabilities
- Modernize SharePoint Designer solutions
- Replace custom scripts with supported approaches
- Develop SPFx solutions where appropriate
- Use Power Apps and Power Automate for business processes
- Integrate SharePoint with Power Platform, Azure and enterprise applications
- Test and validate modernized solutions
Get Complete Support from Custom Script Modernization
Do not wait for 2028. Connect with our team today and transition to a better SharePoint environment without any hassles.
Frequently Asked Questions
-
Is Microsoft banning all JavaScript in SharePoint?
No. Microsoft is restricting the ability to add or update **custom scripts** under the new SharePoint Online enforcement model. Modern supported development approaches such as SPFx are still available.
-
Will my existing SharePoint scripts stop working immediately?
Not necessarily Existing classic pages remain accessible for viewing. However, it will not remain maintainable indefinitely.
-
Can I still temporarily enable custom scripts?
Yes. Microsoft currently provides administrative controls for temporarily allowing custom script on specific SharePoint sites, but those changes can be overridden within 24 hours.
-
Should I replace every custom script with SPFx?
No. Some customizations should be replaced with Power Platform, standard SharePoint functionality or another Microsoft 365 service. Others may no longer be necessary.
