SharePoint HTML Pages Are Here

When I first spotted Roadmap ID 569208, my immediate reaction was not excitement about HTML. It was curiosity about what this might mean for the future of SharePoint publishing.

According to the roadmap, users will be able to create HTML with Copilot in SharePoint or upload HTML from another source, store it in the SharePoint Pages library, render it as a page, edit it, and share it with others. Microsoft describes this as an option alongside existing ASPX pages.

On the surface, that sounds like another page feature. Looking a little deeper, it raises some interesting questions about content creation, governance, ownership, and where Copilot fits into the publishing experience.

More Than Just Another Page Type

Modern SharePoint pages have become the standard publishing experience for most organisations. They are structured, familiar, and relatively easy to govern. Web parts, templates, page approvals, metadata, and permissions all fit neatly into an established model.

HTML pages appear to introduce something different.

The roadmap suggests organisations may be able to generate HTML through Copilot or bring existing HTML content into SharePoint and publish it as a rendered page. That creates opportunities for richer layouts, migration scenarios, training content, campaign sites, and specialised presentations that do not always fit naturally within the standard page canvas.

What makes this interesting is not the HTML itself. Many organisations already have HTML content sitting in documentation platforms, legacy intranets, learning systems, or developer-created prototypes. The possibility of bringing that content into SharePoint could become a practical bridge between existing investments and modern Microsoft 365 publishing.

Where Copilot Changes the Conversation

The mention of Copilot may prove to be the most significant part of the announcement.

If Copilot can help generate HTML from prompts, outlines, policies, or source documents, content creators may be able to move from idea to first draft much faster. An onboarding checklist could become a structured landing page. A policy document could become an explainer page with FAQs and navigation links.

That does not remove the need for review.

Content owners will still need to validate accessibility, branding, permissions, accuracy, and compliance requirements before publishing. Copilot may accelerate creation, but accountability remains with the publisher.

The Questions Administrators Should Be Asking Now

The technology story is straightforward. The governance story is more complicated.

If HTML pages become widely available, organisations should think beyond functionality and start considering ownership and control.

Questions worth asking include:

• Who can create HTML pages?
• Who can upload externally generated HTML?
• Will approval workflows be required?
• How will page ownership be tracked?
• What happens when the original author leaves?
• What accessibility checks will be mandatory?
• Will HTML pages be allowed everywhere or only in selected sites?

These are not reasons to avoid the feature. They are reasons to approach it thoughtfully.

Flexibility Comes With Responsibility

Accessibility, security, and supportability should be part of the conversation from the beginning.

Traditional SharePoint pages benefit from Microsoft-managed components and established design patterns. Custom HTML introduces additional responsibility around semantic structure, navigation, alternative text, colour contrast, and long-term maintenance.

Security considerations are equally important. Microsoft has not yet published complete implementation details, so organisations should avoid assumptions around supported scripts, external resources, rendering behaviour, or administrative controls.

What I’ll Be Watching

The roadmap provides an interesting glimpse of what’s coming, but some of the most important details are still unknown.

I’d like to see how HTML pages interact with search, metadata, approvals, comments, templates, and existing SharePoint publishing capabilities. I’m also interested in understanding how much control administrators will have over adoption and governance.

For now, I see SharePoint HTML Pages as a potentially useful addition rather than a replacement for modern pages.

Resources

• Microsoft Support: Create, upload, edit, and publish HTML pages in SharePoint
• Microsoft 365 Message Center: SharePoint: HTML pages (MC1479517)

If this feature reaches its potential, it could give organisations a new publishing option that sits somewhere between standard SharePoint pages and fully custom development.

Community Discussion

• What do you think? Would HTML pages solve a genuine business need in your organisation, or do they introduce governance challenges you would rather avoid?
• How would you decide when to use an HTML page instead of a modern SharePoint page?