Copilot in SharePoint may be Microsoft’s most overlooked AI advantage: it turns existing SharePoint sites, libraries, and pages into governed AI workspaces using Markdown context files and reusable Skills. For organizations with Microsoft 365 Copilot, it offers a practical path to scale internal AI without new connectors, custom builds, or token-based cost exposure.

I’ve spent the better part of two decades with SharePoint — building on it, writing about it, and for a good stretch, helping ship it from inside Microsoft. Every few years something significantly expands the platform’s scope. Copilot in SharePoint is one of those moments, and many teams haven’t noticed yet.

What it actually is

Copilot in SharePoint is the AI experience that lives right inside your sites, libraries, lists, and pages. Microsoft built it around three jobs:

What to Know — a single SharePoint.md context file in a site’s Agent Assets library that loads into every conversation automatically. Your naming conventions, your library map, your rules — the AI knows them without anyone re-explaining.
How to Act — Skills: reusable Markdown workflows anyone with permission can run. Write the “contract review” or “quarterly report” flow once; the whole team runs it the same way every time. Copilot in SharePoint uses the same skill.md markdown files that Copilot Cowork uses (also mostly the same as Claude Cowork) and it executes them in convert with your organizational unstructured data – in SharePoint, where nearly 3 billion new files are created daily.
What to Produce — real output: Word, Excel, PowerPoint, and interactive HTML dashboards built from the content already in your libraries.

It’s all just Markdown — no code, no Power Platform build, no external connectors. That’s a deliberate, and I’d argue brilliant, design choice: it puts capability in the hands of the people who own the content.

Copilot in SharePoint is one of the best answers to that question, and it’s hiding inside a product you already own. If your organization licenses Microsoft 365 Copilot, Copilot in SharePoint is included during preview at no additional charge — no new SKU, no procurement cycle.

The BlueTrail Intelligence Report captured the same idea in a piece titled “The Secret Free Lane for Enterprise AI,” and its core argument holds: the hardest AI problem in most enterprises is knowledge access. Even the most capable model delivers thin value if it can’t safely reach your trusted internal content. Copilot in SharePoint closes that gap by turning the repository you’ve filled for years into a conversational AI system, governed by the permissions you already have.

How Copilot in SharePoint avoids token economics (today)

Here’s the wall every serious enterprise AI conversation eventually hits -- cost. Advanced AI now runs on consumption economics — every prompt, every agent run, every reasoning step lands on a bill. So the question executives are asking has become “how do we scale this without opening a second cloud bill we can’t forecast?” (As I said at Microsoft, “turn it on and we’ll find out together” isn’t a great way to plan expenses.)

Going beyond what BlueTrail covered, there are even more cost advantages for Copilot in SharePoint:

Copilot in SharePoint doesn’t use Copilot Credits – so no pay-as-you-go cost management or expense above your core Copilot licensing.
Copilot Skills in SharePoint can be automatically shared across the organization - no copying files to each individual OneDrive.

It’s the “cheat code” to bypass token economics and decentralized skill management (for now.)

Why this matters now

Starting this summer, Copilot in SharePoint shifts from opt-in to opt-out for every tenant with Copilot licenses. It’s going to appear for your users whether or not governance is ready. The teams that write one solid context file and one working Skill before the rollout get value on day one. The teams that don’t end up with a tool everyone tried twice and abandoned. Review your content quality, map the high-value use cases (HR, finance, sales, legal, ops), and treat governance as a prerequisite — not an afterthought.

The people doing the real work

Daniel Anderson — Microsoft MVP and the mind behind copilotinsharepoint.com — has been in this preview since the first Knowledge Agent build in September 2025. His 2026 practitioner guide is the most useful single reference out there. If you read one thing after this, read his.
On the Microsoft side, Zach Rosenfield, Partner Director of Product for Content AI, has been a genuine force in shaping and championing this space. It’s easy to forget there are people inside Microsoft pushing hard to make features like this real — Zach is one of them.

Building in the open

In high school and college math, we were always told “show your work.” That’s why our Copilot Skills library is open for anyone to use:

github.com/chris-mcnulty/copilot-skills — my open library of Markdown Skills for both Copilot Cowork and Copilot in SharePoint, one folder per skill. Nothing proprietary is baked in; company-specific values are supplied at runtime via each library’s variables.md, so the skills work for any person and any organization. Fork it, improve it, send a pull request.
Zach has his own repository of skills for SharePoint at github.com/zrosenfield/sharepoint-ai-skills
Vlad Catrinescu – another long-standing Microsoft MVP – also has his own repository online at: github.com/vladcatrinescu/sharepoint-ai-skills

The bottom line

If you already carry Microsoft 365 Copilot, you’ve got a lane open that most of your peers haven’t found yet. Spend an afternoon this month: enable it on one site, write a SharePoint.md, stand up a skill or two from the repo, and watch what your team does. The opt-out clock is running — better to arrive on purpose than by surprise.

References

Daniel Anderson, Copilot in SharePoint, the 2026 practitioner guide — copilotinsharepoint.com
BlueTrail Intelligence Report, The Secret Free Lane for Enterprise AI — bluetrail.ai