You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn about cloud files provider integration with Windows Search.
3
+
title: Cloud files provider integration with Windows Search
4
+
ms.topic: article
5
+
ms.date: 05/08/2025
6
+
ms.localizationpriority: medium
7
+
---
8
+
9
+
# Cloud files provider integration with Windows Search
10
+
11
+
Windows Search integrates with Cloud Sync Engines. When searching for files, Windows Search will call into all registered cloud files providers. Cloud files providers must implement [IStorageProviderSearchHandlerFactory](/uwp/api/windows.storage.provider.istorageprovidersearchhandlerfactory) in order to be integrated into the Windows Search experience. For more information about implementing a Cloud Sync Engine, see [Cloud Sync Engines](/windows/win32/cfapi/cloud-files-api-portal).
description: This section of the documentation provides developer guidance for integrating with Windows Search.
3
+
title: Integrate with Windows Search
4
+
ms.topic: article
5
+
ms.date: 05/08/2025
6
+
ms.localizationpriority: medium
7
+
---
8
+
9
+
# Integrate with Windows Search
10
+
11
+
This section of the documentation provides developer guidance for integrating with Windows Search.
12
+
13
+
## Windows system components that support 3rd party integration
14
+
15
+
The following table lists the Windows Search integration features for 3rd party developers.
16
+
17
+
| Feature | Description |
18
+
|--|--|
19
+
|[Web search providers](search-providers.md)| Learn how to integrate a web search provider with Windows. Only available the European Economic Area (EEA). |
20
+
|[Cloud files provider integration with Windows Search](cloud-search-integration.md)| Learn about cloud file provider integration with Windows Search. |
Copy file name to clipboardExpand all lines: hub/apps/develop/search/search-providers.md
+8-10Lines changed: 8 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Windows Search providers
2
+
title: Windows Search web search providers
3
3
description: Learn how to integrate into the Windows Search experience.
4
4
ms.topic: article
5
5
ms.date: 09/07/2023
@@ -8,18 +8,13 @@ ms.localizationpriority: medium
8
8
9
9
10
10
11
-
# Windows Search providers
11
+
# Windows Search web search providers
12
12
13
-
> [!NOTE]
14
-
> **Some information relates to pre-released product, which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.**
15
-
> [!IMPORTANT]
16
-
> The feature described in this topic is available in preview builds of Windows starting with build 22631.2787 for Windows 11 and build 19045.3758 for Windows 10, although newer builds are recommended because they contain stability improvements. For information on preview builds of Windows, see [Windows 10 Insider Preview](https://insider.windows.com/en-us/preview-windows).
17
-
18
-
Windows Search currently uses the Web Search from Microsoft Bing app to return web content and search results. In the European Economic Area (EEA), you can enable installed apps that implement a web search provider to return web content and search results in Windows Search through Settings.
13
+
Windows Search currently uses the Web Search from Microsoft Bing app to return web content and search results. In the European Economic Area (EEA), you can install apps that implement a web search provider to return web content and search results in Windows Search.
19
14
20
15
:::image type="content" source="images/search-integration.png" alt-text="Screenshot of the Windows Search UI with 3rd party search provider integration.":::
21
16
22
-
Search providers integrate with the Search experience by creating an [MSIX package](/windows/msix/) with a package manifest file that provides the required information for the OS to register the search provider. Users can add a search provider to Windows by installing the associated app package and can remove the search provider through the **Add or remove programs** page in Windows Settings app.
17
+
Search providers integrate with the Search experience by creating an [MSIX package](/windows/msix/) with a package manifest file that provides the required information for the OS to register the search provider. After installation, the search provider is enabled by default in Windows Search experiences. In the Windows Settings app, users can enable and disable installed search providers and manage the order of providers in search results. Users can remove a search provider through the **Settings > Apps > Installed apps** page in Windows Settings app.
23
18
24
19
For development and testing, when Developer Mode is enabled and the search provider app has been sideloaded on the device, it will appear in the list of available search providers. For more information, see [Developer Mode features and debugging](/windows/apps/get-started/developer-mode-features-and-debugging).
25
20
@@ -66,7 +61,7 @@ The protocol schema that will be used when launching the provided web search res
66
61
67
62
#### DynamicContentEndpoint
68
63
69
-
The URL of the HTTPS endpoint to which the OS will send a request for the gleam icon to be displayed in the search box. For more information see [Implement a gleam icon endpoint](#implement-a-gleam-icon-endpoint). This feature is supported starting with Windows 10 build 19045.4233 and Windows 11 build 22621.3371.
64
+
This feature is no longer supported. For more information see [Implement a gleam icon endpoint](#implement-a-gleam-icon-endpoint). The URL of the HTTPS endpoint to which the OS will send a request for the gleam icon to be displayed in the search box.
70
65
71
66
72
67
### Example package manifest file
@@ -174,6 +169,9 @@ Search providers must support the OPTIONS request method and respond to this req
174
169
175
170
## Implement a gleam icon endpoint
176
171
172
+
> [!NOTE]
173
+
> This gleam feature is no longer enabled. Gleam icons are no longer displayed for all web providers in the EEA. The content in this section of the documentation is obsolete.
174
+
177
175
Search providers can optionally provide light and dark mode gleam icons that are displayed in the search bar when the search provider is currently enabled. When the **DynamicContentEndpoint** element is provided in the app manifest, a request will be sent to the specified URL and the search provider responds with a json file in the format defined below that includes the URLs of the icon image files and other metadata. The gleam icon request will be sent periodically while the search provider is the most recent provider active in Windows Search. The cadence for this request is every 6 hours. A request will also be sent upon each Search launch and on device unlock.
Copy file name to clipboardExpand all lines: hub/apps/develop/security/windows-hello.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -37,13 +37,13 @@ The common approach of using an email address as the username makes a bad proble
37
37
38
38
Solving the problems that passwords pose is tricky. Tightening password policies alone will not do it; users may just recycle, share, or write down passwords. Although user education is critical for authentication security, education alone does not eliminate the problem either.
39
39
40
-
Windows Hello replaces passwords with strong two-factor authentication (2FA) by verifying existing credentials and by creating a device-specific credential that a biometric or PIN-based user gesture protects.
40
+
Windows Hello replaces passwords with strong **two-factor authentication** (**2FA**) by verifying existing credentials and by creating a device-specific credential that a biometric or PIN-based user gesture protects.
41
41
42
42
## What is Windows Hello?
43
43
44
-
Windows Hello is the name Microsoft has given to the new biometric sign-in system built into Windows. Because it is built directly into the operating system, Windows Hello allows face or fingerprint identification to unlock users’ devices. Authentication happens when the user supplies his or her unique biometric identifier to access the device-specific credentials, which means that an attacker who steals the device can’t log on to it unless that attacker has the PIN. The Windows secure credential store protects biometric data on the device. By using Windows Hello to unlock a device, the authorized user gains access to all of his or her Windows experience, apps, data, websites, and services.
44
+
Windows Hello is a biometric sign-in system built into Windows that lets you use your face, fingerprint, or a PIN to unlock your device. It replaces traditional passwords with a more secure and convenient method. Your biometric data is stored securely on your device, and even if someone steals your device, they cannot access it without your PIN or biometric gesture. Once unlocked, you can access your apps, data, and services seamlessly.
45
45
46
-
The Windows Hello authenticator is known as a Hello. A Hello is unique to the combination of an individual device and a specific user. It does not roam across devices, is not shared with a server or calling app, and cannot easily be extracted from a device. If multiple users share a device, each user needs to set up his or her own account. Every account gets a unique Hello for that device. You can think of a Hello as a token you can use to unlock (or release) a stored credential. The Hello itself does not authenticate you to an app or service, but it releases credentials that can. In other words, the Hello is not a user credential but it is a second factor for the authenticating process.
46
+
The Windows Hello authenticator is known as a Hello. Each Hello is unique to a specific user and device. It doesn’t sync across devices or share data with servers or apps. If multiple people use the same device, each person needs to set up their own Windows Hello configuration. This configuration is tied to their credentials on that specific device. Think of a Hello as a key that unlocks your stored credentials, which are then used to sign in to apps or services. It’s not a credential itself but acts as a second layer of security during authentication.
47
47
48
48
### Windows Hello authentication
49
49
@@ -53,7 +53,7 @@ Windows Hello is not just a replacement for traditional 2FA systems, though. It
53
53
54
54
### How Windows Hello works
55
55
56
-
When the user sets up Windows Hello on his or her machine, it generates a new public–private key pair on the device. The [trusted platform module](/windows/keep-secure/trusted-platform-module-overview) (TPM) generates and protects this private key. If the device does not have a TPM chip, the private key is encrypted and protected by software. In addition TPM-enabled devices generate a block of data that can be used to attest that a key is bound to TPM. This attestation information can be used in your solution to decide if the user is granted a different authorization level for example.
56
+
When the user sets up Windows Hello on their machine, it generates a new public–private key pair on the device. The [trusted platform module](/windows/keep-secure/trusted-platform-module-overview) (TPM) generates and protects this private key. If the device does not have a TPM chip, the private key is encrypted and protected by software. In addition TPM-enabled devices generate a block of data that can be used to attest that a key is bound to TPM. This attestation information can be used in your solution to decide if the user is granted a different authorization level for example.
57
57
58
58
To enable Windows Hello on a device, the user must have either their Microsoft Entra ID account or Microsoft Account connected in Windows settings.
Copy file name to clipboardExpand all lines: hub/apps/publish/publish-your-app/msi/support-info.md
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -6,28 +6,28 @@ ms.topic: article
6
6
ms.localizationpriority: medium
7
7
---
8
8
9
-
# Support info for MSI/EXE app
9
+
# Privacy policy and support info
10
10
11
-
This section lets you provide info to help customers understand more about your app and how to get support.
12
-
13
-
:::image type="content" source="images/msiexe-support-info.png" lightbox="images/msiexe-support-info.png" alt-text="A screenshot of the Properties section where you can provide support info for your app.":::
11
+
## Privacy policy
14
12
15
-
## Does this product access, collect or transmit personal information (data that could be used to identity a person)?
13
+
You are responsible for ensuring your app complies with privacy laws and regulations, and for providing a valid privacy policy, if required.
16
14
17
-
_Required_
15
+
In this section, you must indicate whether or not your app accesses, collects, or transmits any [personal information](../../store-policies.md#105-personal-information). If you answer **Yes**, a privacy policy is required. Otherwise, it is optional.
18
16
19
-
You are responsible for ensuring your app complies with applicable privacy laws and regulations, and for providing a valid privacy policy URL here if required.
17
+
If you already have a privacy policy hosted on your domain, you can directly provide that link. Otherwise, you can also provide the privacy policy text directly. The Store will use this privacy policy content for all the markets where your product is published.
20
18
21
-
In this section, you must indicate whether your app accesses, collects, or transmits any [personal information](../../store-policies.md#105-personal-information). If you answer Yes, a privacypolicy URL is required. Otherwise, it is optional (though if we determine that your app requires a privacy policy, and you have not provided one, your submission may fail certification).
19
+
:::image type="content" source="images/msiexe-privacy-policy.png" lightbox="images/msiexe-privacy-policy.png" alt-text="A screenshot showing the privacy policy options for a developer.":::
22
20
23
21
To help you determine if your app requires a privacy policy, review the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) and the [Microsoft Store Policies](../../store-policies.md#105-personal-information).
24
22
25
23
> [!NOTE]
26
-
> Microsoft does not provide a default privacy policy for your app, and your app is not covered by any Microsoft privacy policy.
24
+
> Microsoft doesn't provide a default privacy policy for your app. Likewise, your app is not covered by any Microsoft privacy policy.
27
25
28
-
## Privacy policy URL
26
+
## Support info
29
27
30
-
_Required only if you answered yes to the previous question_
28
+
This section lets you provide info to help customers understand more about your app and how to get support.
29
+
30
+
:::image type="content" source="images/msiexe-support-info.png" lightbox="images/msiexe-support-info.png" alt-text="A screenshot of the Properties section where you can provide support info for your app.":::
0 commit comments