Introduction: The New SharePoint and Why Information Architecture Still Matters
Hello, and welcome back to the Simply SharePoint podcast. I’m Liza Tinker—and yes, this is my first episode in a little while.
I have been busy in the best and most real way: client work, building new things, and spending a lot of time deep in the changes happening across SharePoint and Copilot. But I have missed these conversations, and I wanted to come back with an episode that is genuinely worth the wait.
Because the version of SharePoint we were talking about even a few months ago is moving quickly. Today I want to talk about what I think is one of the biggest changes in SharePoint for a very long time: the new way we can create inside SharePoint using HTML and Copilot.
Because, for years, SharePoint has been treated as one of two things.
Either it is a place where people put documents and then complain they cannot find them. Or it is a place where you need a developer, a lengthy project and a huge amount of custom work to create anything that feels useful.
That is changing.
SharePoint is becoming a place where people can create pages, libraries, lists, simple workflows, reusable skills and now richer HTML experiences with natural-language help from Copilot.
And I know that can sound incredibly exciting—and it is. But I also want to say the most important thing at the beginning:
The new SharePoint does not remove the need for information architecture. It raises the stakes for getting it right.
There is no AI without IA.
So, in this episode, I am going to break down three things:
- What the new HTML capability in SharePoint really means;
- What SharePoint Copilot can help you create; and
- The foundations you need so you do not simply generate a prettier version of a messy environment.
Let’s get into it.
SharePoint Is Becoming a Creation Environment
The old model of SharePoint was very page-and-web-part driven. You created a modern page, added the approved web parts, linked to content, used lists and libraries, and built a site over time.
That still matters. It is still the right answer for many things.
But the new model is much more flexible.
Microsoft’s current public guidance describes Copilot in SharePoint as a way to ask questions, run workflows and create sites, pages, interactive reports and Office files using natural language. For people with the relevant licence and permission, Copilot can help you work with content in files, pages, lists and libraries rather than requiring you to begin every task from a blank screen.
That is a real shift.
You can describe the outcome you want in ordinary language. You can ask for a page, improve the structure, refine content, create a view, or turn a repetitive process into a reusable skill.
But—and this is important—Copilot does not suddenly know what the right solution is for your organisation.
It can create quickly. It cannot make the business decisions for you.
It does not know which policy is the current authority just because a file has the word “final” in the name.
It does not know whether a document is appropriate to publish to all staff.
It does not know whether someone should have access to private HR documents, finance information, legal records or sensitive case information.
That is still your work. That is still the work of the content owner, site owner, information manager and business team.
So I want you to think about Copilot not as the person who replaces the work, but as the assistant who helps you carry out a well-designed process much faster.
What HTML Pages in SharePoint Actually Mean
Let’s talk about the part that has people excited: HTML.
SharePoint can now support HTML pages in the Site Pages library. A site owner needs to allow HTML files in that library first. Then, depending on permissions and licence, a page author can create an HTML page with Copilot, upload an existing HTML page, edit it, publish it and share it alongside other SharePoint pages.
That means an experience does not have to look like a standard page with the same familiar collection of web parts.
You can create richer layouts, interactive reports, visual status pages, project summaries, team profile pages, timelines, FAQs and branded internal experiences.
And this is where it gets very interesting.
The new SharePoint HTML experience can support live data sharing with SharePoint lists and Excel. So you can imagine a project list becoming a visual project-status page. You could have milestones, risks, filters and links back to the source records—all inside a SharePoint-safe experience.
That is powerful. But I want to be very clear about the words SharePoint-safe.
An HTML page in SharePoint is not a blank, unrestricted web server.
Microsoft’s published guidance explains that SharePoint renders these pages in a sandboxed iframe and applies content-security controls. You cannot simply point the page at any external API, use arbitrary fetch requests or load whatever script library you find online.
That is not a limitation to complain about. It is a design boundary.
It is there because a trusted internal site cannot be a place where anyone can quietly run unknown scripts, pull data from random services or create a security and support problem for the organisation.
So the question is not: “Can I use HTML to build absolutely anything?”
The better question is: “Can I use HTML to make the information and work already inside SharePoint more useful, clearer and more engaging?”
For many organisations, the answer is absolutely yes.
Start with Trusted Data Before Building a Dashboard
Here is the trap I want you to avoid.
You see HTML, you see Copilot and you immediately think: “We are going to rebuild the intranet.”
Please do not start there.
Start with one clear, contained job that is already supported by a list or library.
For example, imagine you have a project-delivery team. They already have a SharePoint list of projects. In theory, that list contains the project name, sponsor, delivery lead, phase, status, milestone date, risk level and next decision.
The problem is that the list is not being maintained properly. Half the statuses are inconsistent. Some projects have no owner. Dates are blank. People have created their own values. The leadership team does not trust it, so they export it to PowerPoint every month.
In that state, generating a beautiful HTML dashboard does not solve the problem.
It gives you a beautiful dashboard built on unreliable data.
Instead, start with the list itself.
Ask these questions:
- What decision does this list support?
- Who updates it?
- Who owns its accuracy?
- What are the five or six fields leadership actually needs?
- Which values are standard?
- When is the information reviewed?
- What must never be shown to a broader audience?
Then make the list trustworthy first.
Once the foundation is clear, an HTML page becomes incredibly valuable. It can make the right information easier to see. It can give leaders a live summary. It can link them to the source records. It can make the experience easier to use than a giant grid of data.
But it is still only as good as the list beneath it.
The page is the experience layer. The list or library is the information layer. The owner is the accountability layer.
That is the new SharePoint in one sentence.
A Practical Copilot Prompt for an HTML Project Status Page
Let me give you a sensible example.
You have a trusted project list. It has clear fields, named owners and agreed status values. You want a leadership-facing project update page.
You could begin with a prompt such as:
“Create an HTML project status page for this SharePoint site. Use the Project Delivery list as the source. Show a leadership summary, projects by status, upcoming milestones, key risks and links back to the source items. Use our navy, teal and pink brand colours. Keep the page accessible and concise. Do not show confidential notes or content marked for internal delivery-team use.”
Then you review the draft.
You check the labels. You check the information shown. You make sure the page is not claiming something is on track just because a field was blank. You check that the links work. You make sure the right people can view it.
And then you publish it only when it is ready.
That review step matters.
Copilot can generate a first draft. It cannot be the approver.
It cannot be the privacy officer.
It cannot be the person who decides whether the status is true.
It cannot be the content owner.
It can help you get from an approved source to a useful experience faster.
That is the opportunity.
Copilot Skills: Repeatable Workflows for You and Your Team
The second thing I want you to watch is skills.
In SharePoint Copilot, a skill is a repeatable, multi-step workflow saved as something you can reuse.
There are personal skills and site skills.
A personal skill is for the way you work. It is stored in your OneDrive and can follow you across supported SharePoint experiences. You might use it to turn long documents into an executive briefing with the same headings every time: summary, decisions, risks, open questions and next steps.
A site skill is for the way a team needs to work consistently on one site. It is stored in the site’s Agent Assets library and is managed by the site administrator.
This is where your information architecture, your operating standards and your governance become incredibly useful.
Because a good skill is not “do magic.”
A good skill is a clear, repeatable instruction that says:
- What content it applies to;
- What it should assess or create;
- What output it should produce;
- What it must not decide; and
- When a human needs to review the result.
For example, a site skill could help a project team review a set of status updates and create a weekly draft summary. But it should not invent a red-amber-green status, approve a project change or share restricted content with people who should not see it.
The skill works within the permissions of the person using it. It does not expand access.
That is one of the most important governance points in this entire conversation. AI does not remove the need for permissions. It makes it more important to understand them.
Building the Foundations: Trusted Sources, Useful Experiences and Governance
So if I were helping an organisation take advantage of this new SharePoint, I would not begin with a prompt.
I would begin with a sequence.
First: Choose One Useful Business Outcome
Not “we need an AI site.”
Choose something real, such as:
- Staff need to find the current policy;
- Project leaders need to see an accurate delivery position;
- HR needs a clear source for current manager guidance;
- Finance needs a trusted current library of templates and processes; or
- A marketing team needs a single view of approved campaign material.
Second: Make the Source Trustworthy
Give it a clear home. Give it a purpose. Use natural-language file names. Select only the metadata that helps people find, understand, review or act. Name an owner. Set a review date where it matters. Separate current content from drafts, work in progress and historic material.
Third: Create the Useful Experience
This is where standard modern pages, lists, libraries, views, HTML pages and Copilot can all play a role.
Choose the lightest solution that makes the work easier.
Fourth: Build Governance into the Working Experience
Do not write a governance document and put it on a shelf.
Make it visible in the solution:
- Ownership is a field;
- Review dates are visible;
- Overdue content has a view;
- Staff can find the current source;
- Restricted content is not in the same place as general staff content;
- A person knows what action they need to take next.
That is how the solution stays useful after the initial excitement has gone.
Your Starting Point: Five Steps for One List or Library
If you are listening and thinking, “Right, where do I start?” here is the simple plan.
Pick one existing site or document library. Not your entire intranet. Not all of Microsoft 365.
Choose an area where people are already struggling to find, trust or use information.
Then do five things:
- Write a one-sentence purpose for that library or list.
- Name the accountable business owner.
- Clean up natural-language file names and remove version codes from names by using version history instead.
- Create a small, useful set of metadata fields—such as Document Type, Business Area, Content Owner, Content Status and Next Review Date.
- Create a clear current-content view before you create a flashier page on top of it.
Once that is working, trial one Copilot use case.
Maybe it is creating a simple HTML status page.
Maybe it is generating a draft FAQ from a trusted source.
Maybe it is building a reusable site skill for a repeated process.
Maybe it is helping you create a review view or summarise a small selected set of documents.
Start small. Test it. Review the output. Keep the human in the loop.
Then you can scale what works.
Final Thoughts: There Is No AI Without IA
The new SharePoint is not just a place to store files.
It is becoming a place where trusted information, visual experiences, workflows and AI-assisted work can sit together.
That is exciting.
But the organisations that get the best outcomes will not be the ones that generate the most pages or build the fanciest dashboard first.
They will be the ones that create clear boundaries, trusted sources, natural-language names, useful metadata, visible owners and sensible review routines.
Then they will use Copilot and HTML to make that work easier, faster and more useful for people.
That is the opportunity.
And that is why there is no AI without IA.
If you want a practical starting point, join my free Clean Up Your SharePoint Library in 7 Days Challenge. It takes you through one real document library, one practical step at a time. You will find the link in the show notes.
And if you need a complete, self-paced system for a Policy Hub, Project Hub, Intranet, HR, Finance, Marketing or Events solution, explore the Simply AI Ready Blueprints at simplyaiready.com.
Thanks for listening. I’m Liza Tinker, and I’ll see you next time.