From ed93015af68a79b1d15de829531f3283c6d7363a Mon Sep 17 00:00:00 2001 From: Marc Shepard <37675325+marcshep-msft@users.noreply.github.com> Date: Wed, 18 Apr 2018 10:17:06 -0700 Subject: [PATCH 1/2] Update configure-windows-diagnostic-data-in-your-organization.md Added info about data volumes --- .../configure-windows-diagnostic-data-in-your-organization.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/configuration/configure-windows-diagnostic-data-in-your-organization.md b/windows/configuration/configure-windows-diagnostic-data-in-your-organization.md index ce9e5b4792..47c21fdc8b 100644 --- a/windows/configuration/configure-windows-diagnostic-data-in-your-organization.md +++ b/windows/configuration/configure-windows-diagnostic-data-in-your-organization.md @@ -139,6 +139,9 @@ Info collected at the Enhanced and Full levels of diagnostic data is typically g All diagnostic data data is encrypted using SSL and uses certificate pinning during transfer from the device to the Microsoft Data Management Service. With Windows 10, data is uploaded on a schedule that is sensitive to event priority, battery use, and network cost. Real-time events, such as Windows Defender Advanced Threat Protection, are always sent immediately. Normal events are not uploaded on metered networks, unless you are on a metered server connection. On a free network, normal events can be uploaded every 4 hours if on battery, or every 15 minutes if on A/C power. Diagnostic and crash data are only uploaded on A/C power and free networks. +At basic and enhanced telemetry levels, the amount transmitted is quite small; less than 1mb/device/day on most days (and occasionally up to 2mb/device/day). + + ### Endpoints The Microsoft Data Management Service routes data back to our secure cloud storage. Only Microsoft personnel with a valid business justification are permitted access. From e9c241e16c31127d6d48b837d10e0d68b9ae48d3 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 18 Apr 2018 16:53:33 -0700 Subject: [PATCH 2/2] Update configure-windows-diagnostic-data-in-your-organization.md --- .../configure-windows-diagnostic-data-in-your-organization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/configuration/configure-windows-diagnostic-data-in-your-organization.md b/windows/configuration/configure-windows-diagnostic-data-in-your-organization.md index 47c21fdc8b..dab1a8d1a9 100644 --- a/windows/configuration/configure-windows-diagnostic-data-in-your-organization.md +++ b/windows/configuration/configure-windows-diagnostic-data-in-your-organization.md @@ -139,7 +139,7 @@ Info collected at the Enhanced and Full levels of diagnostic data is typically g All diagnostic data data is encrypted using SSL and uses certificate pinning during transfer from the device to the Microsoft Data Management Service. With Windows 10, data is uploaded on a schedule that is sensitive to event priority, battery use, and network cost. Real-time events, such as Windows Defender Advanced Threat Protection, are always sent immediately. Normal events are not uploaded on metered networks, unless you are on a metered server connection. On a free network, normal events can be uploaded every 4 hours if on battery, or every 15 minutes if on A/C power. Diagnostic and crash data are only uploaded on A/C power and free networks. -At basic and enhanced telemetry levels, the amount transmitted is quite small; less than 1mb/device/day on most days (and occasionally up to 2mb/device/day). +The data transmitted at the Basic and Enhanced data diagnostic levels is quite small; typically less than 1 MB per device per day, but occasionally up to 2 MB per device per day). ### Endpoints