managed
We hold the credentials
WPIntegrate runs the client-credentials flow for your tenant. Your administrator grants consent once and is not asked again.
Coming soon — in testing, not yet released
Microsoft 365 Search
Microsoft 365 Search puts one search box over SharePoint and OneDrive on any page, with result tabs, filters and Microsoft’s own result layouts — and on a SharePoint page, each person sees only what they can already open.
Microsoft 365 Search is built, and is being tested against real tenants before it is released. Nothing on this page can be bought or embedded yet, and what people ask for is what sets the order things are released in.
hollins group
Microsoft 365 Search itself, running here: the same bundle the released components load, against sample data of our own invention rather than a customer’s tenant. It is not yet released, so there is no embed key to hand out — this frame uses a public demo key.
Putting it on the page
The pattern it follows.
Microsoft 365 Search is not released, so there is no embed key to hand out and nothing here to paste yet. It is built on the same script-plus-custom-element pattern as every released component, described below.
What it does
How it works
The Microsoft 365 Search component runs a search through Microsoft’s own search index and shows the results the way Microsoft 365 does: a tab for each kind of content, filters for file type and date, a sort, spelling suggestions, and a row for each result that says what it is, where it lives and who changed it last. Results from a connector, such as a knowledge base indexed into Microsoft Search, are drawn with the result layout your administrator designed for it.
Why it exists
An intranet page that links to six libraries asks people to know which library holds the thing they want. Search answers the question they actually have. The usual ways to put it on a page either mean building against the Graph API yourself, or adopting Microsoft’s own Graph Toolkit components, which Microsoft retired in August 2026.
- Element
<wpi-search>- Reads from
- SharePoint sites, lists and libraries, OneDrive for Business, Microsoft Search connectors (signed-in only)
- Arrangements
- 4 in the builder
- Graph access
managedorproxy— the tenant chooses
Arrangements in the builder
- Search box with a visible label, tabs, filter menus and paging
- A result row per hit: icon, title, highlighted extract, location and author
- Connector results in their administrator-designed layout
- Opens on results for a query of your choice, or on an empty box
Where it runs
Anywhere you can paste two lines of HTML
A custom element needs no build step and no framework, so where your site is built is not a question you have to answer before this one.
- WordPress
- Webflow
- Squarespace
- Shopify
- Wix
- Astro
- Next.js
- Drupal
- SharePoint pages
- Plain HTML
Named as examples of places HTML can be pasted. No partnership is implied, none of these are customers, and the marks beside them are our own drawings rather than any vendor's logo. WordPress is the one that gets more than an embed — the same Microsoft 365 jobs also ship as plugins with a Gutenberg block.
In detail
Everything Microsoft 365 Search does.
6 capabilities, every one of them resolved from the embed key rather than written into the page — once the keys are issued.
-
Signed in: Microsoft decides what each person sees
On a SharePoint page the search runs as the person looking at it, so the results are exactly the files and sites they could already open, trimmed by Microsoft rather than by us. Their token goes from the page straight to Microsoft; it never reaches a WPI server, and neither do their results.
-
Public: confined to the sites you choose
On a public website the search covers only the sites or libraries you list, and only content that is shared rather than anyone’s private files. The limit is applied three times — in the query, again on every result Microsoft returns, and again in what each result is allowed to carry — so a result from outside the list is dropped even if the query let it through.
-
Tabs that follow Microsoft’s own rules
Microsoft Search can only rank some kinds of content together: files and sites in one list, mail in another. Each tab is one of those groups, so the builder offers tabs that work rather than letting you combine content Microsoft will refuse to search together.
-
Filters and sort above the results
File type, date modified and size filters, with a count beside each choice and a chip for each one applied. Sorting by date is available where Microsoft supports it: files, list items and sites.
-
Your connector layouts, not ours
When your administrator has designed a result layout for a Microsoft Search connector, the component draws it. It supports the parts of Adaptive Cards that search layouts use; a layout that uses more than that falls back to the standard result row rather than rendering half of it.
-
Suggestions as you type
Recent searches from the same browser, and for a signed-in person the top matching titles. A public page suggests only recent searches, so a busy page’s typing never uses up its search allowance.
Tell us you are waiting on this one.
Microsoft 365 Search is in testing and no release date is announced. What people ask for is what sets the order things are released in, so a sentence about your case is worth more here than a waiting list.
Reaching your tenant
Two ways for us to reach Graph. One of them never lets us.
Every tenant runs in one mode or the other, and the choice belongs to your IT rather than to us. It is the reason this works inside organisations that will not delegate Graph access to a vendor.
proxy
You hold the credentials
You supply a base URL and an API key for your own gateway. We store that key encrypted at rest and never hold a Graph token at all.
Questions
What people ask about this one.
If yours is not here, ask it — the answers come back from a person rather than a form.
Can we use Microsoft 365 Search yet?
Not yet. It is in beta and has not been released to customers, so it cannot be created in a customer dashboard or embedded on a site.
Where does signed-in search work?
On SharePoint pages, through the WPI web part, once a SharePoint administrator approves two read permissions — Files.Read.All and Sites.Read.All — on the API access page. Teams is not supported yet: a Teams tab is not handed a token Microsoft Search will accept, and the exchange that would fix that is designed but not built.
Can it search mail, calendars and Teams messages?
The component can, for a signed-in person, but not inside SharePoint today: the web part asks only for file and site permissions, so those tabs are not available there. Public search never covers them — they belong to individual people.
Has the public mode been tested against a real tenant?
Yes, on our own: scoped to one document library, a word that matched 66 files in the tenant’s main site matched none in that library, every result returned sat inside it, and a query written to break out of the scope did not. That covered files; list items need a permission the test app did not hold, so they were not part of it.
Does it find part of a word?
No. Microsoft’s index matches whole words, so “utloo” does not find “Outlook”. Wildcards are not offered either: the search box treats every character as part of the words you are looking for.