Forum Discussion

rosamartinamilazzo25's avatar
rosamartinamilazzo25
Tin Contributor
Sep 18, 2026

SharePoint Online – BLANKINTERNET#0 Publishing Portal and Modern Pages

Hi everyone,

 

I’m trying to understand the recommended approach for an existing SharePoint Online site based on the BLANKINTERNET#0 template (Publishing Site / Publishing Portal).

The site is still based on the classic SharePoint architecture and currently uses:

  • a custom Master Page;
  • Publishing Pages;
  • custom Web Parts developed with SharePoint Framework (SPFx);
  • the SPFx Web Parts also communicate with a backend/API developed using .NET Framework 4.8.

 

I’ve read Microsoft’s recent announcement regarding the deprecation of classic publishing sites and classic user-created pages.

As I understand it:

  • starting March 1, 2027, the creation of new classic publishing sites and activation of the classic publishing features will be disabled;
  • starting October 1, 2028, existing classic user-created pages, including Publishing Pages, will become read-only;
  • existing pages will not be deleted, but users will no longer be able to create or edit them;
  • Microsoft recommends assessing and gradually modernizing classic content to modern SharePoint experiences.
  •  

However, I’m confused about the recommended modernization path for an existing Publishing Portal.

The deprecation announcement made me think that one possible approach would be to progressively replace the existing classic pages with Modern Pages.

However, in Microsoft’s documentation about modernizing classic publishing portals, I found the following statement:

"For publishing portals (sites based upon BLANKINTERNET#0, ENTERWIKI#0, SRCHCEN#0, SRCHCENTERLITE#0, BICENTERSITE#0, POINTPUBLISHINGHUB#0, POINTPUBLISHINGTOPIC#0 or sites using the “Pages” library) it's not currently supported to connect these to a Microsoft 365 group or to use modern pages. If you want to modernize your publishing portal it's recommended to start from a new communication site and configure that one accordingly."

 

This raises an important question for my scenario.

 

My question

For an existing BLANKINTERNET#0 Publishing Portal, is it currently supported to:

A) Keep the existing Publishing Portal and progressively create/use Modern Pages within the same site, migrating the content from the existing classic Publishing Pages to Modern Pages so that the content remains editable after 2028?

Or:

B) Are Modern Pages actually not supported in an existing BLANKINTERNET#0 Publishing Portal, meaning that the supported modernization path is to create a new Communication Site and migrate/configure the content there?

 

I would particularly like to understand what Microsoft currently considers the officially supported approach.

 

In other words:

For an existing BLANKINTERNET#0 Publishing Portal, can I progressively replace the classic Publishing Pages with Modern Pages within the same site, or do I need to create a new Communication Site and migrate the content there in order to move away from the classic Publishing architecture?

 

I would like to avoid a full migration to a new Communication Site if it is not necessary, but at the same time I want to make sure that I’m not implementing an approach that Microsoft considers unsupported.

 

 

Thanks in advance for any clarification!

developer

1 Reply

  • G_Vijai_Kumar's avatar
    G_Vijai_Kumar
    Copper Contributor
    Sep 19, 2026

    Short answer: B – not A.

    Option A cannot be considered valid a site created based on BLANKINTERNET#0 does not support contemporary pages within the same site therefore, it is not possible to migrate classic Publishing Pages to Modern Pages gradually. The quote is still valid since publishing portals are intentionally not included into group connection and modern pages exclusion. There are no constraints regarding adding a Site Pages library into such a site and creating pages there, however, this will lead you off the official route and you will have all the expected issues the classic master page and chrome will control the navigation there, modern page components will expect modern site, etc.

    So option B represents the official way of modernizing your site: creation of a new Communication Site >> migrating of the content >> retiring of the classic portal.

    Two dates that should be considered separately since they often get confused

    March 1, 2027 won't affect your existing site. It will prevent creating new classic publishing sites and activating the publishing feature. The only aspect to pay attention to: from that day it will be impossible to create a parallel classic site for the purposes of migration.

    October 1, 2028 will make existing classic pages read-only. Your site will still work, pages will still be available, however, it will be impossible to edit them. This is a "plan it now" timeline, not an emergency.

    With regard to SPFx + .NET 4.8 backend of your site: Web parts will be transferred "as is" if they are designed for modern pages; otherwise, web parts used on classic pages work differently, thus, check supportedHosts in your manifest.

    .NET Framework 4.8 API is not influenced by the dates listed above. However, it still may require a separate investigation: if it uses SharePoint app-only/ACS authentication, it was fully retired in April 2026 and should be replaced by Entra ID application. Not related to publishing deprecation, however, tends to show up in the same period.

    One more point, there is no need to perform a cutover. A common solution is creation of a new Communication Site and gradual migration of the most popular sections followed by redirections from the classic portal.