SharePoint HTML pages need governance before wider adoption
Diesen Beitrag auf Deutsch lesen
HTML pages could expand SharePoint publishing, but organisations must define ownership, review, accessibility, security and administrative controls first.
TL;DR
SharePoint HTML pages may be created with Copilot or uploaded from another source, stored in the SharePoint Pages library, rendered, edited and shared. Before publishing, content owners must validate accessibility, branding, permissions, accuracy and compliance, while administrators should define creation rights, approval workflows, ownership tracking and site availability.
Original by Josiah Opiyo, on Microsoft 365 and Power Platform Community Blog. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Validate accessibility, branding, permissions, accuracy and compliance before publishing HTML created with Copilot or uploaded from elsewhere.
- Admins/CoE: Define who can create or upload HTML, whether approvals are required, how ownership is tracked and where pages are allowed.
- Security/Compliance: Avoid assumptions about scripts, external resources, rendering behaviour and administrative controls because implementation details are not complete.
Frequently asked questions
How can HTML pages be created and stored in SharePoint?
Users may create HTML with Copilot or upload it from another source, then store it in the SharePoint Pages library for rendering and editing.
What checks should content owners perform before publishing SharePoint HTML pages?
Content owners should validate accessibility, branding, permissions, accuracy and compliance before publishing an HTML page.
Which governance controls should administrators define for SharePoint HTML pages?
Administrators should determine who can create or upload pages, whether approvals are needed, how ownership is tracked and which sites permit HTML pages.