Windows Search web search provider

Damoon Haji Rostami 20 Reputation points
2025-08-25T21:10:02.0866667+00:00

Dear Microsoft Support Team,

I am currently working on integrating a custom enterprise search experience into Windows. While reviewing the documentation on the Windows Search Provider App Extension, I found that the manifest requires:

<uap3:AppExtension

Name="com.microsoft.windows.websearchprovider"

...

/>

I would like clarification on two points:

Taskbar / Start Menu Integration

Is it possible to specify a different Name value (e.g., a custom identifier) instead of com.microsoft.windows.websearchprovider, in order to register my own search provider that integrates directly with the Windows Taskbar or Start Menu search box?

  Or is this extension name reserved exclusively for Microsoft’s built-in web search provider (Bing), making it impossible for third-party developers to fully integrate at the taskbar level?
  
  **Cookie and Session Handling**
  
     When Windows Taskbar / Start Menu search invokes a registered search provider, is there a supported way to handle cookies or authentication sessions (e.g., passing and persisting authentication cookies between requests)?
     
        If so, what mechanism should developers use to manage these cookies?
        

My goal is to understand whether a third-party search backend can officially integrate with the taskbar / Start Menu search surface, or whether the extension point is restricted to system components only.

Any clarification or official guidance you can provide on these integration possibilities would be greatly appreciated.

Best regards,

Damoon

Developer technologies | C#
0 comments No comments
{count} votes

Accepted answer
  1. Bruce (SqlWork.com) 79,526 Reputation points Volunteer Moderator
    2025-08-25T22:22:03.7666667+00:00

    the Windows Search Provider App Extension lets you replace bing with your own search engine. the MISX package just registers an extension that will be used by the builtin server provider. It does not replace the search provider, the extension just specifies the url to call for search.

    so the "com.microsoft.windows.websearchprovider" just specifies the component the extension will be used by. you can not change this.

    your WISX component just registers the url of your custom server provider, and a couple formatting options. your custom url endpoint will respond to get request with a json response. as there is no UI, so there is no authentication. not sure if cookies are supported, but they would be treated as 3rd party cookies so might be stripped.

    note: this feature is only available in the EU.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.