Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 253/255 feeds/APIs · 417/444 docs · checked 12:24 UTC Customize Public modeDiscuss ChangeIntel on Discord

Upcoming changes to classic publishing sites, classic user-created pages and custom scripting in SharePoint Online

Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.

Action date

Microsoft tags this a retirement but gives no action date in the notice metadata. Any date is in the text below.

Microsoft's start date
31 Aug 2026
Last changed by Microsoft
31 Aug 2026
First seen here
19 Oct 2026
Versions seen
1

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

What and why

Microsoft SharePoint continues to evolve to help organizations create and manage content more securely, easily, and intelligently. As part of this evolution, we’re introducing upcoming changes to classic publishing sites, classic user-created pages, and custom scripting in SharePoint Online, with a two-phase rollout designed to give organizations time to assess usage, plan modernization, and move to modern SharePoint experiences.

Beginning March 1, 2027, classic publishing site creation and publishing feature activation will be disabled for all existing tenants. For new tenants created on or after that date, no new classic pages can be created by default; adding or updating custom scripts and related changes will be disabled.

Beginning October 1, 2028, all existing classic user-created pages will be set to read-only and custom scripting enforcement will extend to all tenants.

Affected classic user-created page types include wiki pages, web part pages, blog pages, publishing pages, and custom ASPX pages created using SharePoint Designer or third-party solutions.

None of these changes affect classic page content; existing pages will remain accessible for viewing.

Rollout schedule

  • Worldwide: We will begin rolling out early March 2027 and expect to complete by early April 2027.
  • GCC: We will begin rolling out early May 2026 and expect to complete by late May 2027.
  • GCC High: We will begin rolling out early May 2027 and expect to complete by late May 2027.
  • DoD: We will begin rolling out mid-June 2027 and expect to complete by early July 2027.

Impact on your organization

1. Creation of new classic publishing sites, and activation of the classic publishing feature, will be turned off for site collections and subsites. Below is the list of affected site templates, and classic templates aren't affected.

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

2. Classic user-created pages — wiki pages, web part pages, blog pages, publishing pages, and custom ASPX pages — will become read-only. For existing tenants, users can still open and view these pages, but can no longer create or edit them.

3. The ability to add or update custom scripts and related settings will be disabled. Existing scripts will continue to function.

Action required / Recommendations

Discover and assess your classic environment

  • Identify usage of classic sites and pages across your tenant. Use the Standard Purview Audit log category (SharePoint Classic Activities) and events (ClassicPageCreated, ClassicPageEdited, and ClassicPageViewed) to identify active classic page usage, and leverage the Microsoft 365 Assessment Tool to understand the overall classic scope and modernization feasibility.

Prioritize based on business importance and usage

  • If your assessment finds no classic content, none of these changes apply to you — no action needed. Otherwise, focus first on high-value or frequently updated classic sites and pages, and identify where modernization will have the greatest impact. Classifying content by business criticality can help guide a phased migration plan.

Transform to modern SharePoint experiences

  • Use modernization tools such as SharePoint PnP Modernization and SharePoint PnP Page Modernization Agent to convert classic pages where applicable. Microsoft will continue enhancing the tooling to accelerate page modernization with best-effort fidelity reservation, but it may not fully automate complex scenarios; modernization is a project that typically requires planning, resourcing, and highly customized pages often need redesign or manual rebuilding.

Adopt a phased migration strategy

  • Combine centralized IT-led planning and prioritization with distributed execution by site owners over time. Most organizations find success by modernizing in waves rather than attempting a single large-scale migration.

Learn more

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Oct 12:24 UTC · 253 of 255 readable · 252 fully read · documentation 417/444 current