{"id":26245,"date":"2026-10-13T06:00:52","date_gmt":"2026-10-13T13:00:52","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/?p=26245"},"modified":"2026-10-13T07:22:49","modified_gmt":"2026-10-13T14:22:49","slug":"build-ai-powered-apps-without-creating-a-vector-database","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/build-ai-powered-apps-without-creating-a-vector-database\/","title":{"rendered":"Build AI-powered apps without creating a vector database"},"content":{"rendered":"

Developers building AI applications face a familiar challenge: how do you ground AI experiences in enterprise content while maintaining security, compliance, and governance?<\/span>\u00a0<\/span><\/p>\n

You can use\u00a0the <\/span>Microsoft 365 Copilot Retrieval API<\/span><\/b><\/a> for SharePoint Embedded, which helps\u00a0you add Microsoft 365 Copilot and agent experiences to your SharePoint Embedded apps when you want to control the grounding step, the prompt, and the model yourself.\u00a0<\/span>\u00a0<\/span><\/p>\n

In addition,\u00a0you can use\u00a0the<\/span> SharePoint Embedded Model Context Protocol (MCP) server<\/span><\/b><\/a>, now available in public preview<\/span><\/b>, to build and manage apps with a coding agent.<\/span>\u00a0<\/span><\/p>\n

Together, these capabilities can help developers move faster from application setup to AI-powered user experiences.\u00a0<\/span>\u00a0<\/span><\/p>\n

Build enterprise apps without creating a document platform\u00a0<\/span>\u00a0<\/span><\/h3>\n

Microsoft SharePoint Embedded is becoming a governed content layer for AI-powered applications, with clearer production guidance. 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.<\/span>\u00a0<\/span><\/p>\n

With SharePoint Embedded, content stays within Microsoft 365 under the tenant\u2019s settings, including Microsoft Purview compliance controls (audit, eDiscovery, retention, data-loss prevention, sensitivity labels, and conditional access). Your applications inherit enterprise governance, meaning you don\u2019t have to rebuild it. And if you\u2019re building customer applications, you don\u2019t have to take custody of your customer\u2019s data.\u00a0<\/span>\u00a0<\/span><\/p>\n

Furthermore, SharePoint Embedded is a consumption-based pay-as-you-go offering through an Azure subscription, with no upfront commitment. As a result, you can choose the billing model that better meets your needs: 1) standard billing of the tenant that owns or develops the application, or 2) pass-through billing to the tenant registered to use the application. <\/span>\u00a0<\/span><\/p>\n

Ground Copilot and agent experiences on enterprise content\u00a0<\/span>\u00a0<\/span><\/h3>\n

SharePoint Embedded grounds AI agents on enterprise content while keeping that content and its compliance controls inside the customer’s Microsoft 365 tenant. There are two ways for you to build SharePoint Embedded agent experiences that let your app answer questions over files stored in SharePoint Embedded containers: <\/span>\u00a0<\/span><\/p>\n

    \n
  1. Microsoft Foundry Agent Service with a SharePoint knowledge source<\/span><\/b><\/a> \u2013 for agents you build on Foundry. <\/span>Foundry runs retrieval for you as part of the agent.<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
      \n
    1. Microsoft 365 Copilot Retrieval API<\/span><\/b><\/a> \u2013 for custom agents and apps that run their own grounding step. <\/span>Call it from any app, including a Foundry agent that doesn’t use the SharePoint knowledge source.<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

      Today, let’s focus on the Retrieval API, which enables applications to retrieve relevant passages from SharePoint Embedded content and use those results as grounding data for AI experiences. Developers maintain control over the prompt, orchestration flow, and model while relying on Microsoft 365 to handle retrieval across enterprise content.<\/span>\u00a0<\/span><\/p>\n

      Because the content stays within Microsoft 365, developers don’t need to build and maintain separate content indexing infrastructure. This means that you can skip building and maintaining a pipeline that extracts text, creates embeddings, stores them in vector database, and keeps permissions in sync \u2013 for the life of the application. Also, you don\u2019t have to build access syncing, because the Retrieval API results are already trimmed to each user\u2019s permissions. <\/span>\u00a0<\/span><\/p>\n

      Furthermore, Microsoft 365 Copilot licenses are not needed for every user who queries the Retrieval API, if at least one user in the tenant has a Microsoft 365 Copilot license. The licensed user(s) can initialize the semantic index.<\/span>\u00a0<\/span><\/p>\n

       <\/p>\n

      \"RetrievalAPIImage<\/a><\/h3>\n

      How the Retrieval API works\u00a0<\/span>\u00a0<\/span><\/h3>\n

      Using the Retrieval API, developers submit a query and specify <\/span>sharePointEmbedded<\/span> as the data source, with pay-as-you-go billing on the <\/span>Copilot Studio message meter<\/span><\/a>. After a user asks a question, your app calls the Retrieval API. The API returns relevant text extracts from content stored within SharePoint Embedded containers, and your app passes the text extracts to its own model as grounding data.<\/span>\u00a0<\/span><\/p>\n

      This gives developers flexibility to build custom copilots, domain-specific assistants, document intelligence solutions, and other AI-powered experiences while keeping content governance aligned with customer expectations.\u00a0<\/span>\u00a0<\/span><\/p>\n

      For more information and guidance, see <\/span>Use the Retrieval API<\/span><\/a>.<\/span><\/p>\n

      Use natural language to build and manage apps with the Model Context Protocol server \u2013 now in public preview\u00a0<\/span>\u00a0<\/span><\/h3>\n

      While the Retrieval API helps developers create intelligent runtime experiences, we’re also making it easier to build SharePoint Embedded applications in the first place.<\/span>\u00a0<\/span><\/p>\n

      The <\/span>SharePoint Embedded Model Context Protocol (MCP) server<\/span><\/a>, now in public preview, enables you to build and manage apps with a coding agent. The open-source SharePoint Embedded MCP server npm package (<\/span>@microsoft\/spe-mcp<\/span><\/a>) lets MCP-compatible AI clients, such as GitHub Copilot in Visual Studio Code or the CLI, Claude, Cursor, and Azure AI Foundry, provision and manage SharePoint Embedded applications through natural language.<\/span>\u00a0<\/span><\/p>\n

      The MCP server can help developers streamline the management of SharePoint applications, allowing for quicker setup and configuration through AI assistance. Instead of clicking through portals and stitching together Microsoft Graph and Azure CLI commands by hand, you can describe what you want, such as “create a trial container type for my app”, and let your coding agent invoke SharePoint Embedded tooling on your behalf.\u00a0<\/span>\u00a0<\/span><\/p>\n

      The MCP server supports scenarios such as:<\/span>\u00a0<\/span><\/p>\n

      Watch the <\/span>SharePoint Embedded presentation<\/span><\/a> from a recent Copilot, Microsoft 365 & Power Platform community call to learn more about the Retrieval API:\u00a0<\/span>\u00a0<\/span><\/p>\n