r/sharepoint • u/TheYouser • Aug 31 '26
SharePoint Online End of custom scripting in SharePoint Online?
Summary
Microsoft will disable creation of classic publishing sites and pages in SharePoint Online starting March 1, 2027, and make existing classic user-created pages read-only by October 1, 2028. Custom scripting will be disabled. Organizations should assess usage and plan phased modernization to modern SharePoint experiences.
Message Center Link
https://admin.cloud.microsoft/?ref=MessageCenter/:/messages/MC1464926
8
u/NorthernYakko Aug 31 '26
I imagine there will be an alternative method for 3rd party tools like ShareGate that rely on custom scripts to be enabled for some operations: https://help.sharegate.com/en/articles/10236719-copying-to-a-microsoft-365-site-collection-requires-custom-scripts-to-be-enabled-at-the-destination
2
5
u/bcameron1231 MVP Aug 31 '26
Yup, this is a big one.
That said, it probably shouldn’t come as a huge surprise. We’ve been warning about this and encouraging everyone to move off Classic for nearly 10 years now. Unfortunately, this is still going to impact quite a few customers who haven’t made the move to the modern experience yet.
1
u/TheYouser Aug 31 '26
It is not a huge surprise, but it is also a bad move IMHO.
We're at the 10 years anniversary of SPFx and there are valid reasons why developers did not adopt it.
Does this future change affect the possibility to enable custom scripting on a site?
https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-scriptWhat I'm currently doing is developing a *insert JS framework here* SPA bundle and copy it to a library. I can deploy it with a HTML or ASPX file as entry point. With this announced change, I will need to take all my apps and wrap them in SPFx application customizers (still to be evaluated on a case by case basis).
The idea is that I know what I'm doing, at the end of the day my JS solution will be as secure as any SPFx component and I'm not being forced to wrap it in the SharePoint UI or deal with webpart caching issues, changes of surrounding page layout, so many historical undocumented updates and basically no support except a open source community.
This is a bad move for the SharePoint developers community.
6
u/bcameron1231 MVP Aug 31 '26
Does this future change affects the possibility to enable custom scripting on a site?
Yes. March 2027 for all new tenants, and October 2028 for all tenants. You won't be able to change it.
The idea is that I know what I'm doing, at the end of the day my JS solution will be as secure as any SPFx component and I'm not being forced to wrap it in the SharePoint UI or deal with webpart caching issues, changes of surrounding page layout, so many historical undocumented updates and basically no support except a open source community.
100%. I can understand the frustration. Respectfully, not everyone has the skillset you might have... which is evident by all the historical implementations of the CEWP/SEWP that wreaked havoc for years.
2
u/daurkin Aug 31 '26
I was understanding the custom scripting would be disabled by default on the tenant and site collections. But you have the ability to enable it on site collections for 24 hours and then it’s automatically turns off. When it’s enabled, you can add SPFx components that use custom scripting, and then it works even after it’s disabled, you just can’t make changes to it.
3
u/bcameron1231 MVP Aug 31 '26
That is how it works today. This is not the way it will work with the deprecation. It will be turned on and read-only.
1
u/issy_haatin Sep 01 '26
Hmm that's annoying, i think pnp somehow relied on the custom script bit to set owner, member and visitor group on subwebs for pnp templates. Will have to update our c sharp code and verify what happens without that activate.
2
u/SilntNfrno IT Pro Aug 31 '26 edited Aug 31 '26
Am I missing something or wasn’t custom scripting already disabled a while back?
Also classic sites will continue functioning after October 2028, but pages will be read only? Classic lists/libraries will still be fully functional?
I’m trying to figure out if this is a bigger deal than I think, as someone recently working at a company that still has a classic root site, but plan to replace it over the next year.
5
u/bcameron1231 MVP Aug 31 '26
Am I missing something or wasn’t custom scripting already disabled a while back?
yes and no. You were allowed to disable it for 24 hours and do what you need to do, then it is re-enabled. This change will force it to always be enabled.
Also classic sites will continue functioning after October 2028, but pages will be read only? Classic lists/libraries will still be fully functional?
Lists and Libraries will not be affected (yet) by this change.
1
u/SilntNfrno IT Pro Aug 31 '26
Thanks. So if a classic site functions today without custom scripting enabled, it should continue to function after this?
My predecessor created the root as a classic publishing site and it has a bunch of subsites under it, so I’ve gotta work through getting everything migrated to new modern team sites, setup a modern communication site, and do the root site swap. Just trying to figure out how long I have lol.
3
u/bcameron1231 MVP Aug 31 '26
Yes.
However, I would be cautious of using the term function. In the short term, your existing content will still continue to work. You'll also still be able to edit those pages until October 1, 2028 (2 years away).
Full timeline here:
https://learn.microsoft.com/en-us/sharepoint/classic-user-created-page-deprecation
2
u/Formal_Solid1476 Sep 01 '26
Will this affect the classic calendars in SharePoint? Or the Modern Script Editor web part added as an app?
1
u/Sparticus247 Dev Sep 02 '26
I second this. There's a lot of classic calendars out there. I doubt it would affect the modern script editor though.
1
2
1
u/jkaczor Sep 01 '26
So, I guess they estimate that migration and modernization of all types of ASPX pages will be complete by then? Because - you can’t do full webpart migrations Classic > Classic and then modernize pages without scripting being enabled…
1
u/sp_admindev Sep 01 '26 edited Sep 01 '26
https://mc.merill.net/message/MC1464926 no login needed.
Toward bottom of the page:
- The ability to add or update custom scripts and related settings will be disabled. Existing scripts will continue to function.
1
1
u/sicmek Aug 31 '26
You can migrate your scripts to modern sites by using a custom script editor spfx webpart
1
u/Sparticus247 Dev Sep 02 '26
Yeah, there are real world use cases for this. People don't have to like it or agree with it, but it's true.
7
u/tootieFuckingFrutie Aug 31 '26
I’ve warned my org about this and they’ve done nothing about it. Let the shit show commence! Time to find a new job.