check before: 2025-09-15
Product:
Purview Information Protection, SharePoint
Platform:
Online, Web, World tenant
Status:
Change type:
Admin impact, Feature update, Updated message
Links:
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.
Details:
Updated January 29, 2026: We are updating this post as a reminder. 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.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2025-07-18
updated:
2026-01-30
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
summary for non-techies**
Starting September 15, 2025, SharePoint Online will disable custom scripting by default for certain classic publishing sites, restrict the creation of new classic sites, and allow some site settings updates without enabling custom scripting, encouraging a transition to modern sites.
Direct effects for Operations**
Disabling Custom Scripting
Users will lose the ability to use script editor web parts, create custom master pages, and page layouts, leading to a decrease in customization options for classic publishing sites.
- roles: SharePoint Admin, Content Creator
- references: https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script#features-affected-when-custom-script-is-blocked, https://learn.microsoft.com/sharepoint/security-considerations-of-allowing-custom-script
Blocking Creation of Classic Publishing Sites
Users will no longer be able to create new classic publishing site collections, which may hinder the development of new content and features in the organization.
- roles: SharePoint Admin, Project Manager
- references: https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-guidance, https://learn.microsoft.com/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps#-allowwebpropertybagupdatewhendenyaddandcustomizepagesisenabled
Impact on Existing Features
Existing features that rely on custom scripting will be affected, potentially leading to broken functionalities and user dissatisfaction.
- roles: IT Support, End User
- references: https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script, https://learn.microsoft.com/sharepoint/security-considerations-of-allowing-custom-script
User Experience Degradation
The inability to customize sites may lead to a less engaging user experience, as users cannot tailor the site to their needs.
- roles: End User, Content Creator
- references: https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-guidance, https://learn.microsoft.com/sharepoint/security-considerations-of-allowing-custom-script
Increased Administrative Burden
SharePoint admins will face increased workload to manage site properties without custom scripting, leading to potential delays in site updates.
- roles: SharePoint Admin, IT Manager
- references: https://learn.microsoft.com/powershell/module/sharepoint-online/set-sposite?view=sharepoint-ps#-allowwebpropertybagupdatewhendenyaddandcustomizepagesisenabled, https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script
Configutation Options**
XXXXXXX ... paid membership only
Opportunities**
XXXXXXX ... free basic plan only
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
XXXXXXX ... free basic plan only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2026-01-30 | MC Messages | 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. | Updated January 29, 2026: We are updating this post as a reminder. 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. |
| 2026-01-30 | MC Last Updated | 09/02/2025 15:16:30 | 2026-01-29T18:41:22Z |
| 2026-01-30 | MC 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 https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script#features-affected-when-custom-script-is-blocked https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-guidance https://learn.microsoft.com/en-us/sharepoint/security-considerations-of-allowing-custom-script https://learn.microsoft.com/powershell/module/sharepoint-online/set-sposite?view=sharepoint-ps#-allowwebpropertybagupdatewhendenyaddandcustomizepagesisenabled https://learn.microsoft.com/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps#-allowwebpropertybagupdatewhendenyaddandcustomizepagesisenabled https://learn.microsoft.com/sharepoint/dev/transform/modernize-guidance https://learn.microsoft.com/sharepoint/security-considerations-of-allowing-custom-script https://www.microsoft.com/en-us/download/details.aspx?id=35588&msockid=1928b372f07766b62b63a78cf1426719 | 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. The following tenant-level opt-out operation, used to allow custom scripting changes in classic publishing sites, will be retired starting March 15, 2026. Please ensure appropriate actions are taken ahead of this change. Set-SPOTenant -DelayDenyAddAndCustomizePagesEnforcementOnClassicPublishingSites $true 3. Customers may still temporarily opt out of custom scripting enforcement for a specific site (any template) with tenant admin approval. This opt-out is effective for 24 hours and can be enabled using 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 https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script#features-affected-when-custom-script-is-blocked https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-guidance https://learn.microsoft.com/en-us/sharepoint/security-considerations-of-allowing-custom-script https://learn.microsoft.com/powershell/module/sharepoint-online/set-sposite?view=sharepoint-ps#-allowwebpropertybagupdatewhendenyaddandcustomizepagesisenabled https://learn.microsoft.com/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps#-allowwebpropertybagupdatewhendenyaddandcustomizepagesisenabled https://learn.microsoft.com/sharepoint/dev/transform/modernize-guidance https://learn.microsoft.com/sharepoint/security-considerations-of-allowing-custom-script https://www.microsoft.com/en-us/download/details.aspx?id=35588&msockid=1928b372f07766b62b63a78cf1426719 |
| 2025-09-03 | MC Messages | Updated August 21, 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 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. | 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. |
| 2025-09-03 | MC Last Updated | 08/21/2025 15:12:21 | 2025-09-02T15:16:30Z |
| 2025-09-03 | MC Summary | Starting September 15, 2025, SharePoint Online will disable custom scripting by default on classic publishing sites and block creation of new classic publishing site collections. New settings allow managing site property bags without enabling custom scripting. Temporary opt-outs are available until March 15, 2026. Existing sites remain unaffected. | 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. |
| 2025-08-22 | MC Messages | 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 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. | Updated August 21, 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 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. |
| 2025-08-22 | MC Title | Updates to custom scripting in sites and Classic Publishing site creation | (Updated) Updates to custom scripting in sites and Classic Publishing site creation |
| 2025-08-22 | MC Last Updated | 07/18/2025 02:07:08 | 2025-08-21T15:12:21Z |
| 2025-08-22 | MC MessageTagNames | Feature update, Admin impact | Updated message, Feature update, Admin impact |
| 2025-08-22 | MC Summary | Custom scripting will be disabled by default for certain SharePoint Online templates starting September 15, 2025. Users can manage site property bag values without enabling custom scripting. Creation of new classic publishing site collections and activation of publishing features will be restricted. Existing sites remain unaffected. | Starting September 15, 2025, SharePoint Online will disable custom scripting by default on classic publishing sites and block creation of new classic publishing site collections. New settings allow managing site property bags without enabling custom scripting. Temporary opt-outs are available until March 15, 2026. Existing sites remain unaffected. |
Last updated 2 weeks ago ago
