Describe the bug
We use the appinstaller and while the app is checking for updates, or downloading updates in the background, certain telemetry is generated and also the requests sent to our CDN contain a special header.
A, ms-cv header added to requests made to our CDN endpoints
When the app's checking for updates, the MS-CV header is added to the requests. Seems like this is a correlation vector, which is useful for diagnosing issues. On the other hand, users might get the impression that we track them and send client identifiers (ms-cv looks like one) to our servers.
B, Microsoft.OSG.DU.DeliveryOptClient.DownloadStarted and Microsoft.OSG.DU.DeliveryOptClient.DownloadCompleted diagnostics
It doesn't matter if user chose "optional" or "required" diagnostics in the system settings, these events are sent to Microsoft servers, with a payload like the one below. I understand why this is required for keeping OS services, OS components and OS apps healthy, but I would like to ask if it's possible to opt-out of these diagnostics events.
Expected behavior
The ability to opt-out of the diagnostics and special headers using MSIX / Appintsaller / PackageManager APIs.
The only workaround we have so far is to download the updates manually (from our code) and use PackageManager.AddPackageByUriAsync + file:///C:/..../updates/update.msixbundle. The biggest downside is that we would lose the incremental updates ability.
Project MSIX SDK
Describe the bug We use the appinstaller and while the app is checking for updates, or downloading updates in the background, certain telemetry is generated and also the requests sent to our CDN contain a special header.
A,
ms-cv
header added to requests made to our CDN endpointsWhen the app's checking for updates, the MS-CV header is added to the requests. Seems like this is a correlation vector, which is useful for diagnosing issues. On the other hand, users might get the impression that we track them and send client identifiers (ms-cv looks like one) to our servers.
Is it possible to turn this behavior off?
B,
Microsoft.OSG.DU.DeliveryOptClient.DownloadStarted
andMicrosoft.OSG.DU.DeliveryOptClient.DownloadCompleted
diagnosticsIt doesn't matter if user chose "optional" or "required" diagnostics in the system settings, these events are sent to Microsoft servers, with a payload like the one below. I understand why this is required for keeping OS services, OS components and OS apps healthy, but I would like to ask if it's possible to opt-out of these diagnostics events.
To Reproduce
Expected behavior The ability to opt-out of the diagnostics and special headers using MSIX / Appintsaller / PackageManager APIs.
The only workaround we have so far is to download the updates manually (from our code) and use
PackageManager.AddPackageByUriAsync
+file:///C:/..../updates/update.msixbundle
. The biggest downside is that we would lose the incremental updates ability.Platform Windows 10 / 11