u/SharePointSteve
-
1points
-
3points
What would make SharePoint Embedded easier to administer? (self.PowerPlatform) [Power Apps]
-
2points
What would make SharePoint Embedded easier to administer? (self.legaltech) [Question / Tech Stack Advice]
-
5points
What would make SharePoint Embedded easier to administer? (self.sharepoint) [SharePoint Online]
-
1points
What would make SharePoint Embedded easier to administer? (self.SharePointEmbedded)
-
1points
New guidance and updates for building enterprise-grade apps with SharePoint Embedded (self.HealthTech) [Innovations]
-
6points
New guidance and updates for building enterprise-grade apps with SharePoint Embedded (self.sharepoint) [SharePoint Online]
-
3points
New guidance and updates for building enterprise-grade apps with SharePoint Embedded (self.legaltech) [Implementation Story]
-
3points
New guidance and updates for building enterprise-grade apps with SharePoint Embedded (self.PowerPlatform) [Power Apps]
-
1points
New guidance and updates for building enterprise-grade apps with SharePoint Embedded (self.SharePointEmbedded)
-
9points
SharePoint Embedded + Power Platform: building document-centric apps without building the storage la (self.PowerPlatform) [Power Apps]
-
1points
-
1points
-
3points
Build grounded AI apps on Microsoft 365 content without managing a vector database (self.legaltech) [Implementation Story]
-
5points
Build grounded AI apps on Microsoft 365 content without managing a vector database (self.sharepoint) [SharePoint Online]
-
1points
Build grounded AI apps on Microsoft 365 content without managing a vector database (self.SharePointEmbedded)
-
1points
How are you isolating data in SharePoint Embedded? (self.softwarearchitecture) [Tool/Product]
-
0points
-
0points
How are you isolating data in SharePoint Embedded? (self.PowerApps) [Discussion]
-
3points
How are you isolating data in SharePoint Embedded? (self.sharepoint) [SharePoint Online]
SharePointSteve
SharePointSteve
That's our goal with the new integration into the SharePoint Admin center to make it easier to create and manage apps in your organization. https://devblogs.microsoft.com/microsoft365dev/streamline-creation-and-management-of-ai-ready-custom-apps-with-sharepoint-embedded?WT.mc_id=MTC-blogB-202610
SharePointSteve
This is a good example of where I’d evaluate SharePoint Embedded, especially since your React app is intentionally separate from the SharePoint UI. SharePoint Embedded gives the app its own API-only content containers in Microsoft 365, so the app remains the experience rather than sitting on top of a site users can also navigate directly and potentially break your application by deleting items your app depends on. You can keep the React front end, Entra sign-in, Graph integration, and your Azure Function pattern for AI.
I’d design the SharePoint Embedded containers around a meaningful access boundary, such as a team, project, or case, and continue using delegated access where the user’s permissions should govern what the app can read. I would not treat an app-only Azure Function that filters results itself as equivalent to delegated authorization; that function needs its own carefully reviewed access model.
The important caveat is that Embedded is a file and document platform, not a drop-in replacement for your SharePoint lists. Since it doesn't support lists, would a .csv or JSON file simulating the list storage work in your app? If lists are doing most of the work, your current approach may be the better fit; if documents, app-controlled access, and a standalone UX are central, SharePoint Embedded is worth comparing. It also has separate metered billing, so the “no separate storage cost” part of your current design changes
SharePointSteve
The SharePoint Embedded MCP server lets compatible AI clients set up and manage SharePoint Embedded applications through natural language. SharePoint Embedded also supports additive file/folder permissions, although access inherits from the container by default. Citations would be the responsibility of the calling application and content centered MCP servers. Versions can be retrieved with the SharePoint Embedded MCP server. https://github.com/microsoft/SharePoint-Embedded-Samples/blob/main/AI/mcp-server/README.md?utm_source=chatgpt.com#what-it-does
SharePointSteve
I think the key is that SPE isn’t trying to be a headless way to rebuild a SharePoint library.
If your users basically need a library with views, metadata, search, permissions and Copilot, use SharePoint. Full stop.
SPE gets compelling when SharePoint isn’t the destination at all. The destination is your claims app, legal platform, SaaS product, customer portal, etc., and documents are just one part of that experience.
In that model, your app owns the UX, while SPE gives it Microsoft 365-backed content. For AI scenarios, that content can also be used to ground custom agents through Foundry or the Microsoft 365 Copilot Retrieval API.
So the decision isn’t really“Which has the better document library?” SharePoint obviously wins that comparison.
The better question is“Should my users be working in SharePoint, or should SharePoint capabilities be working inside my application?”
That’s where I see the SPE line.
I literally just had a customer tell me earlier today on a webinar "We just had an issue with SPO modification from users that messed up our app! Great timing!!!"
That's what our goal is with the new SharePoint Admin Center integration.