The New SharePoint: HTML Pages, Copilot and Why Information Architecture Comes First
SharePoint now supports rich HTML pages, live list data and Copilot-assisted page creation. Here is how to use these capabilities safely without generating a prettier version of an unorganised environment.
- Site Pages library configured by site owner to allow HTML files
- Source list or library with natural-language column names already established
- No tenant-wide scripting restrictions blocking sandboxed iframes
1. What HTML in SharePoint actually is
For years, creating an engaging internal experience in SharePoint meant relying on standard modern page web parts or commissioning a developer for custom SPFx solutions. Modern SharePoint now supports HTML pages directly in the Site Pages library.
A site owner can enable HTML support, allowing page authors to create, upload, edit and publish HTML experiences alongside standard SharePoint pages. These pages can connect with live SharePoint list data and Excel tables, enabling interactive dashboards, team profile pages, and visual status summaries without leaving the security of your Microsoft 365 tenant.
An HTML page in SharePoint runs in a sandboxed iframe with strict Content Security Policy controls. It cannot query arbitrary external APIs or execute untrusted third-party scripts. This boundary protects enterprise data integrity.
2. The foundation before the prompt
The greatest trap with AI-assisted design is jumping straight into generation. If your source project list has inconsistent status values, missing owners and outdated dates, Copilot will simply render an elegant dashboard on top of unreliable data.
Before drafting the HTML experience, ensure your list has a one-sentence stated purpose, named business owners for every entry, and standardized status values. When the information foundation is trustworthy, Copilot becomes an extraordinary accelerator.
3. The tested Copilot prompt
Open Copilot Chat from within your SharePoint site and use this specific, bounded prompt to create the initial status page structure:
4. Reviewing before publication
Copilot can generate the layout and wire the data bindings, but it cannot verify whether the reported project health is accurate or whether a milestone date is realistically achievable. A designated human owner must review the draft before sharing it with leadership.
Once published, set a monthly calendar review to confirm the page continues to reflect current working priorities.
Human Review Checks (Always Perform Before Sharing)
- ✓Confirm the source SharePoint list has restricted permissions matching the intended audience
- ✓Check that empty fields display graceful fallbacks rather than broken code tags
- ✓Ensure an accountable human content owner is clearly identified on the published page
Project Management Hub
Give project teams one practical home for decisions, delivery status and the work that must not get lost. Complete step-by-step Copilot Chat prompt package and manual fallback.
Related Copilot Guides & Workflows
How to Build Personal and Site Skills in SharePoint Copilot
Personal and site skills turn repeated prompts into predictable, one-click workflows. Learn how to package team processes into reusable skills without compromising permissions.
Executive Briefings in 20 Minutes: An AI Workflow for Business Support Teams
A step-by-step workflow for executive assistants and coordinators to turn multi-page project updates, board packs and papers into clear, decision-focused briefings.