What is actually changing?
This is a phased retirement, not a single switch-off, and each phase affects different things:
- Creation of classic publishing sites - From March 1, 2027, creating new classic publishing sites and activating the publishing feature will be turned off for existing tenants. The affected templates include Publishing Portal, Publishing Site, Enterprise Wiki, Site Directory, Report Center and Topic Area, among others.
- Classic pages - Existing classic user-created pages become read-only in October 2028. They will still be viewable, but nobody will be able to edit them.
- Custom scripting - Sites that rely on scripted customizations will lose that capability. Confirm the exact timing in your Message Center post (MC1464926) for your tenant.
This follows earlier retirements in the same family. Microsoft has already announced the end of support for SharePoint Designer 2013, pushing organizations toward Power Automate as the supported replacement for classic workflows. If you missed those, treat this as your second chance to get ahead.
Why it matters more than it looks?
Classic sites are often the quiet foundation of business processes: an intranet built years ago, a wiki everyone relies on, a report center feeding a monthly review. Nobody thinks about them until an edit button disappears. The risk is rarely the page itself. It is the undocumented dependency behind it, such as a script, a workflow or a navigation link another system depends on.
A practical plan
- Discover (now to December)
Find out what you actually have. Use the Microsoft 365 Assessment Tool and the Purview Audit log. Microsoft points to the SharePoint Classic Activities category, with events such as ClassicPageCreated, ClassicPageEdited and ClassicPageViewed, to identify active classic page usage. Usage data matters because it separates sites people use from sites that merely exist. - Triage (December to January)
Sort every classic site into one of four buckets:
Retire: no meaningful activity in 12 months. Archive and delete.
Rebuild: high-value content or processes that deserve a modern redesign.
Migrate as-is: simple content that maps cleanly to modern pages and libraries.
Investigate: heavy customization, scripts or third-party dependencies that need a closer look.
Expect the Retire bucket to be larger than anyone assumes. Cutting scope early is the cheapest way to reduce risk. - Prioritize by risk and date (January)
Start with sites that depend on publishing templates, since those are hit first. Then address anything running custom scripts or legacy workflows. Leave stable, low-traffic classic pages for the 2028 window, but do not ignore them. - Pilot and migrate (February onward)
Pick two or three representative sites and migrate them end to end. Use the pilot to estimate effort per site type, then plan waves of 10 to 20 sites. Build in time for owner review. Technical migration is usually the easy part, and content owner sign-off is what causes delays. - Communicate early and often
Site owners need to know what is happening, what you need from them, and when. A short, repeated message beats one long announcement. Name an owner for every site, because sites with no owner cause the worst surprises late in the program. - Govern what comes next
Once sites are modern, keep them that way. Set rules on site creation, ownership, lifecycle and review. Otherwise you will rebuild the same backlog in five years.
Next steps this week
- Read Message Center post MC1464926 and note the dates that apply to your tenant.
- Run the Microsoft 365 Assessment Tool and pull classic page activity from the audit log.
- Build a single inventory sheet: site, owner, last activity, customization level, decision.
- Book a 30-minute session with your key stakeholders to agree on the triage categories.
- Choose your pilot sites.
The bottom line
The deadlines are staggered, and that helps you. The work is mostly discovery and decision-making, and the migration itself is the smaller part. Teams that inventory early, retire aggressively and migrate in waves will reach each deadline calmly. Teams that start in February 2027 will spend March firefighting.
Resources