← Back
(Updated) Updates to custom scripting in sites and Classic Publishing site creation
MC1117115 · build prod-20251231-200323
Category
planForChange
Severity
normal
Major change
True
Last modified
2025-09-02 13:16:30
Summary source
Azure OpenAI (gpt-4.1)
Action by (Graph)
Action by (AI)
Services
SharePoint Online
Tags
Updated message, Feature update, Admin impact
Master tags
Security
Roadmap IDs

One-line summary

SharePoint Online will disable custom scripting and block new classic publishing site creation/features starting September 15, 2025; admins can temporarily opt out until March 15, 2026.

Similar updates

More like this
MC1186368 Microsoft SharePoint: Update to custom scripting governance in App Catalog site
To temporarily opt out of custom scripting governance for a specific site (effective for 24 hours with tenant admin approval), use the following PowerShell command: Set-SPOSite -DenyAddAndCustomizePages $false To update the site property bag (by default disallowed when custom script governance is enabled), use the following PowerShell commands.
MC1193419 Content Security Policies (CSP) are coming to SharePoint Online and might impact your custom SPFx solutions
Content Security Policies (CSP) are coming to SharePoint Online and might impact your custom SPFx solutions SharePoint Online will enforce Content Security Policy on March 1, 2026, blocking scripts from non-trusted sources and requiring updates to custom SPFx solutions using untrusted or inline scripts. We’re improving SharePoint Online security.
MC1186372 SharePoint branding governance via PowerShell
SharePoint branding governance via PowerShell SharePoint admins can centrally enforce site branding, manage themes, and audit changes via PowerShell, with new controls rolling out starting November 2025. [Introduction] Coming soon to SharePoint: Tenant admins will be able to centrally manage site branding using PowerShell. ...(Worldwide): .
MC1133898 PowerShell 2.0 removal in Windows
PowerShell 2.0 removal in Windows Windows PowerShell 2.0 will be removed from Windows 11 (24H2) in August 2025 and Windows Server 2025 in September 2025; update legacy scripts to newer PowerShell versions. Windows PowerShell 2.0 is removed from Windows 11, version 24H2 starting with the August 2025 non-security update. PowerShell 5.x introduced.
MC1184996 Legacy SharePoint Online Content Delivery Network (CDN) domain to be retired—review configurations
...Content Delivery Network (CDN) domain to be retired—review configurations SharePoint Online will retire the legacy CDN domain publiccdn.sharepointonline.com; update all references to the new domain public-cdn.sharepointonline.com before March 31, 2026[Introduction] As part of ongoing service modernization, Microsoft has migrated the hosting of.
MC693865 (Updated) SharePoint Add-In retirement in Microsoft 365
(Updated) SharePoint Add-In retirement in Microsoft 365 SharePoint Add-Ins will retire and stop working on April 2, 2026; migrate customizations to SharePoint Framework (SPFx) and notify users and developers. Updated October 3, 2025: This update serves as a reminder that SharePoint Add-Ins will retire and stop working in 6 months from now (April.

Details

Summary
Starting September 15, 2025, SharePoint Online will disable custom scripting by default on classic publishing sites, block creation of new classic publishing sites, and prevent publishing feature activation. New settings allow site property bag updates without enabling custom scripting. Temporary opt-outs via PowerShell are available until March 15, 2026.

Body (from Message Center)

Updated September 2, 2025: Upcoming SharePoint Online changes may impact your organization. Please review the below.

We are implementing the following changes to custom scripting and classic publishing in SharePoint Online.

1. Disablement of custom scripting

Custom scripting will be disabled by default (setting DenyAddAndCustomizePages to 1 or $true) for sites created with the following templates:

  • BLANKINTERNETCONTAINER#0 = Classic Publishing Portal Site
  • CMSPUBLISHING#0 = Classic Publishing Site
  • BLANKINTERNET#0 = Classic Publishing Site Blank
  • CSPCONTAINER#0 = SharePoint Embedded Site

NOTE:

  • Existing classic publishing sites created with the templates listed above will have custom scripting disabled by default.
  • Disabling custom scripting does not affect the execution of scripts that have already been added to a site or page.

Refer to this documentation to learn more about the security considerations of ungoverned scripting.

2. Ability to set site property bag valued without requiring custom scripting enablement.

Users no longer need to set DenyAddAndCustomizePages to $false or 0 (i.e. enable custom scripting) in a site to manage site property bag values. We have introduced a new AllowWebPropertyBagUpdateWhenDenyAddAndCustomizePagesIsEnabled setting at the site level and at the tenant level to allow adding/managing site property bag values. Please see documentation here for tenant level setting and here for the site level setting. 

3. Classic publishing sites creation and feature activation changes

Users will no longer be able to create new classic publishing related site collections or activate publishing features in existing site collections. This applies to both UX and API interactions.

Sites collections with the following templates cannot be created:

  • BLANKINTERNETCONTAINER#0 = Publishing Portal Site
  • CMSPUBLISHING#0 = Publishing Site
  • BLANKINTERNET#0 = Publishing Site Blank
  • ENTERWIKI#0 = Enterprise Wiki
  • SRCHCEN#0 = Enterprise Search Center
  • SPSSITES#0 = Site Directory
  • SPSNHOME#0 = News Home Site
  • PRODUCTCATALOG#0 = Product Catalog
  • SPSREPORTCENTER#0 = Report Center
  • SPSTOPIC#0 = Topic Area Template

Existing classic publishing enabled site collections are unaffected and can continue regular usage, including creation of sub sites.

[When this will happen]

Both changes, the extended custom scripting governance and the new classic publishing restrictions, will take effect starting September 15, 2025.

[How this will affect your organization]

  • When custom scripting is disabled in classic publishing sites, users will no longer be able to use script editor web parts, create custom master pages or page layouts, and utilize several other features. More details on features affected when custom scripting is disabled can be viewed in this documentation.

  • With the change to stop the creation of new classic publishing site collections and publishing feature activation, SharePoint admins will no longer be able to create new classic publishing enabled site collections or enable publishing features at site collection level.

[What you need to do to prepare]

We recommend taking the following actions to prepare for these upcoming changes.

1. Inform owners of the classic publishing sites in your organization of these upcoming changes. Promote switching to use of Modern sites. Refer to this guide.

2. To temporarily opt out of the custom scripting enforcement in classic publishing sites for your tenant until March 15, 2026, use the following PowerShell command:

Set-SPOTenant -DelayDenyAddAndCustomizePagesEnforcementOnClassicPublishingSites $true

3. To temporarily opt out of custom scripting enforcement for a specific site (with any template) with tenant admin approval (effective for 24 hours), use the following PowerShell command:

Set-SPOSite <SiteURL> -DenyAddAndCustomizePages $false

4. If you need to allow the creation of new classic publishing site collections or enable publishing feature activations, use the following PowerShell command set the flag to allow.

Set-SPOTenant -AllowClassicPublishingSiteCreation $true

NOTE:

  • You need to install the latest (16.0.26211.12010 or higher) SharePoint Online Management Shell in order to run the commands above.
  • The DelayDenyAddAndCustomizePagesEnforcementOnClassicPublishingSites command is scheduled to end starting on March 15, 2026, while all other commands are expected to remain functional beyond that date. 

[Compliance considerations]

There is no impact or change to compliance.

[Referenced content]

Security considerations of allowing custom script - SharePoint in Microsoft 365 | Microsoft Learn

Allow or prevent custom script - SharePoint in Microsoft 365 | Microsoft Learn

SharePoint modernization guidance | Microsoft Learn


Raw JSON (for debugging)

Expand/collapse the full payload below.
Show/hide raw
{
  "snapshot_item": {
    "action_required_by": null,
    "ai_action_required_by": null,
    "ai_actions": [
      "Inform classic publishing site owners",
      "Promote migration to Modern sites",
      "Review PowerShell opt-out options",
      "Update SharePoint Online Management Shell"
    ],
    "ai_master_tags": [
      "Security"
    ],
    "ai_model": "gpt-4.1",
    "ai_summary": "SharePoint Online will disable custom scripting and block new classic publishing site creation/features starting September 15, 2025; admins can temporarily opt out until March 15, 2026.",
    "ai_topics": [
      "SharePoint"
    ],
    "category": "planForChange",
    "details_map": {
      "Summary": "Starting September 15, 2025, SharePoint Online will disable custom scripting by default on classic publishing sites, block creation of new classic publishing sites, and prevent publishing feature activation. New settings allow site property bag updates without enabling custom scripting. Temporary opt-outs via PowerShell are available until March 15, 2026."
    },
    "id": "MC1117115",
    "importance": 5,
    "is_major_change": true,
    "last_modified": "2025-09-02T13:16:30Z",
    "ms_products": [
      "SharePoint"
    ],
    "platforms": null,
    "roadmap_ids": [],
    "services": [
      "SharePoint Online"
    ],
    "severity": "normal",
    "tags": [
      "Updated message",
      "Feature update",
      "Admin impact"
    ],
    "title": "(Updated) Updates to custom scripting in sites and Classic Publishing site creation"
  }
}