Script editor web part, when will stop working

Question

When script editor webpart will be decommission and not work any more

Answer 1

As per https://mc.merill.net/message/MC1193419 all the inline scripts will stop working from Mar 1st 2026 , example <input type="radio" onchange="Test()">. you can postpone this by 90 days using Set-SPOTenant -DelayContentSecurityPolicyEnforcement $true is applied.

Answer 2

Dear Rivero, Juan (NBCUniversal, Orlando) ,

Welcome to the Microsoft Q&A forum.

Thank you for reaching out and for sharing the details of your concern. Based on the information you have provided, it appears that your question is related to the potential deprecation timeline of the Script Editor web part in SharePoint. I understand this is an important topic, especially when planning future development or maintenance for your SharePoint environment. I have reviewed the documentation and references related to your concern. At this time, Microsoft has not announced any official plan to deprecate the Script Editor web part. The Script Editor remains supported and can still be used in SharePoint Server as well as in classic sites of SharePoint Online.

Please note that for SharePoint Online, the Custom Script feature must be enabled in order to use the Script Editor web part. This setting will need to be re‑enabled every 24 hours, so please ensure that it is turned on when required. If you encounter any issues while using the Script Editor, or if you have additional questions or concerns regarding this feature or its future support, please feel free to let me know.

I am looking forward to hearing from you.

---

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".       

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Answer 3

The Script Editor web part is not explicitly mentioned as being decommissioned in the provided context. However, it is noted that embedding scripts is discouraged due to inherent security risks. In the context of transforming classic web parts to modern ones, the community script editor can be used as an alternative during the transformation process. This suggests that while the classic Script Editor web part may still function for now, there may be a shift towards using more secure and modern alternatives in the future.

If you are using the Script Editor web part, it is advisable to keep an eye on updates from Microsoft regarding any changes to its status or functionality.

---

References:

• Overview of the used web part mapping
• Retiring SharePoint Framework domain isolated web parts for SharePoint Online
• Migrate a jQuery and DataTables solution built using Script Editor web part to the SharePoint Framework