A finished presentation is only useful to your team if they can find it. Anand explains the Document Submission Form, a custom app that brings SharePoint document contributions into Microsoft 365 Copilot Chat, with a preconfigured Knowledge Base destination and the flexibility to choose another library. The same form also works on a SharePoint page for colleagues who prefer to start there.
What we cover in this episode:
- The 4-step interruption: Why finished presentations and documents get stuck between a Copilot conversation and your team's SharePoint library.
- One form, two places: How the same component sits on a SharePoint page for colleagues who start from the intranet, and opens inline inside Microsoft 365 Copilot Chat when you're already working in chat.
- Built-in Home Base: Pre-configuring your team's default SharePoint site URL and destination library (Knowledge Base) so you don't have to look up an address every time—while still letting you switch destinations when a file belongs in another team's library.
- Library fields & permissions: Bringing in required and optional fields (Document Title, Category, Status) from the destination library automatically, and uploading with your existing SharePoint permissions.
- Boundaries & IT deployment: Microsoft 365 Copilot license requirements for the in-chat experience vs. standard SharePoint access on a SharePoint page, IT administrator deployment via the SharePoint App Catalog, and keeping destinations scoped within your company's SharePoint tenant.
Chapters:
(00:00) Finishing a presentation in Copilot — and the 4-step sharing interruption
(00:26) Meet the Document Submission Form
(00:46) One form, two places: on a SharePoint Knowledge Hub page
(01:09) Submitting a document inline inside Microsoft 365 Copilot Chat
(01:33) Configured Home Base: Site URL & Knowledge Base pre-filled
(01:55) Changing the destination library when needed
(02:19) The moment useful work becomes shared knowledge
(02:40) Destination library fields & your existing SharePoint permissions
(03:03) Boundaries: Microsoft 365 Copilot license vs. SharePoint access & IT deployment
(03:28) Under the hood: SharePoint Framework (SPFx) & tenant boundary
(03:51) How to start with your team & PnP Community contribution
Source and implementation:
Document Submission Form contribution, pull request #73: https://github.com/pnp/spfx-copilot-components/pull/73
Deployment uses SharePoint Framework version 1.24, the SharePoint App Catalog, and Sync to Teams. The in-chat experience requires a Microsoft 365 Copilot license; the SharePoint page version requires appropriate SharePoint access.
Fler avsnitt från "Tech Ease"



Missa inte ett avsnitt av “Tech Ease” och prenumerera på det i GetPodcast-appen.








