PG · SP · 01 / 26
§ 01 — The sprawl problem
SEC 01 / 07
REV. MAY 26
Seismic/Platforms/SharePoint
Platform — SharePoint

SharePoint training videos for the surface your users actually use.

SharePoint isn't deployed once — it grows. Most users encounter it through Teams file tabs, Outlook on the web, and OneDrive rather than sharepoint.com, while site owners accumulate from self-service. Microsoft ships continuously with no named release windows, and M365 Copilot has resurfaced permissions debt as a blocking issue for most enterprise rollouts.

Platform
SharePoint Online · M365
Web surfaces
Teams web · OneDrive · OWA
Output
MP4 · captions · SCORM
See also
/capabilities
Illustration: an overhead view of a craftsperson's workbench laid out for a SharePoint training-video library — a large unfurled estate plan at the centre showing labelled blocks for site types (TEAM SITE, COMMS SITE, HUB, ARCHIVE) with a magnifying glass over one block revealing a list-view UI inside; a small wayfinding signpost beside the plan with arrows labelled 'via TEAMS', 'via ONEDRIVE', 'via OUTLOOK' all pointing inward; an ochre permissions key tag pinned in the corner; a steel measuring rule, a fountain pen, and a small stack of reference screenshots.
The sprawl problem

SharePoint isn't deployed once. It grows.

A SharePoint training library produced at rollout — and then left to age — has a different problem from a Salesforce or ServiceNow library. Microsoft ships continuously to SharePoint Online; there is no Spring or Vancouver release window. Microsoft publishes a monthly SharePoint Roadmap Pitstop tracking roughly 80–120+ roadmap items per year reaching general availability. New features flow through Targeted Release tenants first, then reach Standard Release typically 2–6 weeks later for routine items and several months for major overhauls.

Recent examples of the training problem. In August 2024, Microsoft shipped a redesigned SharePoint Start page — any training showing the old SharePoint Home now shows the wrong interface. In December 2024, Microsoft retired Delve entirely; training referencing Delve now directs users to a dead product. In 2025–2026, the document library command bar is being redesigned: “New and Upload” merge into a single “Create or Upload” button, breadcrumbs are rebuilt, and AI Actions appear for Copilot-licensed users. A library recorded against today’s UI will show the wrong command bar by the time it reaches Standard Release tenants.

M365 Copilot (GA November 2023) added a second layer to the training problem. Copilot surfaces all content a user can access via natural language — which means overshared files that previously required knowing where to look became immediately discoverable. Gartner found that 40% of organizations delayed their M365 Copilot rollout by three or more months because of SharePoint permissions and governance debt. Microsoft’s own response was to ship SharePoint Advanced Management as a paid add-on in March 2024, specifically to address oversharing at scale. Permissions training is now a Copilot prerequisite, not an afterthought.

The sharper problem, though, isn’t the platform’s flux alone. It’s that most users never visit a SharePoint URL. They open files from Teams, work in Outlook on the web, share through OneDrive. Training that demonstrates the SharePoint admin UI in isolation teaches the wrong center of gravity.

For SharePoint specifically, that means scoping for:

Per-audience web surface
End users live in Teams web and Outlook on the web. Site owners live in the SharePoint admin UI. IT lives in the M365 admin centers. The same content, taught through a different lens for each audience, outperforms one library that tries to teach everyone.
Modern versus classic
Most enterprises haven't fully migrated. Modern is the default; classic publishing sites and classic lists with InfoPath forms get isolated into a thinner sub-library that retires as those sites do.
Permissions and sharing as a Copilot prerequisite
Broken inheritance, sharing-link expiration, request-access loops, overly broad access groups. M365 Copilot made permissions cleanup urgent — it surfaces all accessible content via natural language, so oversharing that was obscure before becomes easily discoverable. The library treats permissions as a priority, with realistic test users.
Governance for owners
Site templates, hub association, naming conventions, retention labels, sensitivity labels. Owner training is materially different from end-user training and is usually scoped as its own sub-library.
What you get

A finished library, packaged for the M365 channels you already publish through.

A complete SharePoint training video library, scoped to your tenant and your audiences. Standard delivery includes:

Source MP4s
1080p H.264, broadcast-ready, with consistent overlay design across the library — cursor highlights, region focus, callouts. The visual language is consistent so the library reads as one product, not 30 separate recordings.
Captions and transcripts
WebVTT and SRT captions on every video, plus a plain-text transcript per module. Caption styling complies with WCAG 2.2 Level AA; caption files are versioned alongside the video so re-cuts stay in sync.
SCORM 1.2 and 2004
Both SCORM versions packaged on delivery — most enterprise LMS platforms accept either, but procurement reviews often spec one. Direct iframe embed and xAPI are available where the destination supports them.
In-tenant delivery
For organizations distributing inside M365 — Viva Learning catalogs, embedded video on SharePoint pages, hosted on Stream, surfaced in Teams — direct MP4 plus caption files plus iframe-friendly hosting handle the integration.
Library structure
A scoping document that maps your audiences and tasks to videos, organized by web surface (Teams web, OneDrive web, SharePoint admin) and by audience (end user, owner, IT). The structure is the artifact that prevents scope creep.

A typical SharePoint rollout library lands at 25–40 videos, with total runtime of 60–120 minutes, split across end-user and owner sub-libraries. Smaller engagements (a single intranet refresh, a single department’s site collection) run 12–20 videos. Tenant-wide governance resets run 60+, broken into per-audience sub-libraries.

SharePoint-specific scope

What we cover, and how scoping accounts for the platform.

SharePoint is a wide surface that lives behind several others. Scoping decides which slice of it is on screen for which audience. The patterns that recur across engagements, ordered roughly by how frequently each area changes:

M365 Copilot surfaces in SharePoint
For tenants with M365 Copilot licenses: the AI-assist button in the page editor (GA September 2024), the Copilot chat widget on sites (GA November 2024), and AI Actions in the document library command bar. All are license-gated — orgs without Copilot licenses see none of this UI. When Copilot is in scope, it is always isolated into its own videos; the interface and capabilities are still evolving every release cycle.
End-user fundamentals
Finding a file. Sharing without breaking inheritance. Requesting access. Working with versioning, check-out, and metadata. Taught against Teams web files tab and OneDrive on the web — not the SharePoint admin UI — because that is where users actually are when they hit the workflow.
Permissions and sharing
Inheritance, unique permissions, sharing links and their expiration, conditional access, guest access, request-access workflows. M365 Copilot made this area urgent — it surfaces all accessible content via natural language, so permissions are now a Copilot prerequisite for most orgs. Every engagement has a sub-library here because the surface area of mistakes is large.
Sites, lists, libraries
Modern team sites and communication sites, document libraries, lists with metadata, document sets where they're still in use. The container fundamentals that owners and power users need to understand before they can structure information.
Pages, web parts, news
Modern page authoring, web part configuration, news distribution, hub site rollups. The intranet-publishing side, scoped per the editorial workflow your communications team actually runs. The page editor gained new AI-assist capabilities in 2024; those are isolated when Copilot is in scope.
Governance and provisioning
Site provisioning workflows (manual, request-based, or automated via Power Platform), hub site association, naming conventions, retention labels, sensitivity labels. Owner-facing rather than user-facing. Microsoft shipped SharePoint Advanced Management (SAM) in March 2024 as a paid add-on specifically for governance at scale; SAM admin screens are in scope when IT-facing governance training is part of the engagement.
M365 admin and tenant settings
When IT-facing training is in scope: SharePoint admin center, sharing settings, hub site management, site lifecycle policies. These change more frequently than user-facing screens, so they are isolated in shorter videos that re-record cleanly.

What is intentionally not in scope by default: Microsoft 365 fundamentals (Teams meetings, Outlook calendaring, Word/Excel basics) — those are different artifacts, often already covered by Microsoft’s own learning paths or Viva Learning content. The desktop applications (Outlook for Windows, the OneDrive sync client’s File Explorer integration, the Teams desktop app) are also out of scope — the library is built against the web surfaces, which have functional parity for the workflows users hit and stay current as Microsoft ships continuously. The library is procedural and tenant-specific — it teaches a specific user how to do a specific task in your SharePoint.

How we work

From discovery to a library, in days.

The process is the same six phases used on every engagement, summarized here. The full version with timing and deliverables per phase lives on the homepage.

1 · Discovery
A 30-minute paid discovery call. We come back with a content outline, a timeline, and a fixed-fee SOW. You know the scope and cost before production starts.
2 · Access
Read access to a sandbox tenant or a dedicated training site collection, or a VM inside your environment for production-with-redaction. Production runs against the interface; data stays in your environment.
3 · Capture
Footage recorded against your configuration. Sandbox tenant with synthetic users and content, or production with redaction — whichever your security review approves.
4 · Narration and editing
Professional narration recorded against the captured footage. Consistent overlay design applied across the library.
5 · Packaging
MP4 + captions + transcripts + SCORM packages, plus in-tenant delivery files where Viva Learning, SharePoint embed, or Stream hosting is in scope. Output formats locked during discovery.
6 · Handoff
Library delivered, source files retained on your side as part of the deliverable. Updates handled as separately scoped work.

Full phase detail with timing on the homepage.

Sample & proof

Case studies, coming soon.

The studio is new. SharePoint work is underway; case studies post here once clients clear them. For unredacted references during late-stage evaluation, write to hello@seismic-technologies.com.

Anonymized clips of finished modules are available under NDA during discovery, covering voiceover, captioning, screen-recording quality, and branded packaging. A public reel will appear on the homepage samples section as each module clears.

Common questions

Frequently asked, SharePoint-specific.

Platform-specific questions buyers ask between researching the category and starting a conversation. Category-level questions (cost ranges, runtime, AI avatars vs studio) are answered on the pillar guide.

Do you cover both modern SharePoint and the classic experience?
Yes — and most enterprises need both, because few have fully migrated. The pattern that works is to treat the modern experience as the default and isolate classic-only workflows (older publishing sites, classic lists with custom InfoPath forms, on-prem holdovers) into their own short videos rather than mixing them into the main library. Hybrid orgs end up with a thinner classic sub-library that retires as those sites do.
How do you handle the Teams, OneDrive, and Outlook surfaces — they are all SharePoint underneath?
Most end users never visit a SharePoint URL. They live in Teams file tabs, OneDrive sync folders, and Outlook attachment links — all of which read and write to SharePoint document libraries. Effective training meets users where they actually work. The library covers the SharePoint admin surface for owners and IT, and the embedded surfaces (Teams, OneDrive, Outlook share dialogs) for end users. Same underlying platform, different lenses.
Can you train on permissions and sharing without showing real customer or employee data?
Permissions are usually the highest-pain area, so yes — we treat it as a priority. Capture happens in a sandbox tenant or a dedicated training site collection seeded with synthetic users and synthetic content. Real production captures only happen with frame-by-frame redaction of names, email addresses, group memberships, and any data your security review flags. Most engagements use the sandbox path because the workflows (broken inheritance, sharing-link expiration, request-access approval) need realistic test users to teach honestly.
Microsoft updates SharePoint continuously — how do you keep the library current?
There is no Spring/Summer/Winter release cut for SharePoint Online. Microsoft ships through Targeted Release rings (opt-in) and then Standard Release, typically 2–6 weeks later for routine features. Microsoft publishes a monthly SharePoint Roadmap Pitstop tracking roughly 80–120+ items per year reaching general availability. Recent examples of changes that broke training screenshots: the new SharePoint Start page (August 2024), Delve retirement (December 16, 2024), and the document library command bar redesign rolling out through 2025–2026. The library is scoped so volatile UI surfaces — command bars, sharing dialogs, the site creation flow, Copilot panels — sit in their own short videos that re-record cleanly. Stable narration about underlying concepts (what a library is, what inheritance means) usually survives. Refresh cycles run on your tenant's change schedule, not on a fixed calendar.
Can you cover site governance and provisioning training for site owners?
Yes — site-owner training is a frequent ask, and it is materially different from end-user training. Owners need to understand site templates, hub site association, naming conventions, retention policies, sharing settings, and the patterns IT wants enforced. End users need to understand how to find a file, share without breaking, and request access without escalating. Different audiences, different sub-libraries, often packaged together as one engagement so the visual and narration style stays consistent across the catalog.
Do you package for the M365 ecosystem — Viva Learning, SharePoint pages, Stream — or external LMS?
Both. Standard delivery is MP4 + WebVTT/SRT captions + transcript + SCORM 1.2 and 2004 packages, which works for most external LMS platforms. For organizations distributing inside M365 — Viva Learning catalogs, embedded video on SharePoint pages, hosted on Stream, surfaced in Teams — direct MP4 plus caption files plus iframe-friendly hosting handle the integration. Packaging is confirmed during discovery so the output matches the platform you actually deliver through.

For background on the category itself — production approaches, scoping a library, what separates a watched video from one that sits in the LMS — see the software training videos guide. For other platform-specific landings, see Salesforce and ServiceNow training videos.

Where Seismic fits

A boutique studio, not an M365 partner.

Seismic is a production studio, not a Microsoft partner. We do not configure your tenant, build your Power Platform automations, or write your governance policy. We produce the training video library that lands when the configuration is done — and refresh it when Microsoft moves the screens, or when your information architecture grows beyond what the original library covered.

Microsoft Learn (learn.microsoft.com) provides free training for SharePoint covering how the platform works out of the box — site creation, library fundamentals, permissions concepts, search. It does not cover your org’s specific site architecture, naming conventions, governance policies, custom metadata, or how your intranet is structured. Microsoft has trained 14.1 million people across its digital skills programs; none of that covers the decisions your SharePoint admin made for your tenant.

The Copilot rollout has made a tenant-specific library more urgent, not less. Gartner found that 40% of organizations delayed M365 Copilot deployment by three or more months because of SharePoint permissions and governance problems that Copilot would have surfaced to users. A permissions training library and a governance reset are now prerequisites for a safe Copilot deployment — not follow-on work.

We capture in your tenant
Sandbox or production-with-redaction, against your real sites, your real branding, your real intranet. Not a generic out-of-the-box library.
We meet users on the web surfaces
Teams web files tab, OneDrive on the web, Outlook on the web, modern SharePoint pages. Owner and admin training stays in the SharePoint and M365 admin UIs. Desktop apps are out of scope — the web surfaces stay current as Microsoft ships continuously.
We scope volatile areas for individual re-recording
Command bars, sharing dialogs, Copilot panels, the modern site creation flow. Stable workflow narration (what a library is, what inheritance means) survives Microsoft's continuous updates; the volatile UI pieces sit in short videos that re-record cleanly.
We deliver turnkey
Scoping, scripting, capture, narration, editing, and LMS or in-tenant packaging all included. You hand over access; we hand back a finished library.
Fixed-fee SOW
Discovery is paid and ends with a fixed-price SOW. No per-finished-minute billing.

If you’re rolling out a SharePoint intranet, running a governance reset, or preparing users for M365 Copilot, start a conversation.

Bring the tenant you need trained on. Leave with a scoped path.

Thirty-minute discovery call. We come back with a content outline, a timeline, and a fixed-fee SOW.
Book a discovery call