Architecture, Automation, and Development

What Is SharePoint Embedded? SharePoint Definition and Guide

SharePoint Embedded is an API-only Microsoft 365 file and document management platform for custom applications. It lets enterprise developers and software vendors store each application's documents in isolated File Storage Containers inside the customer's Microsoft 365 tenant while using Microsoft Graph, Office collaboration, SharePoint content services, and Microsoft Purview protections.

Business LeaderIT DirectorSharePoint AdminAlso: Microsoft SharePoint EmbeddedAlso: File Storage ContainersAlso: API-only SharePoint storage

Current as of July 13, 2026: As of July 13, 2026, SharePoint Embedded uses Microsoft Graph-managed File Storage Containers, stores app documents in the customer's Microsoft 365 tenant, and bills storage and API use separately through Azure.

What SharePoint Embedded Means in SharePoint

An application creates and controls File Storage Containers in a dedicated SharePoint Embedded partition. The content remains in the consuming organization's tenant but does not appear as ordinary SharePoint sites or libraries; users reach it through the application's own interface and approved APIs. The app owns the content experience and container-level authorization model.

SharePoint Embedded is not a headless replacement for every team site or intranet. It is designed for application-managed content where a line-of-business system or multitenant product needs Microsoft 365 storage, coauthoring, security, compliance, and Copilot-related capabilities without exposing a conventional SharePoint user experience.

Why It Matters to the Business

For an enterprise, Embedded can add governed document capabilities to a custom case, claims, client, product, or records application while keeping content in the tenant. For an ISV, it can provide a Microsoft 365 content foundation for customers. The application still needs a complete product, support, security, and data-lifecycle model.

Pricing is separate from ordinary SharePoint storage entitlements and uses Azure-linked consumption meters for storage and API activity. The business case should include active and archived storage, transaction volume, tenant onboarding, operations, support, migration, exit, and long-term portability.

What SharePoint Administrators Need to Know

Architects should design tenant and container types, app registration, permissions, delegated and application access, roles, sharing, billing, lifecycle, search, events, backup expectations, and disaster recovery. Use Microsoft Graph APIs and follow current limits, throttling, regional availability, and licensing guidance.

The consuming tenant's Purview and Microsoft 365 controls can apply to Embedded content, including retention, DLP, eDiscovery, sensitivity, auditing, and Conditional Access in supported scenarios. Verify each control rather than assuming parity with ordinary SharePoint sites. Build administration, telemetry, support, export, and deletion features into the application.

What to Consider

Choose it for app-managed content

Use Embedded when the custom application?not a SharePoint site?is the primary experience and must own document workflow and authorization.

Model consumption cost

Estimate active and archived storage, API calls, growth, tenants, retention, export, and support before committing to the architecture.

Build tenant operations

Provide onboarding, consent, billing connection, container management, audit, support, export, retention, and secure offboarding.

Practical Takeaway

Choose SharePoint Embedded for application-managed document experiences that need Microsoft 365 content services, and design billing, authorization, compliance, operations, and exit from the start.

How This Shows Up in the Field

Claims application

A custom claims portal stores case documents in containers, uses Office coauthoring, applies tenant compliance controls, and exposes only the application's task-specific interface.

SaaS document module

An ISV creates isolated containers in each customer's tenant and builds onboarding, permissions, metered billing, retention, export, and deletion into the product.

SharePoint Embedded and ordinary SharePoint

SharePoint Embedded	API-only application-managed containers with a custom user experience and separate consumption billing.
SharePoint Online site	A Microsoft-provided collaboration or publishing experience with pages, libraries, lists, navigation, owners, and standard tenant entitlements.
Azure Blob Storage	General object storage without SharePoint's native Office collaboration and Microsoft 365 content-management integration.

Related 6SC Services and Proof

SharePoint Development ServicesDesign and build secure Microsoft 365 applications, APIs, containers, identity, automation, telemetry, and operations. SharePoint CustomizationsChoose the right boundary among native SharePoint, SPFx, Power Platform, Azure, Graph, and Embedded.

Related SharePoint Glossary Terms

Microsoft Graph for SharePointMicrosoft Graph for SharePoint is the unified Microsoft 365 API surface used to work with SharePoint sites, lists, libraries, files, pages, permissions, search, and related Microsoft 365 identities and groups. Applications use Graph endpoints and Microsoft Entra permissions to integrate SharePoint content with services across the wider Microsoft 365 ecosystem. SharePoint REST APIThe SharePoint REST API is the web service exposed through SharePoint's _api endpoints for creating, reading, updating, and deleting SharePoint sites, lists, libraries, items, files, users, permissions, search settings, and other supported objects. It uses HTTP requests and OData conventions so applications can work with SharePoint without a server-side SharePoint object model. SharePoint Framework (SPFx)The SharePoint Framework (SPFx) is Microsoft’s supported client-side extensibility model for building custom SharePoint and Microsoft 365 experiences with modern web technologies. Developers package web parts, extensions, libraries, and related components for controlled deployment through an app catalog while respecting the permissions and hosting patterns of Microsoft 365. Data Loss Prevention (DLP)Data Loss Prevention, or DLP, is a Microsoft Purview policy capability that detects sensitive information and risky handling across SharePoint, OneDrive, Teams, Exchange, endpoints, and other supported locations. In SharePoint, a matching rule can audit activity, notify users, show policy tips, restrict access or sharing, and create incidents without replacing permissions or sensitivity labels. Retention LabelA retention label is a Microsoft Purview control applied to an individual document, folder, list item, email, or other supported item to govern retention and deletion. It can retain content, delete it after a period, retain then delete it, trigger disposition review, or mark it as a record. It differs from a container-wide retention policy.

Frequently Asked Questions

Do SharePoint Embedded files live in the customer's tenant?

Yes. Microsoft describes a dedicated partition and File Storage Containers inside the consuming Microsoft 365 tenant, accessed through the owning application and APIs.

Can users browse SharePoint Embedded content in a normal SharePoint site?

No standard SharePoint site experience is provided. The application supplies the user interface and controls access to its containers through supported APIs.

Does normal SharePoint storage licensing cover Embedded?

Microsoft documents separate Azure-linked consumption billing for active and archived storage and API calls. Model current meters, limits, and entitlements before implementation.

Official Microsoft References

SharePoint Embedded overview

Editorial review date: July 13, 2026. Product status and licensing can change; confirm current Microsoft documentation before implementation.

Put SharePoint Embedded to work with a clear plan

6SC can help your organization evaluate, design, implement, govern, and support SharePoint Embedded in a maintainable Microsoft 365 environment.

Talk with 6SC