AI in SharePoint: What’s Available Today, What’s Coming Next, and How to Prepare
AI in SharePoint has been the subject of more marketing than actual product for the past twelve months. Between roadmap slides, preview announcements, and licensing tiers that change every quarter, it’s genuinely difficult for most organisations to work out what they can actually do today versus what they’ll be able to do next year.
This guide separates the two. What’s generally available. What’s rolling out. What requires additional licensing. What’s still on Microsoft’s roadmap. And most importantly — what your SharePoint environment needs to look like for any of it to work well.
Because here’s the pattern I keep seeing in real organisations: teams are being asked to prepare for AI features that don’t fully exist yet, on top of SharePoint environments that were never structured properly to begin with. The result is a lot of anxiety and very little clarity. This article is my attempt to give you both.
The 60-second answer
“AI in SharePoint” is not one feature — it’s a growing family of capabilities being introduced across SharePoint, some generally available, some in preview, some requiring specific licensing. What’s real today includes Copilot integrations for pages and content, AI-assisted metadata suggestions through features like Autofill columns and SharePoint Premium, and Copilot-powered search in tenants where it’s enabled. What’s still emerging includes autonomous site generation and cross-tenant answering.
The single truth that hasn’t changed: none of these features work well without solid information architecture underneath them. Whatever AI capabilities land in your tenant this year or next, the environment they operate on determines whether they’re useful or embarrassing.
Why this matters more than the feature list
Every organisation I’ve worked with in the last eighteen months has asked the same question, in different words: “Are we ready for AI in SharePoint?”
The honest answer for most of them: not for the reasons they think. The AI features they’re worried about are largely still in development, licensing-restricted, or dependent on specific tenant configurations. What they should be worried about is the SharePoint environment those features will eventually operate on — because that’s already broken, and no AI announcement is going to fix it.
I’ve walked into organisations where the leadership team was preparing “AI readiness plans” for capabilities they’d seen in a Microsoft demo — features that either weren’t yet available in their tenant or required licensing they hadn’t purchased. Meanwhile, the underlying SharePoint had inconsistent permissions, duplicate policies across multiple sites, orphaned content from projects that ended years ago, and no metadata worth speaking of. The AI wasn’t the risk. The environment was.
What’s actually available today
Let me separate what most tenants can genuinely do right now from what’s still emerging. Availability varies significantly by tenant, licensing, and rollout status — so treat this as a general guide rather than a guarantee for your specific environment.
Copilot for content generation
Where Microsoft 365 Copilot is licensed, users can generate text, summarise content, draft page content, and assist with document creation across Word, Excel, PowerPoint, and Outlook — some of which surfaces in SharePoint through embedded documents and page authoring.
AI-assisted page creation
Copilot can help create SharePoint pages, suggest layouts, and generate page content from prompts in tenants where Copilot is enabled and licensed. You still create the underlying site yourself — Copilot accelerates the page-building work inside it.
AI-assisted metadata (Autofill columns, SharePoint Premium)
Features like Autofill columns and SharePoint Premium (formerly Syntex) can analyse document contents and suggest or populate metadata into existing columns. This isn’t automatic in every tenant — it requires specific licensing, configuration, and a metadata structure to work against. Where it’s set up properly, it can significantly reduce manual tagging work.
Natural-language search experiences
Microsoft is progressively adding natural-language search capabilities across SharePoint and Microsoft 365. Availability depends on your tenant, licensing (Copilot enhances search significantly), and modern search experience rollout. Some tenants have rich natural-language search today; others are still on more traditional search behaviours.
AI-assisted list and library creation
In tenants where these capabilities have landed, Copilot can help create lists and document libraries from prompts, suggest column structures, and configure basic settings. Availability is uneven across tenants and often requires Copilot licensing.
Autonomous site generation from prompts
Microsoft has publicly demonstrated AI generating full SharePoint sites from natural-language descriptions, but this isn’t broadly available in production tenants today. In most environments, you create the site yourself and then use AI to accelerate configuration — not the other way around.
Deeper agentic capabilities across SharePoint
Microsoft’s roadmap includes expanding Copilot agents that can operate more autonomously within SharePoint — running multi-step tasks, orchestrating actions across sites, and handling more complex requests. Timing and availability vary. Watch Microsoft’s roadmap for updates rather than assuming these are available today.
What AI in SharePoint won’t do — regardless of what’s available
Even in the most generously licensed, latest-preview-flagged tenant, there are limits to what AI does. Understanding these limits early saves difficult conversations with leadership later.
It won’t fix bad structure. If your libraries are folder-first with a dozen levels of nesting, no AI feature will magically flatten them. It can help you tag files, generate content, or answer questions — but the underlying architecture is still yours to fix.
It won’t fix permissions. If your permissions are inconsistent, files are shared unpredictably, and confidential content is technically accessible to the wrong people — AI will happily surface that content to anyone who’s technically authorised to see it. This isn’t AI misbehaving. It’s AI doing exactly what it’s designed to do, on an environment that wasn’t ready.
It won’t invent metadata that doesn’t exist. AI-assisted metadata features can populate columns you’ve already defined. They don’t design your metadata structure for you. The Document Type, Status, and Department columns — or whatever your equivalent are — still have to be planned and created by someone who understands your content.
It won’t fix scattered content. If your team’s actual working files live in individual OneDrives, Teams chats, or old file shares — AI features running against SharePoint can’t find them. They can only work with what’s in SharePoint. See SharePoint vs OneDrive for the deeper conversation about where files should actually live.
It won’t remove your governance responsibility. If AI surfaces the wrong content to the wrong person, that’s still a governance failure — and it will be treated as one by regulators, auditors, and internal compliance teams. AI doesn’t reduce your governance obligations. In some ways it raises them, because mistakes surface faster and more visibly.
What good preparation for AI in SharePoint looks like
Let me show you what “AI-ready” actually means in a real organisation. Not a Microsoft demo. A working environment.
A 120-person professional services firm I worked with over the last two years spent most of their AI-readiness budget not on new AI licensing but on getting their existing SharePoint in shape. What they did:
- Audited every SharePoint site, identified owners, deprecated the ones that were orphaned or duplicated
- Rebuilt hub-and-spoke architecture around five hubs — Clients, Projects, Departments, Knowledge, Corporate
- Applied a consistent metadata structure to all major libraries — Document Type, Status, Department, Owner
- Ran a permissions audit across sensitive content and fixed inconsistencies
- Moved team content out of individual OneDrives back into SharePoint
- Documented governance standards and appointed named owners for every site
When AI features started rolling into their tenant — first the Copilot-enhanced search, then AI-assisted metadata suggestions, then AI-assisted page authoring — everything worked. Not perfectly, but usefully. The AI was operating on structured, permissioned, cleanly-owned content. It could actually help.
What “not ready” looks like
800+ SharePoint sites with no hub structure. Inconsistent metadata across libraries. Confidential HR content in a “test” site shared broadly. Team files scattered across individual OneDrives. When AI features arrive, they surface duplicated policies, expose confidential content to wrong audiences, and answer questions with conflicting information from outdated sources.
What “ready” looks like
A designed hub-and-spoke architecture. Consistent metadata on major libraries. Permissions audited and documented. Team content in SharePoint, not OneDrive. Named owners for every site. When AI features arrive, they operate on clean information and produce answers people can trust.
There is no AI without IA.
Whatever AI features Microsoft ships this year or next, they will operate on the information architecture you’ve built. Structured, permissioned, cleanly-owned content produces useful AI answers. Messy, scattered, orphaned content produces confidently wrong ones. The AI isn’t the variable that determines whether it’s useful in your organisation. Your foundation is.
The SharePoint 12 Tips Guide
If you’re preparing your SharePoint for AI features — either the ones available today or the ones coming — this is where I’d start. Twelve practical tips covering the structural work that makes any AI capability more useful.
Download the free 12 Tips Guide →The licensing question — the honest answer
Microsoft’s AI licensing has become genuinely complex. Different capabilities require different combinations of:
- Microsoft 365 Copilot (paid add-on)
- SharePoint Premium (formerly Syntex) — for specific content-intelligence features
- Pay-as-you-go pricing for some AI features
- Base Microsoft 365 plans — some baseline AI is included, exact scope varies
- Tenant-level rollout and feature flighting
I won’t tell you what’s included in your plan because the honest answer is: it depends. It depends on your Microsoft 365 licensing, whether you’ve purchased Copilot, whether SharePoint Premium is enabled, what features have rolled out to your tenant, and how your admin has configured things.
The safest advice: don’t assume any AI feature is available or free in your tenant. Ask your Microsoft admin, your account manager, or your IT team what’s currently licensed and enabled. Then plan accordingly. Anyone telling you AI in SharePoint is “included” or “free” is oversimplifying licensing that Microsoft themselves have made increasingly complicated.
How to prepare your SharePoint for AI — the practical steps
Regardless of what AI features land in your tenant this year or next, the preparation work is largely the same. This is what I recommend every organisation focus on now.
1. Get your metadata structure right
At minimum, apply three consistent metadata columns to your main content libraries — Document Type, Status, Department (or their equivalents for your organisation). This is the foundation any AI feature will use to make sense of your content. Without it, AI features have very little to work with.
2. Audit permissions before AI amplifies them
Every AI feature that answers questions or surfaces content does so based on the asking user’s permissions. If your permissions are inconsistent — broken inheritance, orphaned share links, “everyone in the organisation” access on content that shouldn’t have it — AI will faithfully surface that content to whoever’s technically authorised. Audit sensitive areas first: HR, Legal, Finance, executive communications.
3. Consolidate scattered team content
Move team content out of individual OneDrives and back into SharePoint. AI features running against SharePoint can’t see what’s in other people’s OneDrives. If your organisation’s actual knowledge lives in personal accounts, AI features won’t be able to surface it — which defeats most of their value.
4. Deprecate content that shouldn’t be findable
Old projects. Outdated policies. Draft documents from three years ago. If AI features can find it, they’ll cite it — sometimes as if it were current. Retention policies and active content lifecycle management reduce this noise significantly. What isn’t relevant should be archived or deleted, not left where AI can misinterpret it.
5. Document ownership
Every SharePoint site should have a named owner accountable for its content. Orphaned sites are a governance risk in a pre-AI world. In an AI-enabled world, they’re worse — AI can surface content nobody has reviewed in years, from sites nobody remembers exists.
6. Communicate expectations before AI shows up
When AI features start appearing in your tenant, users need to understand what they mean. Content might surface differently. Search might return new kinds of answers. Governance might feel more visible. Getting ahead of this with clear communication prevents surprises and builds trust in whatever features do land.
The Copilot Readiness Quick Guide
If you’re serious about preparing your SharePoint environment for AI features — not just today’s capabilities but everything Microsoft ships next — the Copilot Readiness Quick Guide walks you through the full 25-question readiness scorecard, the 30-day plan, and the sensitive content audit. It’s the guide I wish more organisations had before their AI conversations began.
Get the Copilot Readiness Guide — $39 →Where AI in SharePoint fits alongside Copilot, Agents, and other tools
The AI landscape in Microsoft 365 has genuinely become confusing. Different features live under different names, use different licensing, and do different things. Here’s how I explain it to the organisations I work with.
Microsoft 365 Copilot is Microsoft’s paid AI assistant that lives inside Word, Excel, PowerPoint, Outlook, Teams, and other Microsoft 365 apps. You interact with it directly — asking it to draft, summarise, analyse. Requires a paid Copilot licence per user.
SharePoint Premium (formerly Syntex) is Microsoft’s content-intelligence platform for SharePoint. It handles document processing, classification, extraction, and metadata automation. Requires specific licensing beyond baseline Microsoft 365.
AI features embedded in SharePoint — the umbrella term I’ve been using loosely as “AI in SharePoint” — includes Copilot integrations for pages and content, AI-assisted metadata suggestions, natural-language search improvements, and other capabilities being rolled into the SharePoint experience. Availability and licensing vary.
Copilot Agents are more autonomous AI capabilities that can execute multi-step tasks. Microsoft has been expanding these across Microsoft 365. Availability depends on tenant, licensing, and admin configuration.
You don’t need to use all of these. Most organisations will end up using a subset, depending on their licensing and priorities. The important thing is to understand which features you actually have access to before planning any strategy around them.
Where to go from here
Preparing for AI in SharePoint is mostly about preparing your SharePoint. The features will keep evolving. The foundation work stays the same.
- SharePoint for Beginners — start here if you’re not yet confident with the SharePoint basics AI features will operate on.
- SharePoint vs OneDrive — the “where do I save what?” decision. Foundational for making AI features useful.
- SharePoint Site Structure — the hub-and-spoke architecture that AI features work best against.
- The Knowledge Base — 240+ free step-by-step workflow cards covering everyday tasks.
Frequently asked questions
Is AI in SharePoint available in my tenant right now?
It depends on your Microsoft 365 licensing, whether you have Copilot licensed, whether SharePoint Premium is enabled, and what features have rolled out to your tenant. Some AI capabilities are broadly available; others require specific licensing or configuration. Ask your Microsoft 365 admin or account manager what’s currently active in your environment before planning anything around it.
Do I need Microsoft 365 Copilot licensing to use AI features in SharePoint?
For many of the more powerful AI features, yes. Baseline Microsoft 365 plans include some AI capabilities, but the richer experiences — natural-language content generation, Copilot chat within SharePoint, advanced search — generally require Copilot licensing. Some content-intelligence features require SharePoint Premium separately. Licensing has become genuinely complicated; verify with your admin before assuming.
Can AI automatically tag all my SharePoint content with metadata?
Not automatically in every tenant. Features like Autofill columns and SharePoint Premium can analyse document content and suggest or populate metadata into existing columns — but they require specific licensing, configuration, and a metadata structure to work against. You still need to design the columns, and results still need review, especially for content used in compliance or governance decisions.
Can AI build a complete SharePoint site from a text prompt today?
Not broadly. Microsoft has demonstrated this capability publicly, but in most production tenants today you still create the site yourself. AI can accelerate the work — generating pages, suggesting layouts, helping create lists and libraries — but the underlying site is generally created through the standard SharePoint flow. Autonomous full-site generation is on the roadmap rather than in most tenants right now.
What’s the difference between Microsoft 365 Copilot, SharePoint Premium, and Copilot Agents?
Microsoft 365 Copilot is the paid AI assistant inside your Microsoft 365 apps. SharePoint Premium (formerly Syntex) is Microsoft’s content-intelligence platform for document processing and metadata automation. Copilot Agents are more autonomous AI capabilities that can execute multi-step tasks. They’re separate products with separate licensing that Microsoft sometimes describes under overlapping marketing terms — which is why the space feels confusing.
What should I do to prepare my SharePoint for AI features?
Focus on the foundations rather than the features. Get your metadata structure right. Audit and clean up permissions. Move team content out of individual OneDrives into SharePoint. Deprecate old content. Document ownership. These are the things every AI feature will operate on regardless of what Microsoft ships. My Copilot Readiness Quick Guide walks through the full 25-question readiness scorecard and 30-day plan.
Final thoughts: The foundation is the strategy
AI in SharePoint will keep evolving. Microsoft will keep announcing new capabilities, adjusting licensing, and rolling things out at different paces to different tenants. The specific features will look different in six months, a year, three years.
What won’t change: whatever AI capabilities land in your environment will operate on the information you’ve structured. Clean structure produces useful AI answers. Messy structure produces confidently wrong ones — visibly, to everyone with access.
The best AI preparation isn’t a feature checklist. It’s the unsexy structural work — metadata, permissions, ownership, lifecycle, governance — that makes every future Microsoft announcement more useful in your organisation and less risky. That’s the real “AI readiness.”
There is no AI without IA. Everything else follows from that.
The SharePoint 12 Tips Guide
If you’re preparing your SharePoint for AI features — whichever ones land in your tenant first — this is where I’d start. Twelve practical tips covering the structural work that makes any AI capability more useful, no matter what Microsoft ships next.
Download the free 12 Tips Guide →
