SharePoint Embedded is Microsoft's modern, API-only platform for embedding Microsoft 365 document storage and editing into your SaaS application. By 2026 it has become Microsoft's preferred path for SaaS vendors that want to add full Word, Excel, and PowerPoint editing — and Microsoft 365 Copilot — to their own product without applying to the Cloud Storage Partner Program or building a WOPI host.

SaaS vendors are our primary clients for this service. McKenna Consultants have spent more than a decade implementing Microsoft document integrations for SaaS platforms in legal, auditing, work and workflow management, contract management, document management, education, and compliance. SharePoint Embedded is the natural next step in that practice, and we are delivering SharePoint Embedded implementations for SaaS vendors today — both as the chosen path for new SaaS products and as packaged migrations from an existing WOPI host.

For more information about SharePoint Embedded for SaaS, get in touch with our SharePoint Embedded specialists or read our explainer on what SharePoint Embedded actually is over on our blog.

Introduction to 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 and Microsoft provides the underlying file platform.

What Is SharePoint Embedded?

SharePoint Embedded is built around two simple primitives. A File Storage Container is a unit of storage that lives inside your customer's Microsoft 365 tenant but is accessible only to your SaaS application — 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 to govern 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. 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 — so SaaS vendors can package the cost into their own commercial model. The platform is generally available, has reached v1.0 stability for all the major container, container type, and migration APIs, and is now available in Microsoft 365 GCC for US Government customers and through 21Vianet for customers in China.

Looking to integrate SharePoint Embedded into your SaaS app?

If you are interested in working with McKenna Consultants to integrate SharePoint Embedded into your SaaS, or to migrate an existing WOPI host onto SharePoint Embedded, please contact our expert team today.

Benefits of SharePoint Embedded 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 SaaS 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, and your engineering team gets to spend its time on the parts of the product that differentiate you.

Beyond ease of onboarding, SharePoint Embedded inherits the full 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 SharePoint Embedded container are subject to the customer's Microsoft Purview controls, including eDiscovery, auditing, data loss prevention, retention policies, sensitivity labels, conditional access, and — as of 2026 — information barriers. SharePoint Embedded content is also a first-class knowledge source for Microsoft 365 Copilot through the new SharePoint Embedded knowledge source in Microsoft Foundry, which means your SaaS inherits Copilot and agent integration as a platform capability rather than a custom build. For most SaaS products targeting Microsoft 365 customers, this combination — no partnership barrier, native compliance, and Copilot readiness out of the box — is the reason to choose SharePoint Embedded.

SharePoint Embedded Service Offering for SaaS

You can engage us at any point in your SharePoint Embedded journey, from initial architecture through to a live, production-grade integration shipped to your SaaS customers. Every SaaS product is different, and most engagements blend several of the service levels below:

Container Type and Architecture Design

The single most consequential decision in any SharePoint Embedded implementation is the design of your container types and the way containers are mapped onto your SaaS's tenancy, document, and permission models. We help you define the right container topology for your SaaS multi-tenancy, register your container types with Microsoft, plan your Microsoft Entra ID app registrations and admin consent flow, and design the Azure billing structure that fits your subscription pricing. Get this stage right and the rest of the implementation is straightforward; get it wrong and remediation later is expensive.

Full SharePoint Embedded Implementation

This is a complete, end-to-end SharePoint Embedded implementation service for SaaS products. We deliver your container type registration, your Microsoft Graph integration, the document creation and editing user experience inside your SaaS, the permission model, the operational tooling, and the production deployment. Pick this option if you want McKenna Consultants to own the SharePoint Embedded workstream while your team focuses on the rest of the product roadmap.

Microsoft Graph and Container API Microservice

We build a multi-tenant Microsoft Graph and SharePoint Embedded microservice that handles container lifecycle, permissions, file operations, and Office editing handoff, while your team integrates that microservice into your existing SaaS architecture and user interface. This is a popular option for established SaaS platforms that want to keep their core application surface and team structure unchanged while delegating the SharePoint Embedded specifics to specialists.

Migration from WOPI to SharePoint Embedded

For SaaS vendors with an existing WOPI host, SharePoint Embedded often represents a strategic upgrade — a way to retire bespoke document storage infrastructure, regain native Microsoft 365 compliance, and unlock Copilot integration without building it yourself. We deliver these as packaged migration engagements covering the strategic case, the architectural mapping from WOPI concepts to SharePoint Embedded equivalents, the data and identity migration mechanics, and the phased rollout from pilot through to decommissioning the legacy host. A realistic migration of a non-trivial WOPI host inside a live SaaS product is a multi-month engagement, and our playbook reflects what we have learned in production migrations.

SharePoint Embedded Consultancy

If you want your in-house SaaS engineering team to do the implementation, we can act as a technical advisor — helping you initiate the project, validate your container type design, review your code, and stay on call to unblock the parts of SharePoint Embedded that are easy to get wrong. This is the lightest-weight engagement model, and it works particularly well for SaaS engineering teams that already have strong Microsoft Graph experience.

Technical Approach

Implementing SharePoint Embedded inside a SaaS product is a Microsoft Graph engineering exercise. There is no protocol to learn the way WOPI required, but the platform has its own constraints — container types must be designed up front, owning-tenant and consuming-tenant relationships must be set up correctly, and the Azure billing posture must match the commercial model your SaaS offers customers.

Our typical technical solution is a multi-tenant SharePoint Embedded service that owns the container type registration, manages your SaaS's relationship with each customer's Microsoft 365 tenant, and exposes a clean internal API to the rest of your platform. We implement the necessary Microsoft Graph operations end-to-end — container lifecycle, permission management, file create and update, version history, recycle-bin behaviour, and the handoff to Office for the web — and we wrap them in the operational tooling that production SaaS applications need: telemetry, idempotent retries, tenant-level health checks, and graceful degradation when Microsoft 365 is having a bad day.

Where appropriate, we extend the same architecture to expose your SharePoint Embedded content to Microsoft 365 Copilot through the SharePoint Embedded knowledge source in Microsoft Foundry. This is increasingly a baseline expectation: SaaS customers who have already adopted Copilot expect the SaaS products in their stack to participate in the same Copilot experience over their data.

Our team uses AI coding tools throughout our development workflow, so SharePoint Embedded implementations are delivered faster without compromising on compliance or quality.

Microsoft Compliance for SaaS Customers

SharePoint Embedded sits inside the Microsoft 365 compliance perimeter rather than alongside it — which is a strong selling point 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 a SaaS 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
Information barriers, retention policies, sensitivity labels, and data loss prevention rules
Operational telemetry, audit logging, and recycle-bin and version-history behaviour

We have extensive experience navigating Microsoft's constraints for both WOPI and SharePoint Embedded inside production SaaS products, and we use that experience to keep your implementation on the supported path through to a successful production rollout — and through the procurement and security reviews your customers will run on it.