Right, the first deadline is nearly here – March 15th – and I need to explain what’s actually stopping and whether it affects you.
If you’ve got custom scripts running in your SharePoint, they’re about to stop working. Permanently. And unlike the previous delays Microsoft offered, there’s no extension this time.
What Are Custom Scripts? (In Plain English)
Custom scripts are the behind-the-scenes code that makes your SharePoint do clever things beyond the standard features. Think automatic calculations in your forms, custom approval buttons, special formatting that matches your brand, or those handy little tools your developer built years ago.
Technically, we’re talking about Content Editor Web Parts, Script Editor Web Parts, and any custom JavaScript or jQuery code embedded in your pages. But really, if you’ve got “clever bits” in SharePoint that do things the standard version doesn’t, there’s a good chance custom scripts are involved.
What Actually Stops on March 15th?
From March 15th onwards, this custom code simply won’t run. Your pages will load, but the custom functionality disappears.
Here’s what I’m seeing break for SMEs: automated VAT calculations in quote forms, custom approval workflows that email specific people based on amount, client-facing portals with branded interfaces, property search tools on estate agent intranets, and those modified document libraries that automatically sort and tag files.
If someone built something “special” for you in SharePoint Classic, it probably uses custom scripts.
Why There’s No Workaround This Time
Microsoft provided a temporary PowerShell fix last year that let administrators delay this change. That expires on March 15th, and they’ve been clear – there are no extensions, no exceptions, and no alternative workarounds.
They’re forcing everyone toward Modern SharePoint, which handles customisation differently through Power Automate and the SharePoint Framework. It’s more secure, but it means your old code won’t work.
What You Should Do Right Now
First, find out if you’re affected. Open your SharePoint sites and look for anything that seems custom-built – special forms, unusual buttons, automated processes. If you’re not sure, ask whoever manages your SharePoint.
Second, document what these custom bits actually do for your business. You’ll need this information for planning alternatives.
Third, talk to someone now – whether that’s us at be braver online or another solutions partner. You’ve got weeks, not months, and migration takes time.
Don’t wait until March 16th when things stop working. Find out your risk exposure now and talk to an impartial solutions partner today.
Official Microsoft Sources:
- Updates to custom scripting in sites and Classic Publishing site creation (Message Center MC1117115)
- SharePoint Add-Ins and Azure ACS retirement FAQ
Industry/Partner Sources:
- Custom Script Setting in SharePoint & OneDrive Removed
- SharePoint Classic End of Life: Act Before It’s Too Late
