Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Overview
Windows App utilizes connected experiences to enhance user functionality and engagement. These connected experiences require the collection and processing of specific data, referred to as required client data. This data is essential for ensuring the security, performance, and functionality of the connected experiences.
Scope of this documentation
This document covers telemetry sent from the client and doesn't include telemetry data sent by the service or protocol layers or to installations in Azure China. For installations located in Azure China, client telemetry won't be sent.
Types of client data
Required client data
Required client data is separate from required service data, which relates to information about the use and health of Azure Virtual Desktop, Windows 365, and Microsoft Dev Box connections.
Optional client data
At this time, optional data isn't enabled for Windows App on Windows. Windows App on macOS and iOS collect optional data for Remote Desktop Services and offer a toggle in the app settings to disable optional data.
Categories of required client data
Required client data is organized into the following categories:
Windows App Setup and Inventory: Information related to the initial setup and inventory of the software.
Product and Service Usage: Data indicating whether the connection completed successfully.
Product and Service Performance: Information covering unexpected issues (crashes), poor response times, performance, or errors in functionality.
Device Connectivity and Configuration: Data about the device's connectivity and configuration to ensure that connections perform as expected.
Examples of required client data
Start-up of Windows App
This data ensures that we're able to monitor app startup time so that we can monitor improvements and track potential issues.
Client version
The client version allows Microsoft to understand what client versions are in use across platforms.
MAM enrollment
Where Mobile Application Management is supported, data is collected to track enrollment and which features are in use. This data is used to evaluate MAM effectiveness and usage.