SharePoint Classic is being limited: what you need to know
Microsoft has announced new changes for classic publishing sites, classic pages and custom scripting in SharePoint Online. The changes will be introduced gradually from March 2027. Starting in October 2028, certain classic pages in existing Microsoft 365 environments will become read-only.
That does not mean that all of SharePoint Classic will disappear in the short term. It does mean that organizations must now investigate which parts of their intranet are affected. Especially with large or highly modified environments, modernization can take more time than expected.
What exactly has Microsoft announced?
Microsoft is implementing the changes in two phases.
Starting March 1, 2027 , all Microsoft 365 tenants:
- No new classic publishing sites can be created.
- The classic publishing feature can no longer be activated.
- The associated tenant setting will be permanently disabled.
New tenants created from this date onwards will have additional restrictions. Users can no longer create new classic pages there and adding or modifying custom scripts is blocked by default.
From October 1, 2028 , the restrictions will be extended to existing tenants. Classic pages that have not yet been modernized will then become read-only. Users can still open and view these pages, but they can no longer edit them. They can also no longer create new classic pages.
The full phasing is in the official Microsoft announcement.
Debble
Which SharePoint pages are affected?
The read-only measure applies to, among other things:
- Wiki pages
- Web Part Pages
- Blog pages
- Publishing pages
- Custom ASPX pages created using SharePoint Designer or third-party solutions
Existing content will not be deleted. Pages will remain available for viewing after the deadline.
Other classic components, such as list and library views and list forms, are currently not covered by this read-only measure. Custom scripts within these components may face additional limitations.
The correct conclusion is therefore not: "Microsoft is completely discontinuing SharePoint Classic." The more accurate message is that Microsoft is gradually restricting classic publishing and making certain classic pages read-only from October 2028.
Why is it important to start now?
October 2028 may seem a long way off. Nevertheless, Microsoft advises organizations to start taking stock and planning now.
A classic environment can consist of hundreds of pages, different types of Web Parts, customization, scripts and complex navigation structures. Not every part can be converted automatically or one-to-one. Microsoft indicates that highly customized pages may need to be redesigned or built manually.
By starting early, there is room to:
- Identify active classic pages and sites.
- Determine which content is still business-critical.
- Examine customization, scripts, and dependencies.
- Prioritize pages based on usage and importance.
- To carry out the modernisation in a controlled manner and in steps .
Microsoft recommends using the Microsoft 365 Assessment Tool for this, among other things. This allows organizations to inventory classic pages, Web Parts and custom patterns. Microsoft Purview Audit can also be used to investigate which classic pages are actually viewed or edited. Check out Microsoft's technical explanation.
From technical necessity to a better intranet
The announcement is not just a technical deadline. It is also a logical time to look at the intranet again.
What information do employees need on a daily basis? Can they find that information easily? Is the current environment still in line with hybrid working, mobile use and future AI applications? And how easily can communication and content teams manage the intranet?
A migration that only recreates old pages often takes existing limitations with them to the new environment. By first picking up the needs of employees, content owners, and other stakeholders , the modernization can be leveraged to actually improve the intranet.
Continue to develop with Debble
This change also shows why it is important to continue to develop your intranet. With a product like Debble, you build on an intranet solution that is being further developed and moves with Microsoft 365. This way, as an organization, you don't have to translate every technical change into adjustments to your intranet. This helps to limit the technical backlog and makes innovation part of regular management, instead of a major catch-up.
Need help with the next step?
The first step is not to migrate directly, but to create insight. What do these changes mean for your SharePoint environment? Which parts require attention and where are the opportunities to improve your intranet?
Wortell is happy to help you answer these questions. Together we look at your current environment and which next steps suit your organization. In this way, you work step by step towards a modern and manageable intranet that meets the needs of your employees.