SharePoint SPFx builds Copilot search demo

Key insights

• Microsoft demoed Copilot search functionality in SharePoint using an SPFx extension.
• The session explains where the Microsoft 365 Copilot Search API fits in the Copilot APIs ecosystem.
• Microsoft also covers how it differs from Microsoft Graph Search.
• The demo shows which delegated permissions are needed.
• An SPFx extension can call the beta Copilot Search endpoint through Microsoft Graph client v3.

Microsoft recently published a YouTube demo titled Build Copilot search functionality in SharePoint using an SPFx extension. In the session, Mohammed Amer shows how an SPFx extension can add Copilot search behavior to SharePoint and connect that experience to Microsoft 365 Copilot. The main takeaway is straightforward: developers can build a custom search experience that runs through Copilot instead of relying only on standard search output.

The video is part of a Microsoft 365 and Power Platform Community call, and Microsoft also points viewers to documentation for the Microsoft 365 Copilot APIs, the Copilot Search API, and the preview overview of that API. The description makes clear that the demo is not just a walkthrough of a UI; it also places the Copilot Search API in context, compares it with Microsoft Graph Search, and shows the permission model involved.

What's new

The new piece here is the combination of SharePoint Framework and the Microsoft 365 Copilot Search API. Microsoft presents an SPFx extension as the way to build Copilot search functionality inside SharePoint, with the extension calling the beta Copilot Search endpoint through Microsoft Graph client v3. That means the developer experience is not limited to a plain text answer. It can be a purpose-built search interface that is driven by Copilot but still grounded in SharePoint content.

Microsoft says the demo explains where the Copilot Search API fits in the Copilot APIs ecosystem and how it differs from Microsoft Graph Search. The material also says the session covers what the API can and cannot do in preview, which is useful because preview features often have boundaries that matter in production planning.

Why it matters

This is most relevant for SharePoint and Microsoft 365 developers who need a search experience tailored to a specific business scenario. A generic search box may be enough for broad discovery, but the approach shown here can be used when users need a more guided experience for SharePoint content. The source material does not name specific license requirements or tenant-wide availability, so readers should treat this as a developer-focused demo rather than a finished deployment guide.

For admins and solution owners, the interest is in control and permissions. The description says the demo covers delegated permissions, which indicates the component runs in the signed-in user’s context rather than bypassing their access model. That matters if the search experience is meant to surface documents, lists, or other SharePoint items without exposing content a user should not see. For makers and developers, the value is that the Copilot response can be shaped into a custom interface instead of a plain result list.

Readers who already track Developer Tools and Microsoft 365 changes will recognize the pattern: Microsoft is extending app frameworks into Copilot scenarios, not replacing them. The practical effect is a search experience that can stay inside the Copilot flow while still using SharePoint data.

How it works

The source material describes a flow in which an SPFx extension calls the beta Copilot Search endpoint through Microsoft Graph client v3. It also says the demo explains the Microsoft 365 Copilot Search API, how it relates to the wider Copilot APIs ecosystem, and how it differs from Microsoft Graph Search. Microsoft links to the Copilot APIs overview, the search how-to, and the preview overview for readers who want the supporting documentation.

1. The developer builds an SPFx extension for the SharePoint scenario.
2. The extension is used to connect SharePoint content with Copilot search functionality.
3. Delegated permissions are used so the experience works in the signed-in user’s context.
4. The SPFx solution calls the beta Copilot Search endpoint through Microsoft Graph client v3.
5. The Copilot Search API returns results that the extension can present in a custom interface.

The demo description does not provide a full code sample in the text we received, so the exact component structure and UI logic are not visible here. Still, Microsoft is clear that the API and the SPFx extension work together, and that the session is intended to show the search pattern rather than a single isolated call.

Limitations and open questions

The most important limitation is that the video description says the Copilot Search API is in preview, and it explicitly mentions what it can and cannot do in that state. The source material does not list those limits in detail, so we cannot say more than that the preview behavior is not final. It also says the extension uses the beta Copilot Search endpoint, which signals that the implementation is not based on a fully stabilized API.

The material does not state tenant availability, licensing, rollout timing, or production support boundaries. It also does not list the exact delegated permissions in the transcript snippet we received, even though it says those permissions are covered in the demo. Because of that, readers who plan to use this pattern should consult the linked Microsoft documentation before treating the demo as a deployment reference.

Another open question is how far the custom UI can be pushed in practice. The source says the experience can be interactive and custom, but it does not spell out the limits of the rendered interface in this excerpt. Microsoft’s documentation links are the right place to confirm what the API supports and how the SharePoint Copilot app model is expected to behave.

Sources

• Microsoft YouTube demo: Build Copilot search functionality in SharePoint using an SPFx extension
• Microsoft 365 Copilot APIs overview
• Perform search using the Microsoft 365 Copilot Search API
• Overview of the Microsoft 365 Copilot Search API preview

Frequently asked questions

What does the demo show?

It shows how to build Copilot search functionality in SharePoint using an SPFx extension. Microsoft says the session also explains where the Copilot Search API fits, how it differs from Microsoft Graph Search, and what preview limits apply.

Why use SPFx for this scenario?

SPFx lets developers package and deploy the solution as a SharePoint extension. The demo shows that it can call the Copilot Search endpoint and present the results in a custom interface.

Does the source material list the exact permissions needed?

It says delegated permissions are needed, but the provided text does not list each permission name. Microsoft points to the linked documentation for the broader API context.