Skip to content

Commit 6a1a1b8

Browse files
Merge branch 'main' into Ankur/update-msix-privacy-policy-docs
2 parents e481fe8 + 2fedf5e commit 6a1a1b8

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

58 files changed

+1289
-1233
lines changed

.openpublishing.redirection.json

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,11 @@
11
{
22
"redirections": [
3-
{
3+
{
4+
"source_path": "hub/apps/whats-new/latest-docs-updates.md",
5+
"redirect_url": "https://learn.microsoft.com/windows/apps/whats-new/windows-11-build-22000",
6+
"redirect_document_id": false
7+
},
8+
{
49
"source_path": "hub/apps/design/devices/kinect-for-windows.md",
510
"redirect_url": "https://azure.microsoft.com/en-us/products/kinect-dk",
611
"redirect_document_id": false

hub/apps/develop/actions/action-json.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -35,23 +35,21 @@ This article describes the format of the action definition JSON file format for
3535
"inputCombinations": [
3636
{
3737
"inputs": ["UserFriendlyName"],
38-
"description": "Greet ${UserFriendlyName.Text}"
38+
"description": "Greet ${UserFriendlyName.Text}",
39+
"where": [
40+
"${UserFriendlyName.Length} > 3"
41+
]
3942
},
4043
{
4144
"inputs": ["UserFriendlyName", "PetName"],
42-
"description": "Greet ${UserFriendlyName.Text} and their pet ${PetName.Text}"
45+
"description": "Greet ${UserFriendlyName.Text} and their pet ${PetName.Text}"
4346
}
4447
],
4548
"contentAgeRating": "child",
4649
"invocation":
4750
{
48-
{
4951
"type": "Uri",
5052
"uri": "contoso://greetUser?userName=${UserFriendlyName.Text}&petName=${PetName.Text}",
51-
},
52-
"where": [
53-
"${UserFriendlyName.Length > 3}"
54-
]
5553
}
5654
},
5755
{
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
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).
Loading

hub/apps/develop/search/index.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
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. |

hub/apps/develop/search/search-providers.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Windows Search providers
2+
title: Windows Search web search providers
33
description: Learn how to integrate into the Windows Search experience.
44
ms.topic: article
55
ms.date: 09/07/2023
@@ -8,18 +8,13 @@ ms.localizationpriority: medium
88

99

1010

11-
# Windows Search providers
11+
# Windows Search web search providers
1212

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.
1914

2015
:::image type="content" source="images/search-integration.png" alt-text="Screenshot of the Windows Search UI with 3rd party search provider integration.":::
2116

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.
2318

2419
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).
2520

@@ -66,7 +61,7 @@ The protocol schema that will be used when launching the provided web search res
6661

6762
#### DynamicContentEndpoint
6863

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.
7065

7166

7267
### Example package manifest file
@@ -174,6 +169,9 @@ Search providers must support the OPTIONS request method and respond to this req
174169

175170
## Implement a gleam icon endpoint
176171

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+
177175
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.
178176

179177
### Gleam icon HTTPS request format

hub/apps/develop/security/windows-hello.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -37,13 +37,13 @@ The common approach of using an email address as the username makes a bad proble
3737

3838
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.
3939

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.
4141

4242
## What is Windows Hello?
4343

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.
4545

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.
4747

4848
### Windows Hello authentication
4949

@@ -53,7 +53,7 @@ Windows Hello is not just a replacement for traditional 2FA systems, though. It
5353

5454
### How Windows Hello works
5555

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.
5757

5858
To enable Windows Hello on a device, the user must have either their Microsoft Entra ID account or Microsoft Account connected in Windows settings.
5959

hub/apps/develop/windows-integration/integrate-sharesheet-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,4 +34,4 @@ In this comprehensive guide, you'll learn how to add the share feature to your p
3434
- [Advantages and Disadvantages of packaging an application - Deployment overview](/windows/apps/package-and-deploy/#advantages-and-disadvantages-of-packaging-your-app)
3535
- [Identity, Registration and Activation of Non-packaged Win32 Apps](https://blogs.windows.com/windowsdeveloper/2019/10/29/identity-registration-and-activation-of-non-packaged-win32-apps/)
3636
- [Share Contract Implementation for WinAppSDK App](https://github.com/kmahone/WindowsAppSDK-Samples/tree/user/kmahone/shareapp/Samples/AppLifecycle/ShareTarget/WinUI-CS-ShareTargetSampleApp)
37-
- [Share Contract Implementation for Apps Packaged with External Location](https://github.com/microsoft/AppModelSamples/blob/master/Samples/SparsePackages/PhotoStoreDemo/StartUp.cs)
37+
- [Share Contract Implementation for Apps Packaged with External Location](https://github.com/microsoft/AppModelSamples/blob/master/Samples/PackageWithExternalLocation/cs/PhotoStoreDemo/StartUp.cs)

hub/apps/develop/windows-integration/integrate-sharesheet-packaged.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ public static void Main(string[] cmdArgs)
8686
}
8787
```
8888

89-
See the [Photo Store Demo](https://github.com/microsoft/AppModelSamples/blob/master/Samples/SparsePackages/PhotoStoreDemo/StartUp.cs) app for a complete implementation.
89+
See the [Photo Store Demo](https://github.com/microsoft/AppModelSamples/blob/master/Samples/PackageWithExternalLocation/cs/PhotoStoreDemo/StartUp.cs) app for a complete implementation.
9090

9191
## Handle shared files
9292

@@ -128,6 +128,6 @@ static async void HandleShareAsync(ShareTargetActivatedEventArgs args)
128128
- [Advantages and Disadvantages of packaging an application - Deployment overview](/windows/apps/package-and-deploy/#advantages-and-disadvantages-of-packaging-your-app)
129129
- [Identity, Registration and Activation of Non-packaged Win32 Apps](https://blogs.windows.com/windowsdeveloper/2019/10/29/identity-registration-and-activation-of-non-packaged-win32-apps/)
130130
- [Share Contract Implementation for WinAppSDK App](https://github.com/kmahone/WindowsAppSDK-Samples/tree/user/kmahone/shareapp/Samples/AppLifecycle/ShareTarget/WinUI-CS-ShareTargetSampleApp)
131-
- [Share Contract Implementation for Apps Packaged with External Location](https://github.com/microsoft/AppModelSamples/blob/master/Samples/SparsePackages/PhotoStoreDemo/StartUp.cs)
131+
- [Share Contract Implementation for Apps Packaged with External Location](https://github.com/microsoft/AppModelSamples/blob/master/Samples/PackageWithExternalLocation/cs/PhotoStoreDemo/StartUp.cs)
132132
- [Get activation info for packaged apps](/windows/apps/desktop/modernize/get-activation-info-for-packaged-apps)
133133
- [ShareTarget schema reference](/uwp/schemas/appxpackage/uapmanifestschema/element-uap-sharetarget)

hub/apps/develop/windows-integration/integrate-sharesheet-unpackaged.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ The second way to give your app package identity is to add a package with extern
4343

4444
Documentation on how to create a package with external location is available here, including information on templates to use: [Grant package identity by packaging with external location](/windows/apps/desktop/modernize/grant-identity-to-nonpackaged-apps).
4545

46-
The full sample app is available on GitHub: [SparsePackages (Packaged with External Location)](https://github.com/microsoft/AppModelSamples/tree/master/Samples/SparsePackages).
46+
The full sample app is available on GitHub: [Packaged with External Location](https://github.com/microsoft/AppModelSamples/tree/master/Samples/PackageWithExternalLocation).
4747

4848
## Register as a Share Target
4949

@@ -263,4 +263,4 @@ The following video demonstrates how an unpackaged app can be a share target aft
263263
- [Advantages and Disadvantages of packaging an application - Deployment overview](/windows/apps/package-and-deploy/#advantages-and-disadvantages-of-packaging-your-app)
264264
- [Identity, Registration and Activation of Non-packaged Win32 Apps](https://blogs.windows.com/windowsdeveloper/2019/10/29/identity-registration-and-activation-of-non-packaged-win32-apps/)
265265
- [Share Contract Implementation for WinAppSDK App](https://github.com/kmahone/WindowsAppSDK-Samples/tree/user/kmahone/shareapp/Samples/AppLifecycle/ShareTarget/WinUI-CS-ShareTargetSampleApp)
266-
- [Share Contract Implementation for Apps Packaged with External Location](https://github.com/microsoft/AppModelSamples/tree/master/Samples/SparsePackages)
266+
- [Share Contract Implementation for Apps Packaged with External Location](https://github.com/microsoft/AppModelSamples/tree/master/Samples/PackageWithExternalLocation)

hub/apps/get-started/images/WASDK.png

102 KB
Loading

hub/apps/get-started/images/WCT.png

195 KB
Loading
153 KB
Loading

0 commit comments

Comments
 (0)