null

Continue reading How Developers Can Improve Their Learning and Productivity With AI on SitePoint.

File storage is rarely just file storage. 

Imagine your team is building a contract management application. At first, the document requirement looks straightforward: upload a file, organize it, retrieve it, and let the right people open it. 

Then the real requirements from your customer, security, and operations teams arrive, and the scope quickly expands to collaboration, authentication, permissions, governance, and administrative controls. What began as a feature has become a document platform. And now your team is spending cycles on content services instead of adding unique customer value.  

SharePoint Embedded offers another path: your team builds the application’s user experience and business logic, while SharePoint Embedded supplies the underlying file and document management services. It is a cloud-based, API-only system built on Microsoft 365. Documents remain within the customer’s Microsoft 365 tenant and your application accesses them programmatically through Microsoft Graph. 

The hidden scope behind “add documents” 

A homegrown approach to adding documents to your app can look attractive when the first milestone is small. However, you’ll soon find that customers need granular permissions. Users will want to work together in Word, Excel, and PowerPoint without downloading copies or creating conflicts. They’ll also expect agentic experiences, fast search, previews, sharing, version history, and reliable recovery. Security teams will require audit, data loss prevention, retention, and eDiscovery. And then, Operations teams will need lifecycle controls, scale, and predictable administration.  

The scope compounds to building and maintaining a document platform:  

• Content management: files, folders, metadata, search, versioning, recycle bin, restore, and lifecycle operations 

• Access: authentication, authorization, sharing, tenant isolation, and permission management 

• Collaboration: high-fidelity Office viewing and editing, co-authoring, AutoSave, and version history 

• Copilot and agentic experiences: ingestion, indexing, permission, and governance systems 

• Governance: auditing, retention, eDiscovery, and data loss prevention 

• Enterprise operations: scale, monitoring, administration, and integration with the customer’s Microsoft 365 environment 

Every sprint your team spends recreating commodity content services is a sprint not spent improving the workflow, insight, or intelligence that makes your application valuable. 

Add a document platform with SharePoint Embedded  

SharePoint Embedded changes the architecture decision. With this API-only solution, your team can focus on building the line-of-business and multitenant SaaS applications for enterprise content, without having to create a parallel content, collaboration, and compliance stack.  

SharePoint Embedded can help you do the following:  

• Add collaboration without building a collaboration engine 

• Build agent experiences on governed content 

• Keep content within the customer boundary  

• Enable your team to focus on adding unique value 

Add collaboration without building a collaboration engine 

Users already know how they want to work with Office files. They expect faithful rendering, real-time co-authoring, AutoSave, sharing, and version history; while admins expect a consistent security model.  

With SharePoint Embedded, your app can store files in a container and open them with the same Office services used across Microsoft 365. That lets you add familiar collaboration experiences and capabilities while keeping users anchored in the business process your application was designed to support.  

For example, external users can collaborate on documents in Office in a web browser – without needing a Microsoft 365 license. In addition, if you want to keep users in your app’s UI, you can embed a read-only file preview, and then use Office launch for editing.   

Learn more about how to Add Office co-authoring without building it and Open Office files from your app. 

Build agent experiences on governed content 

In addition to collaboration, users want agents that can find relevant content, answer questions, summarize information, and help move work forward.  

SharePoint Embedded provides a foundation for grounding AI experiences in application content while keeping that content and its compliance controls within the customer’s Microsoft 365 tenant. Developers can make content discoverable to Microsoft 365 Copilot and search it through Microsoft Search, while the application continues to control the user experience. 

With SharePoint Embedded, your teams can build agents that understand your customer’s workflow, such as reviewing contracts, answering case questions, or preparing project summaries. 

Learn more about how to Ground AI without an external vector database and Add Microsoft 365 Copilot and agent experiences. 

Keep content within the customer boundary 

For many customers, location and governance are as important as functionality.  

With SharePoint Embedded, content stays within Microsoft 365 under the customer’s tenant settings. Microsoft Purview compliance capabilities include audit, eDiscovery, retention, data-loss prevention, and sensitivity labels; conditional access also helps govern access. Availability and application of these capabilities depend on the tenant’s configuration and licensing. These capabilities can reduce the need to build a parallel compliance stack. 

And if you’re building customer applications, you don’t have to take custody of your customer’s data.  

For planning guidance, review Understand app and tenant architecture and Plan security, compliance, and governance. 

Enable your team to focus on adding unique value 

When building a content-centric app, it’s important to ask: “Where should our developers create unique customer value?” If document management is essential but is not the differentiator, SharePoint Embedded can provide the platform layer so your team can build the experience that is. 

Choosing SharePoint Embedded allow product and engineering leaders to focus on: 

• Investing in differentiation. Direct engineering capacity toward domain-specific workflows, automation, analytics, and AI instead of foundational document infrastructure. 

• Accelerating enterprise readiness. Build on Microsoft 365 storage, collaboration, agentic AI, security, and compliance capabilities that customers already use and understand. 

• Delivering cohesive product experiences. Keep control of the interface and business logic rather than sending users to a separate document portal. 

• Supporting multiple application models. Use the platform for internal line-of-business applications or multitenant SaaS offerings where each customer’s content stays in its own tenant. 

• Reducing long-term platform burden. Avoid owning an expanding backlog of document fidelity, collaboration, governance, and lifecycle features.  

Start building your app 

SharePoint Embedded provides a foundation for combining enterprise content with collaboration, AI, and governance experiences. For supported experiences, it can reduce the need to build your own document platform, compliance stack, vector database, or separate search index. Pay-as-you-go billing means you pay for usage rather than making an upfront commitment. 

Get started quickly by pointing your coding assistant at the SharePoint Embedded MCP server (preview) to provision and manage resources through natural language. Run: npx @microsoft/spe-mcp and then ask it to create a SharePoint Embedded project and a sample app you can upload files to.  

Prefer to start with a guided view? Use the SharePoint Embedded Visual Studio Code extension to create a container type, configure the owning app and billing, register the container type, create containers, and load a sample app. 

Not sure where to start? Visit the SharePoint Embedded documentation hub to learn more about SharePoint Embedded and whether it fits your app. 

The post Your app needs documents. Do you really want to build a document platform? appeared first on Microsoft 365 Developer Blog.