Skip to content

sharepoint ai skills

What it is

AI Skills in SharePoint entered Public Preview on April 21, 2026 alongside two adjacent capabilities — site-level memory (context) and AI-driven content generation. Together they are Microsoft's answer to the recurring feedback from earlier AI-in-SharePoint preview customers: that AI needed to be "more aware of how their organizations operate — the norms, processes, and content preferences that are essential for how work gets done" (Microsoft, 2026-04-21).

The framing Microsoft uses is a three-way separation:

Layer Question it answers Concrete artifact
Context What to know about this site Plain-text Markdown file holding shared rules and preferences
Skills How to act — repeatable multi-step processes Plain-text Markdown file defining the shortcut
Content generation What to produce — deliverables aligned to preferences Word, Excel, PowerPoint files plus interactive reports/dashboards

This is the same conceptual pattern that underlies [[agent-skills-authoring]] and the custom-skill component of [[copilot-cowork]]: separating knowledge, procedure, and output into versioned artifacts the team can review and improve over time.

Architecture and how it works

Site memory — "what to know"

A user can prompt SharePoint in chat to "remember" a shared rule or preference — Microsoft's worked example is "remember that our team color is purple" or "avoid the use of aspirational language or marketing jargon." SharePoint persists that context at the site level, and anyone using the site's AI capabilities will have it applied automatically — for instance, a generated deck will prioritize purple in its color palette without the second user needing to know the rule exists (Microsoft, 2026-04-21).

This rollout reaches all opt-in public preview tenants over the two weeks following the announcement.

Skills — "how to act"

Skills are reusable multi-step shortcuts. The user defines them by prompting in chat to "define a specialized capability"; once saved on a site, any team member working on the site can invoke them. Microsoft provides four worked examples that show the intended scope:

  • Quarterly report generation — a finance team defines a skill that produces a quarterly report from data already stored in the site.
  • Proposal drafting — a sales team defines a skill that structures proposals and assembles them from past proposals and product documentation, output as a Word document.
  • Project tracker list — a project team defines a skill that creates a list with required columns, column types, and allowed values, so members generate compliant trackers automatically.
  • Content organization by information architecture — a content management team defines a skill that applies corporate taxonomy when assigning metadata, renaming files, or organizing content into the appropriate structure.

Skills are now available to all AI-in-SharePoint public preview tenants with no additional setup required.

Content generation — "what to produce"

Content generation is positioned as the closing piece of the workflow loop: "Most real content workflows don't end with a chat session — they end when the deliverable is produced." SharePoint can now generate Word, Excel, and PowerPoint files directly, as well as structured artifacts — reports, visualizations, interactive summaries — without code. The output is described as "a live, interactive output you can act on without leaving SharePoint" (Microsoft, 2026-04-21).

Critically, the act of generating content can itself be saved as a skill. Ask SharePoint to generate a weekly report once, save that as a skill, and the same structured output will be produced the same way every time — turning a one-off ask into a team-level repeatable pattern.

AI-driven content generation rolled out to public preview between late April and through May 2026.

Storage and editing — the Agent Assets library

The implementation detail that makes this story coherent is the file format. Context and skills are stored as plain-text Markdown (.md) files in a new Agent Assets library on the site. Microsoft frames this as deliberate alignment with "an emerging industry pattern for AI systems: separating what AI needs to know from how it should act and what it needs to produce."

The implications follow from the format choice:

  • Versioned — the files live in a normal SharePoint document library with version history.
  • Governed — library-level permissions and Purview-style controls apply.
  • Editable in the browser — SharePoint and OneDrive now support native Markdown viewing and editing in document libraries, so teams can refine skills without developer tools.
  • Editable via chat — users do not need to touch the Markdown directly; prompting SharePoint to update a skill writes the change behind the scenes.

Microsoft is explicit that "while it's never required for users to visit the markdown files directly, they are there as a simple way for anyone on the team to see the know-how that might otherwise live in one person's head." This is the strongest direct statement of intent: skills are an explicit attempt to externalize tacit team knowledge into a reviewable artifact.

Why the architecture matters

The Markdown-files-in-a-library design is the part most worth thinking about. It means SharePoint AI Skills are:

  1. Inspectable — anyone with read access to the site can read the skill and see exactly what behavior it encodes. There is no opaque skill blob.
  2. Forkable — copying a Markdown file to another site is a straightforward way to propagate a skill. (As a public-preview commenter noted, there is no first-class tool for distributing skills across hubs or intranets yet — that gap is acknowledged in the comments thread of the announcement.)
  3. Continuous with the broader ecosystem — Markdown is the same artifact format used by Claude Skills and the wider [[agent-skills-authoring]] tradition, which means SharePoint skills are not a proprietary format.
  4. A grounding asset for Copilot and agents across M365 — Microsoft writes that "this foundation of trusted, well-structured content also helps power better responses from Copilot and agents across Microsoft 365, enabling more effective end-to-end workflows through Work IQ." In other words, site-level skills and context feed [[copilot-cowork]]-style workflows, not only AI inside SharePoint itself.

This is also where the connection to content governance becomes load-bearing: if skills and context become the carriers of organizational know-how, the [[m365-content-governance-3rs]] capabilities (RAC, RCD, Agent Access Insights, archive, backup) become the controls that govern who can author and propagate behavior, not just who can read documents.

Limitations

Several limitations are visible in the announcement and its comment thread.

The capabilities are Public Preview rather than GA — content generation in particular rolls out gradually through late April and May 2026, and at least one commenter (marco_r_73) reports the content-creation feature is not yet available in their tenant. Tenant-by-tenant availability is uneven during the rollout window.

There is no first-class distribution mechanism for skills across sites or hubs. The public-preview commenter Suhakois highlights this directly: intranets that span many sites and hubs need a way to propagate skills, memory, page templates, brand colors, and tone of voice consistently — and that distribution tooling is absent from this release. Today, skills are site-scoped.

The capabilities require a Microsoft 365 Copilot license and explicit opt-in via aka.ms/SPAIoptin.

The Markdown editor is new and the announcement does not detail conflict resolution behavior when multiple users edit the same skill, nor what happens to in-flight executions if the underlying skill is changed mid-run.

This page is built on a single primary source — Microsoft's April 21, 2026 announcement at the M365 Community Conference. Confidence is high because Microsoft's own product announcement is canonical for status and feature description, but specific behavior should be re-verified against the live preview at the time of use.

Sources

  1. Microsoft Community Hub / Microsoft SharePoint Blog — "AI Skills Are Now in Public Preview: Teaching AI in SharePoint What to Know and How to Act," Zach Rosenfield, 2026-04-21. https://techcommunity.microsoft.com/blog/spblog/ai-skills-are-now-in-public-preview-teaching-ai-in-sharepoint-what-to-know-and-h/4512532
  2. Opt-in link referenced inline: https://aka.ms/SPAIoptin

Changelog

2026-05-18 — Page created from https://techcommunity.microsoft.com/blog/spblog/ai-skills-are-now-in-public-preview-teaching-ai-in-sharepoint-what-to-know-and-h/4512532 (Type: topic, confidence: 90 — single first-party source). Decided to keep as a standalone page rather than merging with [[m365-content-governance-3rs]] because AI Skills are a creation surface, while the 3Rs post is a governance surface; the two pages cross-link.