This guide explains what SharePoint Embedded is, how its two core building blocks work, what it costs to run, and how it compares to the WOPI Cloud Storage Partner Program. If you already know the platform and want to talk about delivery, see our SharePoint Embedded implementation and WOPI migration services.

What Is SharePoint Embedded?

SharePoint Embedded is a Microsoft 365 platform service that exposes the storage, identity, collaboration, and Office editing capabilities of SharePoint and OneDrive as a programmatic surface that your SaaS application consumes through the Microsoft Graph API. In plain language, it lets your SaaS use Microsoft's storage and Office editing infrastructure from inside your own application — without your end users ever needing to see SharePoint, without them needing a SharePoint or Microsoft 365 subscription of their own, and without your engineering team needing to build and operate a WOPI host.

SharePoint Embedded is API-only and headless. Your SaaS provides the user experience; Microsoft provides the underlying file platform.

File Storage Containers and Container Types

SharePoint Embedded is built around two primitives.

A File Storage Container is a unit of storage inside your customer's Microsoft 365 tenant. Content lives in a dedicated storage partition within the tenant boundary and is accessible only through the owning application — it is never visible to the customer's other Microsoft 365 users, or to other vendors' applications.

A Container Type is the schema you, the SaaS vendor, register with Microsoft. It governs how your containers behave, what permissions exist on them, and how they are billed. Once a container type is registered, your SaaS creates and operates against containers in each customer tenant through the Microsoft Graph API.

Because containers are isolated by application, a single Microsoft 365 tenant can host containers belonging to several different SaaS products without any of them being able to see each other's content. SharePoint Embedded also provides real-time co-authoring of Office documents as a platform capability, rather than as something each vendor implements.

How SharePoint Embedded Is Billed

Storage and API usage are metered against your Azure subscription on a pay-as-you-go basis, separate from the customer's other Microsoft 365 entitlements. Consumption is charged across storage volume, Microsoft Graph API transactions, data egress, and archive storage.

That model matters commercially as well as technically: because the cost sits with you rather than with the customer's Microsoft 365 licensing, you can package it into your own subscription pricing. It also means consumption is something to model before you commit to a container design, since container topology drives API transaction volume.

Microsoft's published rates change over time and vary by region and agreement, so we do not reproduce them here. Check Microsoft's SharePoint Embedded documentation for the current rate card, and build your business case against rates you have confirmed for your own region and agreement. Modelling consumption before the container design is fixed is part of every engagement we run.

Benefits For SaaS Vendors

SharePoint Embedded removes most of the operational and commercial friction that has historically slowed SaaS vendors down when embedding Microsoft 365 document editing. There is no Cloud Storage Partner Program membership to apply for, no Microsoft business-development gating, no dedicated WOPI host to build and operate, and no requirement that each end user already has a Microsoft 365 subscription of their own. Your application stands up containers in your customer's tenant on demand; Microsoft handles the storage, the Office for the web rendering, and the co-authoring infrastructure.

Beyond ease of onboarding, SharePoint Embedded inherits the Microsoft 365 compliance and security stack at no extra integration cost — which is decisive for SaaS vendors selling into regulated verticals such as legal, audit, financial services, healthcare, and the public sector. Documents stored in a container are subject to the customer's Microsoft Purview controls, so eDiscovery, auditing, data loss prevention, retention policies, sensitivity labels, and conditional access all apply automatically rather than having to be re-established on your own infrastructure.

Container content is also indexed for Microsoft 365 Copilot, which means your SaaS can participate in the Copilot experience your customers have already adopted without building a retrieval layer yourself. For most SaaS products targeting Microsoft 365 customers, that combination — no partnership barrier, inherited compliance, and Copilot readiness — is the reason to choose SharePoint Embedded.

Microsoft 365 Compliance

SharePoint Embedded sits inside the Microsoft 365 compliance perimeter rather than alongside it, which is a strong position for SaaS vendors competing for procurement against incumbents that store customer documents on the vendor's own infrastructure. From an architecture perspective the inheritance is largely an advantage, but an implementation must respect Microsoft's constraints. These include (but are not limited to):

Microsoft Entra ID app registration, owning-tenant, and consenting-tenant configuration
Container type registration, billing classification, and Azure subscription setup that aligns with your SaaS pricing
Microsoft Graph permission scopes and admin consent flow for each customer tenant
Microsoft Purview security and compliance settings inherited by container content
Retention policies, sensitivity labels, and data loss prevention rules
Operational telemetry, audit logging, and recycle-bin and version-history behaviour

SharePoint Embedded and WOPI

SharePoint Embedded is often described as the successor to the WOPI Cloud Storage Partner Program, and for new SaaS products it is generally the more direct route. It is worth being precise about what that does and does not mean.

WOPI remains a fully supported integration model, and Cloud Storage Partner Program membership remains open. What has changed is the recommended path for new entrants, not the support position for either model. There are still situations in which a custom WOPI host is the correct architecture — most obviously where storage itself is the product, where data residency requirements fall outside Microsoft's regional footprint, or where CSPP Plus capabilities are already in production.

The two platforms also differ in more than their APIs. They differ in who owns the storage, in the identity model, in where operational responsibility sits, and in the commercial and licensing shape of the integration. Our decision framework for SharePoint Embedded vs WOPI works through those differences in detail.

Talk To Us About SharePoint Embedded

McKenna Consultants implement SharePoint Embedded for SaaS vendors and migrate existing WOPI hosts onto the platform. To discuss what that would involve for your product, see our SharePoint Embedded services or contact our team.