Add notice on deprecating classic sites & pages - #11011
Conversation
Updated the document to reflect changes in SharePoint Online, including deprecation timelines for classic pages and modernization guidance.
PoliCheck Scan ReportThe 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 foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 4164519: ✅ Validation status: passed
For more details, please refer to the build report. |
Added important notice regarding the deprecation of classic SharePoint pages and updated content for clarity.
PoliCheck Scan ReportThe 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 foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit c7c8252: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
- "Classic SharePoint pages are being deprecated" -> Can we use "Classic user-created pages" to be more specific?
- "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?
- Need to bold the two milestone dates.
- "existing classic user-created pages will become read-only" -> "existing classic user-created pages will become read-only for all tenants".
- "Existing page content" -> "Existing classic page content".
- "modern SharePoint experiences" -> "modern SharePoint page experiences"
There was a problem hiding this comment.
Updated the notice to be more accurate.
There was a problem hiding this comment.
- "Classic SharePoint pages are being deprecated" -> Can we use "Classic user-created pages" to be more specific?
- "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?
- Need to bold the two milestone dates.
- "existing classic user-created pages will become read-only" -> "existing classic user-created pages will become read-only for all tenants".
- "Existing page content" -> "Existing classic page content".
- "modern SharePoint experiences" -> "modern SharePoint page experiences"
There was a problem hiding this comment.
Updated the notice to be more accurate.
Updated deprecation details for classic SharePoint pages to be more accurate
PoliCheck Scan ReportThe 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 foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 2118aa7: ✅ Validation status: passed
For more details, please refer to the build report. |
Updated deprecation details for classic SharePoint pages to be more accurate
PoliCheck Scan ReportThe 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 foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 90d3f71: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Content reviewed / approved. |
Updated the document to reflect changes in SharePoint Online, including deprecation timelines for classic pages and modernization guidance.
Category
Related issues
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.