Microsoft Is Retiring Classic SharePoint Pages: What Businesses Need to Do

Microsoft is retiring classic SharePoint publishing sites, user-created pages and legacy custom scripting in two stages. New classic publishing sites are blocked from 1 March 2027, while affected pages in existing Microsoft 365 tenants become read-only from 1 October 2028. Businesses should identify important classic content and plan its move to modern SharePoint now.

Microsoft is not deleting existing classic content. However, businesses that still rely on wiki pages, Web Part pages, publishing pages or custom ASPX pages need to know which pages must remain editable.

The announcement matters even if your current SharePoint sites appear to work normally. Complex pages, old scripts and heavily customised publishing sites can take time to assess, rebuild and test.

What is Microsoft changing in SharePoint?

Microsoft is reducing support for the legacy SharePoint experiences that pre-date modern SharePoint. It describes the goal as moving customers towards more secure, manageable, and mobile-ready modern SharePoint experiences.

Microsoft also says classic page content is not fully represented in the formats used by Microsoft 365 Copilot. That can reduce the coverage or accuracy of Copilot answers when important business information remains on classic pages.

Modern SharePoint pages and solutions built with the SharePoint Framework are not included in this particular retirement. The change is aimed at classic publishing sites, classic user-created pages and legacy custom scripting.

When will classic SharePoint pages become read-only?

Phase 1: 1 March 2027

• All tenants will be prevented from creating new classic publishing site collections and subsites.
• The classic publishing feature can no longer be activated for site collections or subsites.
• For tenants created on or after this date, users cannot create new classic pages and legacy custom scripting is disabled by default.

Phase 2: 1 October 2028

• The page and scripting restrictions extend to remaining existing tenants.
• Affected classic user-created pages become read-only.
• Users can still open and view those pages, but they cannot create or edit them.
• Adding or updating affected custom scripts is disabled.

For an established Microsoft 365 tenant, the key practical deadline is October 2028. The earlier March 2027 date still matters because it ends creation of new classic publishing sites for everyone.

Which SharePoint pages are affected?

Microsoft lists the following classic user-created page types:

• Wiki pages
• Web Part pages
• Blog pages
• Publishing pages
• Custom ASPX pages created with SharePoint Designer or third-party solutions

Classic publishing site templates are also affected. Modern SharePoint pages are not, and ordinary classic list and library views or list form pages are not currently included in the page read-only change. However, legacy scripts embedded in those experiences may still be affected by the separate scripting restrictions.

Will Microsoft delete classic SharePoint content?

No. Microsoft says these phases will not delete or modify existing classic page content. Pages that reach the enforcement date remain available for viewing, with existing data-governance controls continuing to apply.

The operational risk is loss of editing rather than immediate deletion. A business could discover that an important procedure, intranet page or bespoke workflow interface can still be opened but can no longer be maintained.

Do not assume that a page is modern simply because it looks current. Older sites are sometimes restyled while retaining classic page types, Web Parts or scripts underneath.

How can businesses find classic SharePoint pages?

Microsoft recommends beginning with evidence rather than assumptions. SharePoint administrators can use the SharePoint Classic Activities category in Microsoft Purview Audit and review the ClassicPageCreated, ClassicPageEdited and ClassicPageViewed events.

The Microsoft 365 Assessment Tool can also identify classic pages, Web Parts, customisation patterns and likely modernisation options. If the assessment finds no affected classic publishing sites, pages or scripts, no action is required for this retirement.

Prioritise pages that are frequently edited, heavily used or business-critical. An old page that nobody uses may be retired, while a page supporting a live operational process needs careful testing and a replacement plan.

What should businesses do now?

1. Confirm whether classic content exists. Ask your Microsoft 365 administrator or IT provider to inventory classic sites, pages and custom scripts.
2. Check actual usage. Audit events help separate important pages from abandoned content.
3. Identify business owners. Every important page should have someone who can confirm what it does and whether it is still required.
4. Group pages by complexity. Simple wiki pages may be straightforward to transform; bespoke scripts, layouts and integrations can require redesign.
5. Modernise in manageable waves. Test representative pages first, then reuse what you learn across similar content.
6. Validate permissions and links. A visually correct replacement can still expose the wrong information or break a business process.
7. Allow time for manual work. Microsoft warns that automated tools may not fully reproduce highly customised pages.

Any modernisation project is also a useful opportunity to review who can access the underlying files. Our guide to checking access to Microsoft 365 files explains the practical permission checks businesses should make.

Why does this matter for Microsoft 365 Copilot?

Microsoft says classic page content is not fully represented in the content formats that support Microsoft 365 Copilot. Important policies or instructions kept only on classic pages may therefore be less visible to Copilot than modern SharePoint content.

Modernising pages does not replace good permissions and governance. Copilot works within the access a user already has, so businesses should review old sharing and permissions before making more content easier to discover. See our guidance on why SharePoint permissions matter for Copilot.

The retirement should be treated as a content, governance and business-continuity project—not simply a visual redesign.

Quick answers

Is Microsoft retiring SharePoint Online?

No. Microsoft is retiring specific classic publishing, page and scripting experiences. Modern SharePoint continues.

When do classic SharePoint pages become read-only?

For existing tenants, affected classic user-created pages become read-only from 1 October 2028. New tenants created on or after 1 March 2027 face earlier restrictions.

Will classic SharePoint pages be deleted?

No. Microsoft says existing content remains viewable, but affected pages can no longer be edited after enforcement.

Do modern SharePoint pages need migrating?

No. Modern pages are not included in this retirement.

What if we do not use classic SharePoint?

If a proper assessment finds no affected classic publishing sites, pages or custom scripts, no action is required for this change.

The important point

The deadline is not a reason to panic, but it is a reason to start checking. Businesses have time to identify classic SharePoint content and modernise it in controlled stages.

Waiting until 2028 could turn a manageable content project into an urgent rebuild. Start with an inventory, focus on pages the business still uses, and test replacements before the old pages become read-only.

Microsoft sources

• Microsoft Learn: Upcoming changes to classic publishing sites, classic pages and custom scripting in SharePoint Online (last updated 28 August 2026).
• Microsoft SharePoint Blog: Upcoming changes to classic experiences in SharePoint Online (published 31 August 2026).

Microsoft 365 timelines and implementation details can change. Check the linked Microsoft guidance and your Microsoft 365 Message Center for the latest tenant-specific information.