Skip to content

Add notice on deprecating classic sites & pages - #11011

Merged
Bert Jansen (jansenbe) merged 4 commits into
SharePoint:mainfrom
shiongzuo:classic-page-deprecate-notice
Sep 1, 2026
Merged

Add notice on deprecating classic sites & pages#11011
Bert Jansen (jansenbe) merged 4 commits into
SharePoint:mainfrom
shiongzuo:classic-page-deprecate-notice

Conversation

@shiongzuo

Copy link
Copy Markdown
Contributor

Updated the document to reflect changes in SharePoint Online, including deprecation timelines for classic pages and modernization guidance.

Category

  • Content fix
  • New article

Related issues

  • N/A

What's in this Pull Request?

This PR adds a notice on the upcoming deprecation of classic SharePoint sites and pages, and set up the link to the documentation.

Updated the document to reflect changes in SharePoint Online, including deprecation timelines for classic pages and modernization guidance.
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 4164519:

✅ Validation status: passed

File Status Preview URL Details
docs/transform/modernize-classic-sites.md ✅Succeeded View

For more details, please refer to the build report.

Added important notice regarding the deprecation of classic SharePoint pages and updated content for clarity.
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit c7c8252:

✅ Validation status: passed

File Status Preview URL Details
docs/transform/assess-sharepoint-modernization.md ✅Succeeded View
docs/transform/modernize-classic-sites.md ✅Succeeded View

For more details, please refer to the build report.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. "Classic SharePoint pages are being deprecated" -> Can we use "Classic user-created pages" to be more specific?
  2. "creation of new classic experiences will be restricted in certain scenarios" -> Can we use "creation of classic pages will be disabled for new tenants" to be more specific?
  3. Need to bold the two milestone dates.
  4. "existing classic user-created pages will become read-only" -> "existing classic user-created pages will become read-only for all tenants".
  5. "Existing page content" -> "Existing classic page content".
  6. "modern SharePoint experiences" -> "modern SharePoint page experiences"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the notice to be more accurate.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. "Classic SharePoint pages are being deprecated" -> Can we use "Classic user-created pages" to be more specific?
  2. "creation of new classic experiences will be restricted in certain scenarios" -> Can we use "creation of classic pages will be disabled for new tenants" to be more specific?
  3. Need to bold the two milestone dates.
  4. "existing classic user-created pages will become read-only" -> "existing classic user-created pages will become read-only for all tenants".
  5. "Existing page content" -> "Existing classic page content".
  6. "modern SharePoint experiences" -> "modern SharePoint page experiences"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the notice to be more accurate.

Updated deprecation details for classic SharePoint pages to be more accurate
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 2118aa7:

✅ Validation status: passed

File Status Preview URL Details
docs/transform/assess-sharepoint-modernization.md ✅Succeeded View
docs/transform/modernize-classic-sites.md ✅Succeeded View

For more details, please refer to the build report.

Updated deprecation details for classic SharePoint pages to be more accurate
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 90d3f71:

✅ Validation status: passed

File Status Preview URL Details
docs/transform/assess-sharepoint-modernization.md ✅Succeeded View
docs/transform/modernize-classic-sites.md ✅Succeeded View

For more details, please refer to the build report.

@liangzheng816

Copy link
Copy Markdown

Content reviewed / approved.

@liangzheng816 Liang Zheng (liangzheng816) left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed - the update looks good.

@jansenbe
Bert Jansen (jansenbe) merged commit 49869e4 into SharePoint:main Sep 1, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants