Copilot Cowork helps execute work, not just answer prompts.
You delegate outcomes; Cowork plans and carries the task forward.
It works across Microsoft 365 (Outlook, Teams, Word, Excel, SharePoint).
You stay in control with approvals and check‑ins.
It uses your existing permissions and data.
Messy M365 = messy results (Cowork highlights the cracks).
Availability is limited via Microsoft’s Frontier program.

If you’ve been using Copilot, you know you can use it for answering questions, summarising documents, and drafting the first version of… anything really.

Copilot Cowork is different.

Instead of helping you think, Copilot Cowork is designed to help you get things done.

Not in a sci‑fi, “AI replaces your job” way. More like a very capable team member who can:

Take a task
Break it into steps
Work across numerous platforms (Outlook, Teams, Word, Excel, SharePoint and any integrated workloads)
Check in when it needs guidance
And keep going in the background while you focus elsewhere

Microsoft describes Copilot Cowork as being built for long‑running, multi‑step work, not just quick answers or single prompts.

If regular Copilot is like asking a colleague a question, Copilot Cowork is like delegating the task and saying, “Can you run with this?”

So… what is Copilot Cowork?

Copilot Cowork is an execution layer inside Microsoft 365 Copilot.

You describe the outcome you want, and Cowork:

Turns that request into a plan
Uses your emails, meetings, chats, files, and data to do the work
Carries tasks forward over time
Shows progress and asks for approval before making changes

All of this happens within your Microsoft 365 tenant, using your existing permissions and security model.

Think of it like this:

Regular Copilot is a great assistant sitting next to you.

Copilot Cowork is a teammate who can actually leave the room and do the work.

Importantly, you don’t lose control. Cowork:

Flags what it plans to do
Pauses for approval
Checks in when something is unclear
Let’s you steer or stop at any point

You’re still in charge. You’re just no longer doing every step yourself.

What can Copilot Cowork do?

This is where it gets practical.

Copilot Cowork is designed to work across apps, not inside a single one. Microsoft has shown Cowork handling things like:

Coordinating work across tools

Cowork can reason across Outlook, Teams, Excel, Word, SharePoint and your calendar, pulling context from all of them at once.

For example:

Review recent emails and Teams chats
Pull relevant documents from SharePoint
Draft a summary in Word
Create a data table in Excel
Prep a deck in PowerPoint

All from one instruction.

Turning intent into action

Instead of “summarise this doc”, you can ask things like:

“Prepare me for next week’s exec review”
“Clean up my calendar and protect focus time”
“Pull together a status update for stakeholders”

Cowork builds a plan, executes it step by step, and keeps you looped in.

Handling longer‑running tasks

Cowork isn’t limited to a single prompt-and-response moment.

Tasks can run for minutes or longer, carry on in the background, and continue even while you’re doing other work, with visible progress along the way.

That’s a big shift from the Copilot many people are used to.

What do you need to make Copilot Cowork work properly?

Here’s the part people sometimes skip. And regret later.

Copilot Cowork doesn’t magically fix a messy Microsoft 365 environment.

It uses what it can access.

That means everything that already matters for Copilot readiness matters here too.

Permissions still rule

Cowork respects your existing permissions.

Which is great, if your permissions are set up properly.

If not, Cowork can surface:

Outdated content
Overshared documents
Confusing or conflicting information

Same rules, bigger spotlight.

Structure matters more than ever

Copilot Cowork works best when:

SharePoint sites are clear and purposeful
Content lives where people expect it
Files aren’t duplicated across twenty folders “just in case”

AI doesn’t hate mess.

But it also doesn’t tidy it up for you.

Content quality affects output quality

Cowork isn’t inventing knowledge. It’s working with your information.

If documents are:

Out of date
Vaguely named
Missing context

Cowork will still produce confident answers, just not always the right ones.

In other words: Copilot Cowork readiness is Copilot readiness.

Cowork simply raises the stakes.

When is Copilot Cowork available?

Right now, Copilot Cowork is not generally available to everyone.

As of March–April 2026:

Copilot Cowork is available through Microsoft’s Frontier program
Access is limited to organisations enrolled in that early-access channel
Even then, it may only be enabled for selected users or roles

This means:

You can have Microsoft 365 Copilot and still not see Cowork
You can hear people talk about it before IT enables it
You may need both the right licence and the right tenant settings

That staged rollout is intentional. Cowork touches real workflows, not just drafts and summaries.

The bottom line

Copilot Cowork is not “just another Copilot feature”.

It’s Microsoft signalling a shift from:

“AI helps you do your work faster”
to
“AI helps carry the work forward with you.”

It's what Microsoft is calling the 3^rd wave of AI, agentic capability.

That’s powerful, and genuinely helpful, when the foundations are in place.

If your Microsoft 365 environment is well-structured, secure, and understood, Copilot Cowork can feel like gaining an extra pair of hands.

If it isn’t?

Cowork doesn’t hide the cracks. It highlights them.

FAQs: Copilot Cowork

What is Copilot Cowork?

Copilot Cowork is an execution layer within Microsoft 365 Copilot that helps carry work forward over time. Instead of just responding to a prompt, it turns your goal into a plan and executes it step by step.

How is Copilot Cowork different from regular Copilot?

Regular Copilot helps you think and draft. Copilot Cowork helps you delegate and execute. It’s designed for long‑running, multi‑step work rather than quick questions or single responses.

What kinds of tasks can Copilot Cowork handle?

Copilot Cowork can coordinate work across multiple Microsoft 365 tool, for example:

Reviewing emails and Teams chats
Pulling documents from SharePoint
Creating summaries, tables, or presentations
Preparing updates or reviews from multiple sources. All from one instruction.

Does Copilot Cowork work in the background?

Yes. Tasks can run for minutes or longer, continue in the background, and show visible progress while you work on other things.

Do I still have control over what Copilot Cowork does?

Yes. Copilot Cowork:

Shows what it plans to do
Pauses for approval
Checks in when something is unclear
Allows you to steer, stop, or change direction at any time. You remain responsible for the outcome.

Does Copilot Cowork respect Microsoft 365 permissions?

Yes. Copilot Cowork works entirely within your Microsoft 365 tenant and uses your existing permissions and security model. It can only access information you already have access to.

Will Copilot Cowork clean up my SharePoint or files for me?

No. Copilot Cowork does not fix poor structure, oversharing, or outdated content. Instead, it surfaces whatever is already there. Good or bad.

What happens if our content or permissions are messy?

Cowork will still produce outputs, but they may be based on:

Outdated documents
Conflicting information
Overshared or poorly structured content. The more complex the task, the more visible these issues become.

What do we need to be “Copilot Cowork ready”?

The same things are needed for Copilot readiness:

Clear, purposeful SharePoint sites
Logical content locations
Well‑governed permissions
Up‑to‑date, well‑named documents with context.

Copilot Cowork simply raises the stakes.

Sources

Copilot Cowork: A new way of getting work done
https://www.microsoft.com/en-us/microsoft-365/blog/2026/03/09/copilot-cowork-a-new-way-of-getting-work-done/
Copilot Cowork: Now available in Frontier
https://www.microsoft.com/en-us/microsoft-365/blog/2026/03/30/copilot-cowork-now-available-in-frontier/
Get started with Copilot Cowork (Frontier)
https://support.microsoft.com/en-us/topic/get-started-with-copilot-cowork-frontier-60be4cea-b913-471b-a0d8-f9ab73c6b0be
Microsoft Copilot Frontier program
https://www.microsoft.com/en-us/microsoft-365-copilot/frontier-individuals

TL;DR

If no one’s using your new tool, it’s not a tech problem. It’s a change problem
Go‑live is the starting line, not the finish
Announcing a tool doesn’t mean people understand how to use it
Adoption grows when people see how it helps their day‑to‑day work
Role‑based training and real examples matter more than big demos
Ongoing reminders and visible support drive usage
Adoption takes time, and that’s normal

Dear WebVine,

We launched a new digital tool. We announced it everywhere. And now… crickets. What did we do wrong?

We invested in a new digital tool, that would fix a real problem. We researched options, worked hard on the rollout, and made sure everyone knew about it.

It was announced. It was demoed. There was even cake….

But weeks later, hardly anyone is using it. Some people say they “forgot about it”. Others say they’ll “get to it one day”. A few didn’t even realise it had launched.

We’re confused, frustrated, and honestly a bit deflated. The tool is good. How do we make sure everyone uses it? Is it the wrong tool?

Chloe’s Take

Dear Perplexed,

First of all: you didn’t fail. Second: this is incredibly common.

And let me start by saying this: if I had a dollar for every time I heard “We launched it, but no one’s using it”, I’d be writing this from a very comfortable beach somewhere.

Unfortunately what you’re experiencing isn’t a technology problem. It’s a change problem.

Think of it like buying a top-of-the-range treadmill. You unbox it. You admire it. You tell everyone you’re “definitely going to use it”. And then… it becomes a very expensive clothes rack.

The treadmill didn’t do anything wrong. Neither did you.

But intention ≠ adoption.

One of the biggest myths in digital projects is the idea that go-live = success.

In reality, go-live is just the starting line.

From your perspective, the tool is “out there”. From your users’ perspective, it’s just one more new thing competing with emails, meetings, deadlines, and actual work.

People don’t resist change because they’re difficult. They resist change because:

they’re busy
they’re unsure
or they don’t yet see how this helps them

Change doesn’t stick because it exists. It sticks because it makes sense in someone’s day-to-day life.

Announcement ≠ understanding

You mentioned that you announced the tool, demoed it, and shared the news widely.

That’s all important. But here’s the tricky bit:

People rarely understand a new tool just because they’ve been told about it.

A demo shows what a tool can do.

Training shows people how they should use it.

Reinforcement shows them when and why it matters.

Without that middle and last piece, tools often feel optional… or easy to ignore.

So what can you do now? (Yes, you can absolutely recover this)

The good news? You don’t need to start again. You need to shift from launch mode to adoption mode.

Here are a few practical, low-drama ways to do that:

1. Reframe the “why”. In human terms

Instead of talking about features, talk about friction.

What will this save people time on?
What annoying task does it reduce?
What problem does it quietly solve?

If people can’t answer “What’s in it for me?” in about five seconds, usage will stay low.

2. Train for real work, not ideal scenarios

Generic demos rarely stick.

Short, role-based training does.

Show:

“If you’re in finance, here’s how this helps you on a Tuesday afternoon.”
“If you’re on the frontline, here’s where this fits in your actual workflow.”

Even ten focused minutes beats an hour of broad explanation.

3. Make it visible after launch

Silence after go-live results in the tool falling off the radar.

Try:

quick reminders
spotlighting small wins
sharing real examples of people using it successfully

Adoption grows when people see peers using the tool. Not just leadership endorsing it.

4. Support beats perfection

People don’t avoid new tools because they hate them. They avoid them because they’re worried about getting it wrong.

Make support:

obvious
friendly
judgement-free

“Ask us anything” beats “Read the documentation” every time.

5. Expect adoption to take time

This one’s important. And often overlooked.

Change is a curve, not a switch.

Most tools don’t suddenly “take off”. They grow gradually, with nudges, reminders, and reinforcement.

If you plan only for launch and not for the weeks (or months) after, adoption is left to chance.

One last thing (and it’s a big one)

Post-implementation work isn’t a nice-to-have. It’s where most of the value lives.

You’ve already done the hardest part: getting the tool in place. Now it’s about helping people feel confident, capable, and supported enough to use it.

Its kind-of simple, but not easy.

Good luck!
— Chloe

About Chloe:

Chloe Dervin is WebVine’s Managing Director and resident intranet whisperer.

With a background in digital strategy and a knack for translating tech into plain English, Chloe helps organisations untangle their messiest SharePoint setups and turn them into something people want to use.

She’s worked with everyone from local councils to fast-growing engineering firms, and she’s seen it all. From “Final_v2_REAL_final.docx” nightmares to intranets that haven’t been touched since 2011.

Her superpower? Making the complex feel doable, and helping teams move from “we’re flying blind” to “we’ve got this.”

When she’s not rewriting the rules of digital workplaces or penning her latest “Dear WebVine,” Chloe is making work, work for everyone.

WebVine was featured on Microsoft’s SharePoint Partner Showcase, highlighting how we build modern digital workplaces on Microsoft 365.
The showcase focused less on shiny features and more on approach, extending SharePoint sensibly, not replacing it.
Microsoft called out the polish, clarity, and usability of Injio and Injio Docs, especially how complexity is hidden from everyday users.
The session explored WebVine’s practical approach to Copilot readiness, starting with content quality and structure before AI.
We shared how tools like PAT (Page Assessment Tool) and CAT (Copilot Assessment Tool) make readiness visible, measurable, and manageable.
Being selected for the showcase reinforces WebVine’s long‑standing philosophy: build with the platform, simplify without dumbing down, and design for the long term.

We were proud to be featured by Microsoft in a recent SharePoint Partner Showcase, where Vesa Juvnoen (Microsoft Principal Product Manager) sat down with WebVine to walk through how we design, build and evolve modern digital workplaces on Microsoft 365, including Injio, Injio Docs, and our focus on Copilot readiness.

For us, it was a meaningful moment, because it reinforced how we’ve always chosen to work.

You can watch the full Microsoft showcase video below. If you prefer to read, scroll down to our summary.

Built the way SharePoint is meant to be built

One theme came through clearly during the session: the solutions Microsoft highlights are the ones that extend SharePoint rather than fight it.

That philosophy has guided WebVine since we started working with SharePoint back in 2010.

We don’t build platforms beside Microsoft 365. We don’t replace what works. And we don’t create complexity for the sake of customisation.

Instead, we focus on layering clarity, structure and usability on top of SharePoint’s native capabilities. So, organisations can move faster, with less risk, and without painting themselves into a corner.

Think of it like fitting out a well-designed workspace. You’re not knocking down load‑bearing walls. You’re improving how people use the space every day.

More than products: an approach shaped by people

While Injio and Injio Docs were demonstrated during the showcase, the conversation was really about how WebVine approaches digital workplace problems.

Our team was represented by:

Chloe Dervin, Managing Director
James Dellow, Head of Delivery & Product

Between them, they brought together delivery experience, product thinking, and a very practical understanding of what organisations are up against.

We’ve worked with teams who:

Just want their intranet to make sense
Are exhausted by fragile workflows and approvals
Are being asked about Copilot readiness without knowing where to start

That reality shapes every decision we make. From architecture choices through to how much abstraction we add for business users.

“We’re proud Microsoft said this about us”

One of the most affirming parts of the showcase was hearing Microsoft reflect on what they saw during the demo.

A few moments stood out for us.

On Injio’s intranet experience:

“Beautiful looking stuff, super polished.”

On Injio Docs:

“Nice clean implementation, beautiful looking stuff.”

On simplifying complex processes for everyday users:

“The key value here… is the end user doesn’t have to go into Power Automate and understand which step in that complex set‑up they need to modify. Most business users don’t have that skill set. So having that simplification is really nice.”

And on the overall design approach:

“I like the fact that it’s using all the out‑of‑the‑box features and capabilities, but with a simplified layer on top. Adapting it in a more customer‑friendly way.”

For us, those comments mattered because they reflect exactly what we aim for: solutions that feel polished without being heavy, and powerful without being fragile.

Copilot readiness: starting with the fundamentals

The showcase also gave us the chance to talk about an area we’re spending a lot of time on with clients: Copilot readiness.

Not from a “turn it on and hope” perspective. But from a content and structure one.

Why structure still matters (even with AI)

Copilot doesn’t magically fix messy content.
It amplifies what’s already there.

That’s why our approach to Copilot readiness starts with the fundamentals:

Is content well structured?
Is it readable by humans?
Does metadata actually mean something?

During the session, James walked through two tools that support that thinking.

PAT and CAT: making readiness visible and measurable

Page Assessment Tool (PAT)

The Page Assessment Tool (PAT) looks at individual SharePoint pages and scores them against clear, transparent criteria. Things like layout, structure and readability.

It combines:

Mechanical scoring, to keep results consistent
Copilot‑assisted feedback, to explain why something scored the way it did

Microsoft described this as a strong, responsible use of AI. Guiding improvement rather than guessing.

It’s the difference between “this page isn’t great” and “here’s what to fix, and why.”

Copilot Assessment Tool (CAT)

The Copilot Assessment Tool (CAT) takes that same logic and applies it at scale.

Instead of reviewing content one page at a time, CAT:

Scans large sets of intranet and knowledge content
Groups pages by readiness and priority
Helps teams focus where effort will make the biggest difference

Microsoft called this out as a great use case for AI: analysing, pre‑checking and presenting information in a way that makes delegation and improvement easier. Not harder.

Supporting readiness

What we were most pleased to see reflected in the conversation was alignment.

Microsoft spoke positively about an approach that:

Improves content for people first
Uses AI as an assistant, not a crutch
Makes quality measurable, visible and manageable

That’s the same approach we take with clients every day.

Copilot readiness isn’t a switch you flip.

It’s something you build towards. One decision, one page, one improvement at a time.

A moment of validation and a signpost forward

Being featured on the SharePoint Partner Showcase was a proud moment for the WebVine team. Its a huge validation of the path we’re already on.

Build with the platform.

Simplify without dumbing down.

Design for the long term.

And help people do their jobs with confidence.

If you’re navigating intranet improvements, document governance, or Copilot readiness and want a practical, human take on what helps, we’re always happy to talk.

Frequently Asked Questions

Why was WebVine featured on Microsoft’s SharePoint Partner Showcase?

Microsoft uses the SharePoint Partner Showcase to highlight partners who build in ways that align with how SharePoint and Microsoft 365 are intended to be used.
WebVine was featured for its practical, sustainable approach to intranets, document management, and Copilot readiness, extending SharePoint rather than fighting it.

What is the SharePoint Partner Showcase?

The SharePoint Partner Showcase is a Microsoft‑run series that highlights real partner solutions and approaches built on SharePoint Online, SharePoint Framework (SPFx), and the Power Platform. It focuses on real‑world implementation, not marketing demos.

How does WebVine approach Copilot readiness differently?

WebVine doesn’t treat Copilot as a switch you turn on.
Our approach starts with the fundamentals:

Clear structure
Readable, well‑written content
Meaningful metadata

Copilot then becomes far more effective, because it’s working with quality inputs.

What are PAT and CAT?

PAT (Page Assessment Tool) assesses individual SharePoint pages against clear criteria like structure and readability, combining mechanical scoring with Copilot‑assisted feedback.
CAT (Copilot Assessment Tool) applies the same thinking at scale, scanning large volumes of content to highlight readiness, priorities, and focus areas.

Together, they help organisations move from guessing about readiness to making informed, practical improvements.

TL;DR

WebVine is now a Microsoft Solutions Partner for Modern Work, recognising our real world delivery across Microsoft 365
This status is earned through proven customer outcomes, not marketing claims
It reflects strong results across SharePoint, Teams, governance, adoption, and Copilot readiness
For you, it means lower risk, better foundations, and a partner Microsoft independently backs
Most importantly, it confirms what our clients already experience: Modern Work that works

We’re excited to share a milestone for WebVine: we’ve officially achieved Microsoft Solutions Partner for Modern Work.

Exciting? YES! It’s Microsoft formally recognising the quality, consistency, and real world impact of the Modern Work solutions we deliver for our clients across Microsoft 365.

Think of it like a trusted referee stepping in and saying, “Yep, these folks know what they’re doing, and they do it well.”

What does “Solutions Partner for Modern Work” mean?

Microsoft overhauled its partner program, replacing the old Gold and Silver badges with the Solutions Partner model. The bar is higher, and much more practical.

To earn this designation, partners must prove they can deliver real outcomes for clients, and undertake extensive training.

For the Modern Work designation, it covers things our clients care deeply about, including:

SharePoint Online and intranets that people actually use
Microsoft Teams collaboration that supports real work (not chaos)
Clear information architecture and governance
Adoption, change, and ongoing usage across Microsoft 365

Microsoft doesn’t just take our word for it. This recognition is based on verified delivery, certifications, and measurable customer outcomes across live Microsoft 365 environments.

Why this matters to you

If you’re choosing a partner for SharePoint, Microsoft 365, or Copilot readiness, this designation should give you confidence.

Here’s why.

You’re choosing a partner Microsoft independently backs

This is Microsoft effectively saying: WebVine consistently delivers strong Modern Work outcomes.

That matters when you’re investing time, budget, and trust into platforms that underpin how your organisation works.

You benefit from best‑practice foundations (without the guesswork)

We stay closely aligned to Microsoft’s evolving guidance across governance, architecture, adoption, and Copilot‑ready foundations.

For you, that means fewer dead ends, less rework, and solutions built to last, not quick fixes that unravel later.

You get outcomes, not just technology

The designation reflects what our clients tell us matters most: clarity, usability, and genuine adoption.

We don’t believe in rolling out tools and hoping people figure them out. We focus on making Modern Work actually work.

You’re backed by a partner in it for the long haul

This status isn’t permanent. It has to be maintained.

That means ongoing learning, delivery, and improvement on our side, so you’re supported by a partner who’s invested for the long term, not just the project go‑live.

What got us here

This milestone is the result of a huge amount of care, effort, and teamwork, from both our clients and our people.

It reflects:

High quality Microsoft 365 and SharePoint delivery
Strong adoption and change outcomes
A consistent focus on governance, information architecture, and content quality
Strategic alignment to Modern Work and Copilot foundations across everything we do

Most importantly, it’s a testament to our team.

So a genuine thank you to everyone at WebVine who’s contributed to this. Through thoughtful delivery, continuous learning, and a shared commitment to doing Modern Work properly.

If you’re curious about what this means for your own Microsoft 365 environment, or want a practical view of how ready you are for what’s next, we’re always happy to have a chat.

FAQs

What is a Microsoft Solutions Partner for Modern Work?

A Microsoft Solutions Partner for Modern Work is a partner Microsoft recognises for consistently delivering strong results across Microsoft 365, including SharePoint, Teams, information management, adoption, and collaboration.

It replaces the old Gold and Silver partner badges and focuses on real customer outcomes, not just certifications or sales volume.

In simple terms: it’s Microsoft independently confirming that a partner knows how to design, deliver, and sustain Modern Work environments that get used.

Why did Microsoft replace Gold and Silver partners?

Microsoft updated its partner program to better reflect how organisations really use Microsoft 365 today.

Instead of rewarding partners for volume or legacy criteria, the Solutions Partner model focuses on:

Real‑world delivery
Ongoing customer usage
Skills that stay current as Microsoft evolves

For customers, this makes it easier to identify partners who can support Modern Work beyond go‑live.

Why is the Solutions Partner for Modern Work designation hard to get?

Because it’s earned through consistent, long‑term customer success.

Microsoft looks at whether:

Customers are actively using the solutions delivered
Adoption holds up over time (not just at launch)
The partner team has the right skills, and keeps them up to date
Outcomes are delivered across multiple client environments

It’s not a form you fill in or a one‑off submission. It reflects sustained delivery across real Microsoft 365 tenants.

What does this mean for me as a client of WebVine?

It means confidence and reduced risk.

When you choose a Microsoft Solutions Partner for Modern Work, you’re choosing a partner that Microsoft independently backs for delivering quality outcomes, not just deploying tools.

For you, that means:

Stronger foundations for SharePoint, Teams, and Microsoft 365
Better adoption and usability
Less rework and fewer “we’ll fix that later” moments

Why choose WebVine as a Modern Work partner?

This designation confirms what our clients already experience working with us.

WebVine focuses on:

Making information easy to find and trust
Designing intranets and collaboration spaces people actually use
Putting governance and structure in place without slowing people down
Supporting long‑term adoption, not just project delivery

Microsoft’s recognition simply reinforces that approach.

Does this help with Microsoft Copilot readiness?

Yes, very much so.

Microsoft Copilot works best when your content is:

Well structured
Clearly governed
Actively used and maintained

The Solutions Partner for Modern Work designation reflects strong delivery across exactly those areas, making it especially relevant if Copilot is already in your environment or on your roadmap.

Does this change how WebVine works with clients?

Not really. And that’s the point.

This designation reflects how we already work: focusing on clarity, usability, governance, and adoption so your Microsoft 365 environment supports real work, not frustration.

The difference is that Microsoft is now formally backing that approach.

Is the Solutions Partner status permanent?

No. It has to be maintained.

That means ongoing delivery, continuous learning, and staying aligned to Microsoft best practice. For clients, that’s a good thing. It ensures your partner doesn’t stand still while Microsoft moves fast.

Is WebVine a Microsoft Solutions Partner in Australia?

Yes. WebVine is an Australian Microsoft Solutions Partner for Modern Work, supporting organisations across Australia and the broader ANZ region.

Webinar Wrap Up

Copilot puts a spotlight on something councils have been wrestling with for years: findability in SharePoint.

So we partnered with Microsoft to run a practical webinar for councils, focused on getting SharePoint foundations right and preparing for Copilot with confidence.

In the session:

John Crawford, Chief Digital and Information Officer at Central Coast Council, shared what really happened when his council enabled Copilot for every employee
James Dellow, WebVine’s Head of Delivery and Product, walked through what a good SharePoint setup looks like, plus a practical Copilot adoption approach councils can confidently apply

You can watch the full webinar recording below.
If you prefer to read, we’ve summarised the key takeaways underneath.

The big message from the webinar

One thing became very clear during the session:

If SharePoint isn’t working well today, Copilot will only amplify the problem.

Copilot doesn’t magically fix messy content, unclear permissions, or poor structure.
It reflects what’s already there just faster and more visibly.

That’s why getting the foundations right matters so much.

The “perfect” SharePoint setup (spoiler: it’s not about perfection)

When people hear “the perfect SharePoint setup”, they often imagine something complex or unrealistic.

In reality, as James explained, a strong SharePoint environment isn’t about perfection.
It’s about solid foundations.

A good way to think about it is like a well‑run library:

Clear signage
Sensible rules
Spaces people want to use

Across the councils we work with, the ones getting the most value from SharePoint (and feeling more confident about Copilot) consistently focus on three things.

1. Well‑planned information architecture

Clear site structures, logical groupings, and just enough metadata to help people find what they need, without over‑engineering.

When architecture is done well, staff aren’t relying on memory, luck, or the same “go‑to person” every time.

2. Governance built in from the start

Good governance isn’t about locking everything down.

It’s about:

Clear ownership
Simple rules
Guardrails that support work instead of blocking it

When governance is built early, it’s much easier to support compliance and productivity. And much harder for SharePoint to quietly drift into chaos.

3. User‑friendly design

SharePoint must make sense to real council staff, not just the people who built it.

Clear navigation, consistent layouts, and familiar language all make a huge difference to:

Adoption
Trust
Long‑term sustainability

We often compare this to a well‑run council building: clear signage, sensible rules, and spaces people want to use.

What “good” delivers day to day

When SharePoint is set up well, the benefits show up quickly, not as flashy features, but in everyday work:

Less time searching, more time doing
Smoother collaboration across teams and departments
More consistent ways of working
A reliable foundation for Copilot to add real value

The bottom line?
Fewer workarounds, less frustration, and better value from tools councils already pay for.

Why findability still matters (especially for councils)

Staff expectations at work have changed.

Outside the workplace, people type full questions into search boxes and get clear answers. Inside many council intranets, they’re still guessing keywords, clicking through folders, or asking colleagues where things live.

That gap creates:

Lost time searching
Low trust in content
Workarounds outside governed systems

For councils, this isn’t just a productivity issue. It’s a risk and compliance issue.

Search today isn’t just about keywords. It’s about meaning, context and trust. And that’s exactly what tools like Copilot rely on.

Copilot changes the stakes (but not the fundamentals)

Copilot respects your existing permissions. That’s reassuring. And also important.

Because it means:

If access is messy, Copilot can surface information more widely than expected
If content is outdated or duplicated, Copilot reflects that
If structure is unclear, answers are less trustworthy

Copilot doesn’t fix SharePoint problems.
It magnifies them.

That’s why Copilot readiness is really about:

Security and permissions
Content organisation
Compliance and information lifecycle

Not flipping a switch.

What happened when Central Coast Council enabled Copilot for everyone?

John Crawford, Chief Digital and Information Officer at Central Coast Council, shared why his team made the decision to enable Copilot for 100% of staff.

Like many councils, they were seeing teams use unsanctioned tools. Not because people were trying to bypass IT, but because they were just trying to get their work done.

Over time, that created growing security and governance risks.

Rather than restricting access, the council took a different approach.

The Foundations Behind it

~2,400 staff upgraded to Microsoft 365 E5 (including Copilot)
~700 servers migrated to Azure
A single, secure environment across Microsoft 365, SharePoint and Teams

The result was a platform that was safe, secure, and easy to use, so staff naturally returned to a governed environment.

Key Lessons from Central Coast Council’s Copilot Enablement

Get your digital house in order first: organised content, strong governance and a modern SharePoint/MS365 platform
Invest in your people: Training, champions and change management drove adoption
Be bold: Rolling Copilot out organisation wide accelerated uptake and learning.

A Practical Copilot Adoption Approach for Councils

Rather than rushing to roll Copilot out everywhere, we talked through a safer, more realistic approach.

Start with readiness

Before enabling Copilot, councils should be confident that SharePoint is:

Secure — right access for the right people
Well organised — clear structure and findable content
Compliant — aligned to records and retention obligations

A SharePoint‑focused readiness check is often a practical starting point.

Think about it as not giving AI the keys till you’ve checked the doors.

Align stakeholders early

Successful Copilot adoption isn’t just technical.

Different groups care about different things:

Executives focus on risk, governance and strategic value
IT and data teams focus on security, licensing and content quality
End users want clear, practical wins that help them do their job

Alignment means meeting each group where they are, and not giving everyone the same message.

Utlising Tools to Support Readiness

Software Asset Management (SAM)

SAM helps councils understand how Microsoft 365 is actually being used.

It provides:

Visibility into real usage
Confidence in licensing decisions
Reduced risk of uncontrolled sprawl

This matters because Copilot amplifies usage patterns.

SAM helps ensure adoption is intentional, not accidental, and supports cost, governance, and compliance conversations as AI moves into business‑as‑usual.

AI Readiness Check

WebVine’s AI readiness check turns insight into action by:

Supporting governance conversations
Helping prioritise improvements
Grounding Copilot readiness in evidence

Page Readiness Dashboard

Copilot doesn’t fix content. It reflects it.

This WebVine‑run assessment helps councils:

Identify outdated or low‑quality pages
Improve findability and trust
Make content more Copilot‑ready

Pilot first, then scale

A controlled Copilot pilot:

Reduces risk
Surfaces issues early
Builds confidence based on real experience

By the time Copilot scales, it feels familiar. Not risky or overwhelming.

Train your people

Good training turns curiosity into confident use.

What works best:

Targeted, role‑based training
Real examples and demos
Practical wins (like drafting reports from council documents)

The key is combining content preparation with user education, and being clear about what Copilot can, and can’t, do.

5 Steps for SharePoint Best Practice

Governance – clear ownership and simple rules
Architecture – structure that reflects how councils work
Training – practical, role‑based, scenario‑driven
Incremental rollout – steady, manageable change
Measure and support – ongoing improvement, not set‑and‑forget

Key takeaway

If there’s one message to take away from the webinar, it’s this:

Foundations first. Always.

When SharePoint is easy to use and trustworthy:

Staff adopt it naturally
Governance becomes easier
Copilot becomes a natural next step — not a risky leap

If you’re thinking about Copilot, or simply want SharePoint to work better for your council, you don’t have to tackle it alone.

WebVine supports councils with:

SharePoint governance and architecture
Copilot readiness assessments
Practical training and pilot programs

If you’d like to talk through what makes sense for your organisation, we’re always happy to help.

TL;DR

Microsoft used SharePoint’s 25th birthday to set direction, not look back
SharePoint is now the primary knowledge platform powering Copilot and AI agents
Microsoft is redesigning SharePoint around how people actually use it:
Discover, Publish and Build
This is a foundational UX shift, not a cosmetic refresh
Copilot doesn’t fix messy content. It amplifies whatever structure and governance already exist
Navigation is being standardised for AI, while becoming more safely extensible
Organisations don’t need to rebuild everything, but strong foundations now matter more than ever

When Microsoft SharePoint turned 25 this week, Microsoft didn’t spend much time looking back.

Instead, they used the milestone to clarify where SharePoint is heading next. And how it underpins AI across Microsoft 365.

We watched the event, followed the AMA with the product team, and unpacked the announcements through the lens of intranets, governance and Copilot readiness.

Here’s the practical takeaway.

SharePoint as AI infrastructure

Microsoft was very clear on one point:

SharePoint is now confirmed the primary grounding source for Microsoft 365 Copilot.

In simple terms, Copilot relies heavily on the content, structure and permissions inside your SharePoint environment.

If Copilot is the smart assistant, SharePoint is the filing cabinet. If the cabinet is well organised, clearly labelled and properly locked, the assistant gives confident answers. If it is messy, duplicated or unclear, that confusion shows up in the output.

This isn’t new in theory. But Microsoft has now made it explicit and is reshaping SharePoint accordingly.

For organisations, that raises the importance of getting the foundations right.

Discover, Publish, Build: More than a fresh coat of paint

Microsoft announced a refreshed SharePoint experience organised around three core jobs:

Discover
Publish
Build

This is not just a visual update. The previous experience largely dates back to 2016, long before AI first design was a priority.

Microsoft is restructuring SharePoint around how people use knowledge.

Discover: A clearer front door

Discover replaces the traditional SharePoint start experience with:

A more personalised home
Easier discovery of relevant sites and content
Stronger alignment with Teams and OneDrive

For most organisations, this means a cleaner, more consistent entry point.

What it does not mean is Microsoft reorganising your intranet for you. Your information architecture remains your responsibility.

If your structure is strong, Discover will surface that well. If it is inconsistent, those gaps may become more visible.

Publish: Making it easier to communicate well

Publish introduces a more unified experience for creating pages and news, with:

Clearer publishing workflows
Better use of templates
Improved visibility of drafts and live content
Foundations for Copilot assisted authoring

This is good news for content owners. It lowers the barrier to creating consistent, professional looking pages.

But it doesn’t replace governance.

If anything, as content becomes easier to create and AI can help draft it, clarity around ownership, review processes and lifecycle becomes even more important.

AI can help you write faster. It cannot decide what should exist, how long it should stay live, or who is accountable for it.

Build: From “sites and pages” to structured solutions

Build centralises how sites, lists and libraries are created and managed.

Microsoft is positioning SharePoint not just as a place to publish news, but as a structured platform for business solutions.

For organisations using SharePoint for controlled documents, operational portals or structured knowledge hubs, this direction makes sense.

In the AMA, Microsoft reinforced a helpful principle: AI assists the build, but people still own the decisions.

That aligns with what we consistently see. AI can suggest, draft and accelerate. It does not replace architectural thinking.

Copilot will amplify what’s already there

One of the clearest messages from the event was this:

Copilot does not bypass permissions.
Copilot does not fix poor governance.
Copilot depends on the quality of your SharePoint environment.

If permissions are messy, Copilot reflects that.
If metadata is inconsistent, answers can become broad or noisy.
If ownership is unclear, trust drops quickly.

We are already seeing this in Copilot readiness conversations. The organisations getting the most value are the ones that have invested in structure, clarity and governance.

Not perfect environments. Just intentional ones.

Navigation: Standardised, but still flexible

Navigation came up repeatedly in the AMA, particularly for intranet owners.

Microsoft confirmed that:

Core navigation will be standardised to support consistent AI experiences
Supported extensibility is expanding via SPFx navigation customiser APIs
Unsupported techniques such as hiding native navigation with CSS will not be future proof

For organisations with global navigation, mega menus or intranet accelerators, this is important.

The direction is not “less flexibility.” It is “flexibility on supported foundations.”

That is good for long term stability and upgrade paths.

What you can take advantage of now

Some elements are still in preview, but there are practical steps you can take today.

You can:

Review your SharePoint structure with Copilot use cases in mind
Strengthen metadata and naming standards
Clarify ownership and lifecycle rules
Assess navigation customisations for future supportability
Align your intranet roadmap with Microsoft’s AI direction

None of this requires a full rebuild. Often it starts with targeted improvements in high value areas.

The bottom line

SharePoint’s 25th anniversary was a clear nod to the future.

SharePoint is now firmly positioned as the knowledge backbone for AI in Microsoft 365.

For organisations, the message is simple:

The stronger your foundations, SharePoint foundations, the more value you’ll unlock from Copilot.

If you’re unsure how your current intranet stacks up, this is a good moment to pause and assess. A practical review now can prevent bigger clean ups later.

And if you’d like a second set of experienced eyes on your structure, governance or Copilot readiness, we’re always happy to have that conversation.

FAQs

What does “SharePoint is the primary grounding source for Copilot” actually mean?

It means Copilot relies heavily on SharePoint content, permissions, metadata and structure when answering questions. If your SharePoint environment is clear and well‑governed, Copilot’s answers are more accurate and trustworthy. If it’s messy, that mess shows up in the output.

Haven’t we known for a while that Copilot uses SharePoint?

Yes, that’s not new.
What is new is that Microsoft has now made SharePoint the explicit foundation for Copilot and AI agents and is reshaping SharePoint’s UX, navigation and extensibility to support that role.

What are Discover, Publish and Build?

They’re the three core jobs Microsoft is now designing SharePoint around:

Discover: finding relevant content quickly
Publish: creating and managing pages and news consistently
Build: creating structured SharePoint solutions, not just sites

This structure reflects how people actually use intranets day to day.

Is Microsoft reorganising our intranet for us?

No.
Microsoft was very clear that customers remain in control of their information architecture. The new experience changes how content is surfaced, not how your sites, libraries or pages are structured behind the scenes.

Will AI or Copilot clean up our content automatically?

No. And Microsoft explicitly addressed this.
AI can help draft, suggest and accelerate work, but it does not decide what content should exist, who owns it, or how long it should stay live. Governance and ownership still matter.

What does “AI‑assisted” or “agentic” building mean?

It means AI can help with planning, structuring and iterating on solutions. Like a smart collaborator. Humans still make decisions, approve content and own accountability. Microsoft described this as AI as a collaborator, not an autopilot.

Is navigation becoming more locked down?

Baseline navigation is becoming more consistent to support Copilot.
At the same time, Microsoft is introducing supported navigation extensibility through SPFx APIs. Custom navigation isn’t going away. It’s moving onto more stable, future‑proof foundations.

Do we need to rebuild our intranet now?

In most cases, no.
What organisations should do is:

Review structure with Copilot use cases in mind
Improve metadata and ownership in high‑value areas
Assess custom navigation for future supportability

Small, targeted improvements now can prevent bigger clean‑ups later.

Sources

Microsoft 365 Blog — SharePoint at 25: How Microsoft is putting knowledge to work in the AI era
https://www.microsoft.com/microsoft-365/blog/2026/03/02/sharepoint-at-25-how-microsoft-is-putting-knowledge-to-work-in-the-ai-era/
Microsoft Adoption — SharePoint at 25
https://adoption.microsoft.com/sharepoint/birthday/
Microsoft 365 Message Center summary (via Hands On Tek) — Introducing the new SharePoint experience
https://m365admin.handsontek.net/introducing-new-sharepoint-experience/
BuckleyPlanet — SharePoint at 25: The biggest refresh since 2016
https://buckleyplanet.com/2026/03/sharepoint-at-25-the-biggest-refresh-since-2016/
Microsoft Support — Getting started with Publish in SharePoint
https://support.microsoft.com/office/getting-started-with-publish-in-sharepoint-11d2b61d-7c25-4d7d-94cf-0abe66fb2936

TL;DR

If Copilot sounds confident but wrong, it’s usually a data foundations issue, not an AI problem.
Messy, duplicated, or unclear content leads Copilot to fill in the gaps.
Fixing structure, metadata, permissions, and prompts makes Copilot far more reliable. And improves everyday work too.

Dear WebVine,

We’ve got a bit of a trust issue brewing.

Our team has been using Microsoft Copilot and (on the surface) it looks brilliant. The answers are confident. Well‑written. Very convincing.

But then we dig a little deeper. We click through to the files it references. We try to validate the facts.

And… the information isn’t quite right.

Some of the data it seems to be pulling from our documents doesn’t exist. Some conclusions don’t line up with what’s actually in SharePoint.

We’ve realised what’s happening: Copilot is hallucinating.

Why is this happening? And more importantly, how do we fix it?

Chloe’s Take

Dear Slightly Spooked,

First up: you’re not alone. Not even a little bit.

We hear this all the time. From councils, healthcare providers, professional services teams, not-for-profits… pretty much anyone excited about Copilot and then has that moment of, “Hang on… where did it get that from?”

Here’s the reassuring part: in most cases, Copilot isn’t being reckless or broken. It’s doing exactly what it’s designed to do. Making sense of the information it can see.

The less reassuring (but fixable) part?

If your data is messy, outdated, duplicated, poorly labelled, or inconsistently structured… Copilot will confidently stitch together messy answers.

Think of Copilot like a very fast, very enthusiastic librarian. If the books are misfiled, unlabelled, and half of them are outdated, don’t be surprised if you get the wrong recommendation.

In short:

Messy data in = messy AI answers out.

Let’s talk about how to fix it.

Why Copilot Hallucinates (Even in Microsoft 365)

Copilot works by:

Looking at the content it has permission to access
Trying to infer meaning, patterns, and context
Generating the most likely helpful response

When your environment includes:

Multiple versions of the same document
Deep, inconsistent folder structures
Files with vague names like Final_v7_REALLYFINAL.docx
Missing or meaningless metadata
Permissions that don’t reflect reality

Copilot fills in the gaps.

Not maliciously. Not carelessly.

It’s more like a confident intern who’s been told, “Just do your best with what you’ve got.”

6 Practical Steps to Reduce Copilot Hallucinations

The good news? You don’t need to “turn off AI” or panic‑ban Copilot. You need to tidy up the foundations it relies on.

1. Clean Up Obvious Content Clutter

Start with the low‑hanging fruit:

Archive or delete outdated documents
Remove duplicate files
Agree on what the source of truth is

If humans struggle to find the right version, Copilot definitely will too.

2. Simplify Your Structure (Less Is More)

Deep folder mazes might feel organised (and old style). But they confuse both people and AI.

Aim for:

Flatter structures
Clear site and library purposes
Consistent naming conventions

If you have to explain your folder logic in a meeting… it’s probably too complex.

3. Use Metadata Like Labels on a Filing Cabinet

Metadata gives Copilot context. Something folders alone can’t do.

Even a small set of meaningful tags (document type, business area, status) can dramatically improve answer quality.

Think of metadata as the difference between: “Here’s a pile of paper” and “Here are clearly labelled folders.”

4. Fix Permissions (They Matter More Than You Think)

Copilot can only work with what it’s allowed to see, but it may generate confident summaries based on incomplete retrieval context..

That’s how you end up with:

Incomplete answers
Missing nuance
Over‑confident summaries

Permissions hygiene = better AI answers.

The Takeaway

If Copilot is hallucinating in your environment, it’s rarely a Copilot problem.

It’s a data quality, structure, and governance problem. One that many organisations are only now discovering because AI is shining a very bright light on it.

The upside? Fixing this doesn’t just improve Copilot. It improves search, collaboration, onboarding, and day‑to‑day work for your people.

And if you need a hand getting your data (and Copilot) back on solid ground - well, you know where to find us.

About Chloe:

Chloe Dervin is WebVine’s Managing Director and resident intranet whisperer.

Her superpower? Making the complex feel doable, and helping teams move from “we’re flying blind” to “we’ve got this.”

When she’s not rewriting the rules of digital workplaces or penning her latest “Dear WebVine,” Chloe is making work, work for everyone.

FAQs

What does it mean when Copilot is “hallucinating”?

Hallucination is when Copilot generates information that sounds plausible but isn’t actually supported by the content in your Microsoft 365 environment. It’s not lying. It’s filling in gaps based on incomplete or messy data.

Is Copilot broken if it gives incorrect answers?

In most cases, no. Copilot is behaving exactly as designed. It’s trying to infer meaning from the information it has access to. When that information is outdated, duplicated, or poorly structured, the output reflects that.

What are the most common causes of Copilot hallucinations?

Common causes include multiple versions of documents, deep and inconsistent folder structures, vague file names, missing metadata, and permissions that don’t reflect how people work.

Do we need to stop using Copilot until this is fixed?

No. The recommendation is not to panic or disable Copilot, but to clean up the foundations it relies on. Improving data quality reduces hallucinations and improves Copilot’s usefulness over time.

How much metadata do we actually need?

You don’t need a complex taxonomy to see improvements. Even a small, meaningful set of metadata, like document type, business area, or status, can significantly improve Copilot’s understanding and responses.

Why do permissions affect Copilot’s answers?

Copilot can only summarise what it’s allowed to see. If permissions are inconsistent or overly restrictive, Copilot may generate confident summaries based on partial information, leading to missing nuance or incomplete answers.

Can better prompts really make a difference?

Yes. Vague prompts encourage Copilot to guess. Being explicit about which document, library, or time period you’re referring to reduces ambiguity and improves accuracy.

Should Copilot ever be used without human review?

No. Copilot is best treated as a highly confident first draft. Facts should always be sense‑checked, citations followed back to source documents, and outputs reviewed before anything is shared externally.

Sources

WebVine – Understanding AI hallucinations and how to avoid them
https://webvine.com.au/understanding-ai-hallucinations-and-how-to-avoid-them/
Microsoft Learn – Microsoft Copilot for Microsoft 365 overview
https://learn.microsoft.com/en-us/copilot/microsoft-365/overview
Microsoft Learn – Data, security, and permissions in Copilot
https://learn.microsoft.com/en-us/copilot/microsoft-365/data-privacy-security
Microsoft Learn – SharePoint information architecture guidance
https://learn.microsoft.com/en-us/sharepoint/information-architecture-modern-experience

(A Very Serious Ceremony)

SharePoint is 25.

Which feels impossible, because surely 2001 was only… five years ago?

To celebrate a quarter-century of intranets, document chaos, governance debates, and the occasional “why can’t I access this folder” mystery, we’re hosting The WebVine Awards. A lovingly biased, slightly nostalgic, very real-world tribute to the features that quietly (and sometimes loudly) shaped how organisations work.

And yes: we’ve been working with SharePoint long enough to remember when some of these were “the new shiny thing”. WebVine’s been delivering on Microsoft platforms since 2010, which means we’ve lived through a few eras, a few migrations, and more than a few architectural decisions that made sense at the time.

Award 1: The “Held It All Together” Lifetime Achievement Award

Nominees:

Document Libraries
Version History
Permissions / Inheritance
Lists

Winner: Document Libraries

No matter what era we’re in, classic, modern, Teams‑first, Copilot‑everywhere, everything still comes back to the same question:

Where does the content live, and how do we manage it properly?

Document libraries are the engine room.

They’re not glamorous, but they’re foundational.

Document libraries became the default home base for organisational content: documents, records, policies, templates, working files, and long‑lived knowledge.

Over time, they quietly picked up responsibility for permissions, versioning, retention, metadata, and ownership. All the unsexy things that keep work from falling apart.

As Copilot and agents increasingly rely on SharePoint content as a trusted knowledge source, libraries matter even more. Not because they’re exciting, but because they’re one of the few places where structure, access, and context come together in a way both humans and AI can work with.

In other words: libraries didn’t just store work. They shaped how work gets governed and reused.

Award 2: Best Glow-Up Award

(From “Corporate Beige” to “Actually Nice”)

Nominees:

Modern Pages
Communication Sites
Modern web parts
Brand-aligned intranet patterns

Winner: Modern Pages

Modern pages unlocked real intranet design. Not just “prettier pages”, but content that’s easier to scan, easier to navigate, and easier to keep current.

Once pages became readable and flexible, intranets could finally be designed around how people look for information. Think clear headings, fewer dead ends, and content grouped around tasks instead of organisational charts.

If you’ve ever watched people struggle to find a form buried three clicks deep, you know how much this matters.

It’s also why modern SharePoint design became such a big part of how we build and advise. People don’t engage with spaces that feel cluttered, confusing, or outdated. No matter how powerful the platform underneath.

Award 3: The Plot Twist Award

(Nobody Saw This Coming)

Nominees:

SharePoint as the content layer for Microsoft 365
SharePoint quietly living inside Teams
SharePoint’s “knowledge platform” era
Copilot + agents using SharePoint content as fuel

Winner: Copilot + agents using SharePoint content as fuel

Here’s the real twist: SharePoint didn’t just survive 25 years.

It quietly positioned itself as the place organisational knowledge lives. And now it’s central to how Copilot and agent experiences work.

Instead of trying to be the flashiest tool in the stack, SharePoint became the dependable layer underneath everything else. The place where content could be structured, permissioned, curated, and kept (mostly) trustworthy.

That matters more now than ever. Copilot doesn’t invent knowledge. It surfaces what’s already there, respecting the access, structure, and signals SharePoint provides. Which means SharePoint’s long‑standing strengths (and weaknesses) are suddenly much more visible.

This isn’t about SharePoint becoming magical overnight. It’s about the reality that AI shines a very bright light on whatever content foundations you already have, good or bad.

Award 4: The “Made Our Lives Easier” Award

Nominees:

Co-authoring (goodbye “FINAL_final_v7_REALLYFINAL.docx”)
Sharing links / modern sharing
Modern page editing
Recycle Bin + restore (the quiet hero)

Winner: Co-authoring

It removed an entire category of workplace pain.

Email tennis. Version chaos. The fear of overwriting someone’s work. Gone.

Co‑authoring changed collaboration from taking turns to working together. Once files lived in SharePoint or OneDrive, multiple people could edit at the same time, see changes as they happened, and stop treating email as a document management system.

It’s one of those shifts that feels obvious now. Until you remember the years of attachments, renamed files, and polite arguments about which version was “the real one”. And then you realise: we really did live like that.

Award 5: The Funniest Feature Award

(Affectionately Unhinged)

Nominees:

“Check-in / Check-out”
Unique permissions
“This page is in edit mode somewhere”
My Site “personalisation” era

Winner: Unique Permissions

Nobody means to create a permission labyrinth.

And yet here we all are. Flashlight in hand, whispering “why can’t Karen see the policy?”

Unique permissions gave organisations precision control over sensitive content, which is genuinely useful when it’s applied deliberately.

But they also made it very easy to create invisible complexity. Over time, layers of broken inheritance and one-off access decisions quietly erode trust: people stop knowing what’s reliable, who can see what, and where the “official” version lives.

In an AI-shaped world, that mess doesn’t stay hidden for long. Over‑permissioned content isn’t just annoying anymore. It’s how the wrong information ends up confidently surfaced.

Powerful? Yes. Harmless? Absolutely not.

Award 6: The “We Loved You… But You’ve Aged” Award

Nominees:

Subsites
Classic publishing sites
Custom master pages
Heavy customisations that made upgrades… character building

Winner: Subsites
Subsites were the architecture pattern for years, and plenty of us got very good at making them work.

Subsites made it easy to spin up structure quickly. One site, lots of areas, job done.

But at scale, they often turned into a maze: tangled navigation, unclear ownership, permission quirks, and the eternal question “who is actually responsible for this content?”

Modern intranet thinking tends to favour clearer, flatter structures that reflect how people find information, not how org charts are drawn.

If you’ve ever migrated a subsite‑heavy environment, you know exactly why this award exists.

Award 7: The “Good Riddance” Award

Nominees:

SharePoint Designer 2013
SharePoint 2010 workflows
InfoPath Forms Services
Workflow Manager dependency era

Winner: SharePoint Designer 2013

SharePoint Designer empowered power users to automate processes without waiting for developers. A genuinely big deal when it arrived.

The downside?

Workflows that only one person understood, brittle dependencies, and solutions that aged badly. As environments modernise, these legacy patterns become harder to maintain, harder to migrate, and harder to explain to the next person who inherits them.

Thank you for your service. Please stop living in production.

Award 8: The “Most Iconic Interface Moment” Award

Nominees:

The SharePoint 2010 Ribbon
Site Actions
Classic list settings pages

Winner: The SharePoint 2010 Ribbon

You either loved it or feared it, but everyone remembers it.

A whole era of “look how much you can do!” followed closely by “why are there 400 buttons?”

It surfaced enormous capability in one place, which thrilled power users and slightly terrified everyone else.

It marked an era where SharePoint fully embraced being a platform, not just an intranet.

Lots of buttons. Lots of options. Lots of ways to accidentally do something permanent.

Award 9: The “Most Likely to Start a Fight in a Project Meeting” Award

Nominees:

Folders vs Metadata
Permissions debates
Governance
Navigation by org chart vs task

Winner: Folders vs Metadata

It’s the SharePoint equivalent of pineapple on pizza.

This debate forced organisations to confront a hard truth: findability is a design decision, not a setting you turn on.

The reality has always been that pure “folders only” or “metadata only” approaches rarely survive contact with real people. The best solutions tend to blend structure with behaviour. And now, with AI in the mix, that balance matters even more. If content is scattered, duplicated, or inconsistently described, both humans and AI struggle to make sense of it.

Award 10: The “Shook Us” Innovation Award

Nominees:

Copilot shaping content experiences
SharePoint as an AI‑ready knowledge layer
Content quality directly affecting AI output
Community‑driven acceleration

Winner: SharePoint’s AI + Copilot + agent direction

For many this was a “hold on… this changes everything” moment.

It reframed SharePoint from where we store things to how knowledge gets used. Content quality, structure, ownership, and governance now directly influence AI outcomes. Not just human ones.

AI didn’t make governance optional. It made it visible.

Happy 25th birthday, SharePoint.

You’ve been many things over the years: a portal, a file server replacement, a publishing engine, a workflow playground, and occasionally a source of mild emotional distress.

But the best part? You keep evolving.

Right now, you’re stepping into a new era where great information management doesn’t just help people find knowledge… it helps AI use it.

And to everyone who has ever said, “It’s in SharePoint somewhere” - this one’s for you.

If your SharePoint has a bit of history (read: subsites, legacy workflows, and permissions folklore), you’re not alone. Modernising it doesn’t have to be painful. But it does benefit from a plan.

Sources

Microsoft Adoption – Microsoft 365 knowledge management
https://adoption.microsoft.com/en-us/microsoft-365-knowledge-management/
Microsoft Learn – Get ready for Microsoft 365 Copilot with SharePoint Advanced Management
https://learn.microsoft.com/en-us/sharepoint/get-ready-copilot-sharepoint-advanced-management
Microsoft Learn – Add SharePoint as a knowledge source in Copilot Studio
https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-add-sharepoint
Microsoft Support – Document collaboration and co‑authoring in Microsoft 365
https://support.microsoft.com/en-us/office/document-collaboration-and-co-authoring-ee1509b4-1f6e-401e-b04a-782d26f564a4
Thrive – Microsoft 365’s real‑time co‑authoring and collaboration
https://thrivenextgen.com/collaboration-microsoft-365s-co-authoring/
Springer Nature – The impact of modern AI in metadata management
https://link.springer.com/article/10.1007/s44230-025-00106-5
Gartner – State of Metadata Management: Aggressively pursue metadata to enable AI
https://www.gartner.com/en/documents/5735883

TL;DR for CIOs

Copilot reflects the quality of your content, structure, and permissions. It does not fix them.
If your SharePoint is messy, Copilot will confidently surface messy answers.
Security trimming works, but over-permissioning becomes very visible, very fast.
Adoption is not automatic. People still need guidance, examples, and guardrails.
Copilot is a forcing function. It will accelerate both good and bad practices.

AI is having its “spreadsheet moment”.

Everyone wants it. Everyone assumes it is magic. And many organisations are about to be disappointed because the groundwork was skipped.

Microsoft Copilot can absolutely change how work gets done. But only if CIOs understand what it is, what it is not, and what it quietly exposes about the state of their digital workplace.

Let’s talk about what matters.

Copilot Is Not Your Organisational Expert. It’s More Like a Very Fast Graduate

There is a common mental model problem with Copilot.

Many leaders imagine an AI assistant that “just knows” the organisation. Something that can join tomorrow and instantly add value.

Copilot does not work like that.

A better analogy is a very smart graduate who reads everything you give them at lightning speed and then answers questions using exactly what they found.

If the documents are outdated, duplicated, poorly titled, or contradictory, that is what you will get back. Quickly. With confidence.

Copilot does not invent structure. It amplifies the structure you already have.

Your Information Architecture Just Became a Board-Level Topic

For years, information architecture, metadata, and content hygiene were seen as “nice to have”. Important, but always deprioritised.

Copilot changes that.

Why? Because it relies on:

Clear headings and semantic structure
Meaningful file names and page titles
Consistent use of metadata and page properties
Logical site and library boundaries (and avoiding deep folder hierarchies, which provide little semantic value to Copilot compared to metadata)

When these are missing, Copilot struggles to retrieve the right context. When they are done well, Copilot becomes genuinely useful.

This is why some teams say “Copilot is amazing” and others say “it’s underwhelming”, often inside the same organisation.

Permissions Debt: The Hidden Governance Problem Copilot Will Expose

Copilot respects permissions. That part works.

What it does not forgive is years of over-sharing.

If everyone has access to everything “just in case”, Copilot will happily surface content people forgot existed, including:

Draft strategies
Old policy versions
Half-finished working documents
Content that was never meant to be discoverable

CIOs should expect Copilot to shine a bright light on permission sprawl and governance shortcuts. This is not a Copilot problem. It is an organisational document management maturity problem that Copilot exposes.

Copilot Will Not Fix Poor Writing (But It Will Make It Obvious)

Copilot thrives on clarity.

Short paragraphs. Clear headings. Purposeful summaries. Explicit context.

For example, if your intranet reads like a legal thesis or a stream of consciousness, Copilot will still answer questions, but the answers will be vague, bloated, or oddly specific in the wrong places.

The upside? This is a huge opportunity to improve how people write for humans and machines at the same time.

Good content design now benefits:

Readers
Search
Copilot
Accessibility

That is a rare alignment worth leaning into.

Adoption Is a Change Challenge, Not a Licensing Problem

Buying Copilot licenses does not equal value.

People need to understand:

What Copilot is good at and how it can help them
What it is bad at
When to trust it
How to ask better questions/prompts
How to validate outputs

Without this, Copilot becomes shelfware or worse, a source of mistrust.

The most successful organisations we work with treat Copilot like any other capability uplift. They run enablement, share real examples, and set expectations early and keep training!

Copilot Is a Mirror – of Your Content, Culture and Governance

This is the part CIOs should sit with.

Copilot does not transform your organisation on its own. It reflects it.

It mirrors your content quality.
It mirrors your governance.
It mirrors your information culture.
It mirrors how intentional you have been about digital work.

That can be uncomfortable. It can also be incredibly useful.

Handled well, Copilot becomes the catalyst that finally gets long-ignored fundamentals addressed.

Author Bio

Rachel Harnott is the kind of modern work leader who can turn a blank page into something brilliant and remind you to drink water, usually in the same sentence.

As Head of Modern Work at WebVine, she helps organisations make their intranets, and their AI, work for real people. With a passion for clear communication and a healthy respect for good metadata (yes, really), Rachel spends her days bringing order to the delightful chaos of SharePoint, Copilot and the modern workplace.

Known for her practical takes and people-first mindset, she translates complex tech into plain English guidance teams can actually use: sensible information architecture, content governance that sticks, and success measured in answers, not page views.

When she’s not refining prompt patterns or untangling SharePoint pages, you’ll find her hunting down the perfect analogy to make change resistant colleagues nod along.

Rachel brings curiosity, clarity and just enough humour to make digital transformation feel a little less scary. And a lot more achievable.

FAQs

Will Copilot leak sensitive information?
Copilot respects Microsoft 365 permissions. It cannot show users what they do not already have access to. However, if your permissions are overly broad, Copilot will surface content accordingly.

Do we need perfect SharePoint to use Copilot?
No. But you do need to accept that Copilot will work better in well-structured areas and worse in chaotic ones. Many organisations start by fixing priority sites first.

Is Copilot accurate?
Copilot is as accurate as the content it can find. It does not fact-check your internal documents. Humans still need to apply judgment.

Will Copilot replace roles or reduce headcount?
Copilot changes how work is done. It speeds up drafting, summarising, and synthesis. It does not replace accountability, decision-making, or expertise.

Where should CIOs start?
Start with readiness, not rollout. Review information architecture, permissions, content quality, and user capability. Copilot rewards preparation.

Sources

Microsoft Copilot for Microsoft 365 Overview
https://learn.microsoft.com/microsoft-365-copilot

Microsoft 365 Information Architecture Guidance
https://learn.microsoft.com/sharepoint/information-architecture

SharePoint Governance Planning
https://learn.microsoft.com/sharepoint/governance

Microsoft 365 Security & Compliance Documentation
https://learn.microsoft.com/microsoft-365/security

Microsoft 365 Copilot Adoption Resources
https://adoption.microsoft.com/copilot

TL;DR

Designing for people first results in much better Copilot outcomes.
Clear headings, short sections, good summaries, strong page properties and alt text make content easier for people to read - and easier for Copilot’s semantic index to interpret.
Over-optimising for AI leads to brittle experiences and bad content.
Think of Copilot as the colleague who can do brilliant things… but only if you give them clear instructions and clean inputs.
Modern SharePoint pages + well-structured documents = your AI-enabled intranet power couple

There’s a growing trend in digital workplaces: rewriting content ‘for AI.’
As in, ‘Let’s restructure every page so the machine likes it.

And look - we love AI. We train it, we deploy it, we write about it. But designing your intranet exclusively for AI is like reorganising your entire kitchen so your toaster has a nicer view. Technically possible. Not actually helpful.

The truth is wonderfully simple:

Content that works for people also works best for Copilot.
Because Copilot’s semantic index thrives on clarity, structure and meaning - the very things people need too. If a person can quickly tell what a page is about, so can Copilot.
If a person can’t tell… Copilot won’t magically guess.

Let’s break down why.

Why people-friendly structure = AI-friendly structure

Copilot doesn’t magically “read your mind.”
It reads your content, and how well that content is organised directly affects the quality of its responses.

The Semantic Index for Microsoft 365 maps text, context and relationships across your environment so Copilot can retrieve relevant pieces when generating answers. It is powerful - but it is not psychic.
Think of the Semantic Index as the map that helps Copilot know what relates to what. It’s not just collecting words - it’s connecting ideas.

On top of that, Copilot’s architecture honours Microsoft Graph permissions, relationships and context. If your content is messy, rambling, buried in nested pages, or full of ambiguous sections, Copilot has to work harder than it should.

Think of Copilot less as an omniscient oracle and more as a highly capable, well, co‑pilot: powerful, fast and insightful, but still relying on you for direction, context and judgement.

The anatomy of a people-first, AI-ready SharePoint page

Below is the secret recipe. You already use most of these techniques in good intranet design - now they simply matter even more.

1. Clear headings (H2 + H3)

Humans skim.
AI chunks.

Headings help both audiences understand how a page is structured. Copilot’s semantic index uses these logical breaks to anchor meaning and retrieve relevant sections.

2. Short, purposeful sections

Break content into bite-sized paragraphs.

If your page feels like reading a doctoral thesis in one breath, Copilot won’t parse it cleanly. Neither will Sharon from Finance.

3. A strong summary at the top

This isn’t fluff. It’s context.

A crisp, 2–3 sentence summary helps readers instantly grasp what they’re looking at and helps Copilot understand the intent and scope of the page.

Similar to how you would tell an intern what to look for before sending them into the archive room.

4. Alt text that describes the image

Not “image1.jpg.”
Not “banner.”
Not “staff smiling.”

Good alt text improves accessibility and enhances semantic signals. It’s a win-win.

5. Page properties set correctly

Topic
Department
Keywords
Audience
Lifecycle stage (draft/published/archived)

These properties make rollups, filters and search ranking work smoothly - and give Copilot ready-to-use metadata for grounding responses.

6. Avoid overly complex layouts

Yes, flexible sections are great.
No, you don’t need a Russian-doll arrangement of a Russian-doll stack of nested columns inside a hero web part.

If humans struggle to visually follow the page, Copilot will too.

7. Avoid designing for AI

Don’t stuff your page with keywords.
Don’t add “For AI:” blocks.
Don’t write like you're briefing a legal robot overlord.

Avoid the temptation. It backfires.

Why modern pages + documents form your AI content ecosystem

A quick reality check:
Agents and AI engines prefer parsable sources like Word, PowerPoint and PDF over dynamic .aspx Site Pages. Modern SharePoint pages are built from JSON-like components, which can be harder for AI to extract reliably.
So the winning strategy is:

Write high-quality user-centric pages for navigation, clarity and experience.
Pair them with clean, final documents for policies, procedures and heavy detail.

People get elegant pages.
Copilot gets stable source-of-truth documents.
Everyone wins.

Practical tips (and friendly reminders)

Use page templates to ensure consistent structure.
Don’t bury important content in images - Copilot can’t read your infographic (yet).
Keep one canonical version of documents rather than five half-updated variants scattered across your site.
Use metadata over folders - Copilot doesn’t understand “nested folder spaghetti,” but it does understand categorisation.
Audience targeting is for people, not AI - Copilot follows permissions, not targeting.
Clean documents matter too - if your source-of-truth PDF is chaotic, Copilot can only do so much.

Author Bio

Rachel Harnott is the kind of modern work leader who can turn a blank page into something brilliant and remind you to drink water, usually in the same sentence.

Known for her practical takes and people‑first mindset, she translates complex tech into plain‑English guidance teams can actually use: sensible information architecture, content governance that sticks, and success measured in answers, not page views.

When she’s not refining prompt patterns or untangling SharePoint pages, you’ll find her hunting down the perfect analogy to make change‑resistant colleagues nod along.

Rachel brings curiosity, clarity and just enough humour to make digital transformation feel a little less scary. And a lot more achievable.

FAQs

Do I need to rewrite my entire intranet for AI?

Definitely not. Strengthen structure, metadata and summaries. That alone often delivers huge improvements in Copilot output.

Will designing for people reduce AI accuracy?

No - it improves it. Clear writing is the best “AI optimisation” available.

Do I need to add special “AI sections” to my pages?

Please don’t. If you feel the urge, take a walk, drink some water, and write a better summary instead.

Should I change my writing style to sound more ‘AI friendly’?

No - keep writing for people. Plain, clear, confident language gives Copilot the best possible input. You don’t need robotic phrasing, keyword stuffing, or ‘AI voice’ tricks.

Does Copilot read everything on my page?

Copilot honours permissions and relies on how well content is structured, chunked and indexed. If something is hidden in a web part configuration or buried in complex layout markup, retrieval may vary.

Should I move everything into documents instead of pages?

No - each has a role.
Pages = user experience.
Documents = stable, parsable grounding data.
Use both intentionally.

Is this all just content governance with a new hat on?

More or less. Quality, clarity and structure have always mattered - AI just raises the stakes.

Sources

https://learn.microsoft.com/en-us/microsoftsearch/semantic-index-for-copilot

https://download.microsoft.com/download/c/d/6/cd6c6858-f87b-4dc5-a593-e87db0aa6029/microsoft-365-copilot-architecture.pdf

TL;DR

Many growing organisations struggle with the same problem: no central intranet, scattered documents, and limited visibility across projects. When policies live in inboxes, forms are buried in emails, and dashboards don’t exist, teams waste time and leaders are forced to make decisions without data.

In this edition of Dear WebVine, Chloe shares practical advice on how to fix intranet sprawl, improve operational visibility, and make work easier without a massive transformation program.

Dear WebVine, “We’re Flying Blind…”

Dear WebVine,

We don’t have a central place for staff to go.

Everything’s scattered. Policies live in Word docs. Forms are buried in email threads. ISO procedures are hiding in a shared drive like they’re playing a very committed game of hide and seek.

People waste time just trying to work out how to apply for leave or log an IT request.

Half the answers live in someone’s head. The other half are… somewhere.

We’re growing quickly, but we’re still operating like a small business that’s held together with spreadsheets, memory, and crossed fingers.

It’s messy, manual, and honestly a bit embarrassing.

Help?

Chloe’s take

(Also known as: you’re not alone)

First things first. Take a breath.

If your organisation feels like it’s being run out of inboxes, shared drives, and “that one spreadsheet everyone’s afraid to touch,” you’re in very good company.

We hear this exact story all the time from growing teams. Especially ones that have scaled fast. They’ve had to take on more compliance, or add new systems quickly, meaning they can’t stop to redesign how work flows.

The good news? This is fixable.

The better news? It doesn’t require a 12-month transformation program or a budget that needs board-level therapy.

The real issue (and it’s not laziness): No central intranet

From what you’ve described, one thing is missing:

A central intranet
One clear digital home where staff can run their work lives. Not just read news, but do things.

Without that foundation, work gets harder than it needs to be.

People rely on email archaeology, hallway conversations, and “I think it lives somewhere in SharePoint?” That’s confusing and exhausting for everyone.

Why this happens (hint: it’s very normal)

This kind of disorganisation doesn’t happen because teams don’t care. It happens because:

Email worked… until it didn’t
Early on, Word docs and inboxes are fine. Then suddenly an organisation has grown so much that they’re not.
The accidental intranet
Someone built a SharePoint site once. It had good intentions. It never quite grew up and evolved.
No clear ownership
When everyone owns content, no one really owns it.
Disconnected systems
HR, finance, delivery, and IT all use different tools that don’t talk to each other.

It’s a sign that your organisation has outgrown its original setup.

What I recommend instead – a good intranet set up

Think of your digital workplace like a house.

Right now, it sounds like you’ve got great furniture, but no floor plan. Things exist, but no one knows where to find them.

Here’s what good looks like when your intranet finally works:

A modern intranet that feels obvious
Staff land in one place that’s clean, intuitive, and tailored to their role. Like a digital front desk that answers questions before they’re emailed.
Information that’s easy to find
Policies, forms, and procedures are clearly structured. No more “where’s the leave form?” messages.
Lightweight automation
Approvals, requests, and workflows that reduce chasing and follow-ups.
Change that feels human
Clear guidance, simple training, and support that meets people where they are.

It’s all about making the tech you already have work for your people.

Where to start (without overwhelming everyone)

Quick wins to improve your intranet and findability (the “this week” category)

Simplify your homepage, remove old news, long text blocks unused widgets,
Create a simple “Top Ten” section for staff to find resources they need daily eg find a person, find a policy, find a form
Run our intranet audit tool
Remove or hide worst outdated content
Run a short “can you find this?” session to spot findability issues

Sustainable intranet and reporting fixes (in 30-90 days)

Design a clear information architecture and intranet structure
Set up a sensible metadata and term model
Define content owners and governance, without making it heavy
Migrate legacy content with intention, not panic

The bottom line: Clear Information Makes Work Easier

This isn’t about perfection. It’s about clarity.

When people know where to go, what to trust, and how to get things done, work feels lighter. Decisions get easier. And growth stops feeling chaotic.

If your organisation feels like it’s outgrown its current setup, that’s not something to be embarrassed about. It’s usually a sign you’re ready for the next chapter.

Got something weighing on your digital workplace?

Send us your own Dear WebVine question.
We’ll read it, unpack it, and offer practical, honest advice. No jargon. No judgement.

About Chloe:

Chloe Dervin is WebVine’s Managing Director and resident intranet whisperer.

Her superpower? Making the complex feel doable, and helping teams move from “we’re flying blind” to “we’ve got this.”

When she’s not rewriting the rules of digital workplaces or penning her latest “Dear WebVine,” Chloe is shaping tomorrow’s leaders and making design work for everyone.

FAQs

What’s the first step to fixing our intranet mess?

Start small. Identify your biggest pain points. Is it findability, outdated content, or lack of ownership? A “Start Here” page, a quick content audit, or even a call with our team can help you get clarity fast.

We’ve already got a SharePoint site. Do we really need an intranet?

If your SharePoint site is just a document dump or a news feed no one reads, then yes. There’s a big opportunity to turn it into a true digital workplace. A good intranet helps people get things done, not just read announcements.

How do we make sure people use the intranet?

Engagement starts with relevance. If your intranet reflects how people work, with clear navigation, useful tools, and content that’s easy to find, they’ll use it. We also recommend lightweight training, champions, and regular feedback loops.

What’s the role of governance in all this?

Governance isn’t about locking things down. It’s about clarity and continuity. Who owns what? What’s the process for updates? How do we keep things tidy over time? Good governance makes your intranet sustainable, not bureaucratic.

How long does it take to get this right?

You can see real progress in as little as 7 days with some quick wins. For a more sustainable setup (like a new IA, term store, and dashboards), we typically work with clients over 30–90 days. It’s not about doing everything at once; it’s about doing the right things in the right order.

We’re not sure where to start. Can you help?

Absolutely. Book in a call with our team.

TL;DR

Copilot’s answers depend entirely on the quality of your SharePoint content, metadata, and permissions.
• Knowledge Agent will soon automate tagging, classification, and cleanup (great news for SMBs).
• Quick wins: flatten folders, add proper metadata, fix permissions.
• Copilot won’t fix a messy SharePoint. Its output is only as good as your input.
• A clean, well-structured SharePoint is your launchpad for AI productivity.
• Rewatch the full webinar below for demos and practical steps.

Why Getting SharePoint Ready Matters

AI is everywhere, but Microsoft Copilot is becoming the workplace assistant people see. There’s just one hitch: Copilot can’t think clearly if your SharePoint looks like the digital version of a pantry where the labels have peeled off, and someone has been “organising” at 2am.

There have also been multiple AI related updates and announcements by Microsoft. This includes Knowledge Agent and all the updates from Microsoft Ignite.

That’s why Chloe Dervin (Managing Director, WebVine) and James Dellow (Head of Product & Delivery, WebVine) hosted a webinar breaking down exactly what “Copilot readiness” means, and how you can take advantage of the new AI updates.

Rewatch the webinar here. If you prefer to read, scroll down for a summary.

Why Copilot Readiness Matters

If SharePoint is cluttered, outdated, or mislabelled, Copilot must guess. And guessing leads to:

People losing trust in AI (and abandoning it)
• Sensitive information appearing where it absolutely shouldn’t
• Copilot giving bad or incomplete answers
• Duplicate files, shadow IT, and messy version sprawl
• Content that Copilot simply can’t “see” or contextualise

Put simply: if SharePoint isn’t ready, Copilot won’t be either.

SharePoint’s Evolving Role in the Agentic AI Era

Microsoft’s message at Ignite 2025 was loud and clear: SharePoint isn’t just a document library. It’s now the knowledge layer for Copilot and AI agents.

Imagine it as your organisation’s central library. When the books are organised, labelled, and accessible, everything flows. If not, you get digital chaos disguised as “search results.” AKA AI hallucination.

What “Copilot Ready” Look Like

A Copilot-ready SharePoint has three markers:

Healthy Content & Structure

Clean libraries, sensible folder depth, no zombie files.

Useful Metadata

Documents labelled with meaningful properties so Copilot can understand context.

Good Permissions Hygiene

The right people see the right things. The wrong people don’t.

A messy SharePoint? That’s like a supermarket where cereal lives next to bleach and no one’s sure who has keys to the stockroom.

Demystifying Microsoft’s AI Terms

Let’s decode the alphabet soup:

AI: Technology that mimics human reasoning
Chatbot: Answers questions but can’t act
Copilot: Microsoft’s built-in AI helper across 365 apps
Agent: An AI that plans and performs tasks
Knowledge Agent: New Copilot feature that organises your content
Generative AI: Creates content
LLM: The brain behind tools like Copilot

Think of a chatbot as a helpful librarian. Agents are librarians who rearrange the shelves so that you can find things.

Knowledge Agent: Your Future SharePoint Organiser

Knowledge Agent is a win for SMBs or any team without an army of information managers.

It offers:

Auto-tagging and AI-driven classification
PAYG model with site-level opt-in
Included in most Copilot licences
Automated cleanup and lifecycle rules
Health checks for intranets and content hubs

No more marathon taxonomy workshops. No more “who last updated this?” panic. Just fast, intelligent organisation.

Where Knowledge Agent Works Best

It shines in everyday chaos:

Turning unstructured libraries into organised spaces
Tidying up stale content and broken links
Adding rich metadata for improved Copilot accuracy
Handling multiple file types (DOCX, PDF, PPTX, XLSX, HTML)
Enforcing governance and reducing risk
Automating content reviews and update cycles

Think of it as a content concierge that never gets tired.

What Copilot Cannot Do

Copilot has it’s limits:

It can’t access data outside M365 without connectors
It won’t override permissions
It can’t repair messy formatting or missing fields
It won’t create data that doesn’t exist
It can’t replace human judgment

In other words: Copilot is a super-powered assistant, not a miracle worker. Garbage in, garbage out.

Actionable Steps and Roadmap for Copilot Readiness

Quick Wins (Start This Week!)

Enable Admin Agent: Boosts management and Copilot readiness.
Flatten Folder Structures: Easier access, less confusion.
Start Metadata Uplift: Begin with 5–6 standard columns (Owner, Department, Document Type, Status, etc.).

Mid-term Actions

Clean-up & Permissions Audit: Secure your SharePoint and remove clutter.
Develop a Metadata Strategy: Plan for consistent, useful labels.

Long-term

Automate Governance: Set up alerts, retention policies, and review cycles.
Site-level Opt-in for Knowledge Agent: Roll out where it matters most.
Dashboard Progress: Show stakeholders the improvements.

What’s Coming Next in Copilot for SharePoint

Keep an eye out for:

AI workflows for lists and libraries
Create pages & lists via Copilot
AI-powered FAQ web part
Custom no-code agents
Admin center for agent governance
Viva Amplify integration
PAYG storage flexibility

Focus on capability, not dates. Microsoft’s roadmap evolves quickly.

Copilot Adoption Requirements

To get the most from Copilot:

Fix information quality issues.
Streamline workflows.
Close governance gaps and address shadow IT.
Enforce security: least privilege and regular reviews.

Not sure where you stand? WebVine’s Copilot Flight Check gives you:

A clear view of your SharePoint readiness
Quick wins and long-term improvements
A tailored roadmap for safe, effective Copilot adoption
Actionable recommendations and stakeholder engagement

Reach out to our team for more information.

Meet the Presenters

Chloe Dervin
Managing Director, WebVine
Chloe leads WebVine’s digital transformation projects, helping organisations energise their teams with Microsoft’s evolving suite of tools. She’s passionate about making technology accessible and impactful for everyone.

James Dellow
Head of Product & Delivery, WebVine
James is a SharePoint and M365 expert with a knack for turning complex problems into practical solutions. He’s a thought leader in information management and a champion for user-friendly design.

FAQs

Q: Can Copilot help me find content in poorly organised libraries?
A: Copilot does its best, but messy content means messy answers. Start by cleaning up your structure and metadata.

Q: Do I need a big team to get ready?
A: Not at all! Start with small, practical steps. Flatten folders, add metadata, and audit permissions.

Q: Can Copilot access data outside Microsoft 365?
A: Only if you set up connectors. Otherwise, it stays within your M365 environment.

Q: How do I get started?
A: Try WebVine’s Copilot Flight Check or start with the quick wins listed above.

WebVine Blog

So… what is Copilot Cowork?

What can Copilot Cowork do?

Coordinating work across tools

Turning intent into action

Handling longer‑running tasks

What do you need to make Copilot Cowork work properly?

Permissions still rule

Structure matters more than ever

Content quality affects output quality

When is Copilot Cowork available?

The bottom line

FAQs: Copilot Cowork

Sources

TL;DR

Chloe’s Take

Announcement ≠ understanding

So what can you do now? (Yes, you can absolutely recover this)

1. Reframe the “why”. In human terms

2. Train for real work, not ideal scenarios

3. Make it visible after launch

4. Support beats perfection

5. Expect adoption to take time

One last thing (and it’s a big one)

About Chloe:

Built the way SharePoint is meant to be built

More than products: an approach shaped by people

“We’re proud Microsoft said this about us”

Copilot readiness: starting with the fundamentals

Why structure still matters (even with AI)

PAT and CAT: making readiness visible and measurable

Page Assessment Tool (PAT)

Copilot Assessment Tool (CAT)

Supporting readiness

A moment of validation and a signpost forward

Frequently Asked Questions

TL;DR

What does “Solutions Partner for Modern Work” mean?

Why this matters to you

You’re choosing a partner Microsoft independently backs

You benefit from best‑practice foundations (without the guesswork)

You get outcomes, not just technology

You’re backed by a partner in it for the long haul

What got us here

FAQs

Webinar Wrap Up

The “perfect” SharePoint setup (spoiler: it’s not about perfection)

1. Well‑planned information architecture

2. Governance built in from the start

3. User‑friendly design

What “good” delivers day to day

Why findability still matters (especially for councils)

Copilot changes the stakes (but not the fundamentals)

What happened when Central Coast Council enabled Copilot for everyone?

The Foundations Behind it

Key Lessons from Central Coast Council’s Copilot Enablement

A Practical Copilot Adoption Approach for Councils

Start with readiness

Align stakeholders early

Utlising Tools to Support Readiness

AI Readiness Check

Page Readiness Dashboard

Pilot first, then scale

Train your people

5 Steps for SharePoint Best Practice

Key takeaway

TL;DR

SharePoint as AI infrastructure

Discover, Publish, Build: More than a fresh coat of paint

Discover: A clearer front door

Publish: Making it easier to communicate well

Build: From “sites and pages” to structured solutions

Copilot will amplify what’s already there

Navigation: Standardised, but still flexible

What you can take advantage of now

The bottom line

FAQs

Sources

TL;DR

Dear WebVine,