SharePoint adds HTML pages for richer site content

Microsoft is expanding SharePoint publishing with support for HTML pages. This gives organizations a new way to build interactive content directly in SharePoint, whether by prompting Copilot in SharePoint or by uploading existing HTML files and folders.

For IT teams and site owners, this matters because HTML pages now fit into the same Site Pages workflow used for modern pages, making publishing easier without introducing a separate platform.

What’s new

SharePoint HTML pages are stored in the Site Pages library and support the standard page lifecycle for editing, draft, publishing, and sharing.

Key capabilities include:

• Create with Copilot in SharePoint using natural language prompts and attached files
• Upload existing HTML content as a single file or full folder
• Automatic asset handling, with images and videos placed in Site Assets
• Direct editing on the canvas without requiring HTML coding
• Live data support from SharePoint lists, Excel, and CSV on refresh
• Built-in support for approved libraries including Chart.js, Mermaid, React, Fluent UI, and Babylon
• Page analytics and sharing using standard SharePoint capabilities
• Rich email sharing for HTML pages

New entry points are also available in the +New, +Create, and upload menus, as well as Edit in SharePoint from document libraries.

Security and admin controls

Microsoft says HTML pages are rendered in a sandboxed iFrame with Content Security Policy protections. SharePoint blocks arbitrary outbound API calls, cross-tenant communication, and CDN-hosted scripts outside the approved model.

Important admin details:

• HTML pages are enabled by default
• They cannot be disabled tenant-wide
• Site owners can disable or allow HTML files in the Site Pages library per site
• If links on a page do not open, admins may need to add domains to the site’s HTML Field Security allow list

Licensing and permissions

A Microsoft 365 Copilot license is only required for Copilot-powered creation and editing experiences. Standard tasks such as uploading HTML, editing page content directly, publishing, sharing, and viewing rely on existing SharePoint permissions.

What this means for IT admins

This update gives communications teams, project owners, and department site authors more flexibility to publish dynamic content without custom development. It also introduces new governance considerations around allowed domains, site-level HTML settings, and supported scripting patterns.

Next steps

• Check whether your tenant or site has received the feature, especially if you use the Frontier public program
• Review Site Pages library settings for Allow HTML files
• Update governance guidance for approved domains and HTML content usage
• Validate whether content authors need Copilot licenses for page generation
• Test uploaded HTML pages for branding, links, and supported scripts before broad rollout

For organizations heavily using SharePoint for internal communications, this is a notable new publishing option that blends flexibility with Microsoft’s existing security model.