Skip to content

Commit 1a4c346

Browse files
authored
Merge pull request #224492 from kgremban/jan19-duengagement
DU - review of low engagement articles
2 parents 062feba + 5072916 commit 1a4c346

File tree

2 files changed

+20
-22
lines changed

2 files changed

+20
-22
lines changed
Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,31 @@
11
---
2-
title: Data privacy for Device Update for Azure IoT Hub | Microsoft Docs
2+
title: Data privacy for Device Update for Azure IoT Hub
33
description: Understand how Device Update for IoT Hub protects data privacy.
44
author: cjlin
55
ms.author: lichris
6-
ms.date: 09/12/2022
6+
ms.date: 01/19/2023
77
ms.topic: conceptual
88
ms.service: iot-hub-device-update
99
---
1010

1111
# Device Update telemetry collection
1212

13-
Device Update for IoT Hub is a REST API-based cloud service targeted at enterprise customers that enables secure, over-the-air updating of millions of devices via a partitioned Azure service.
13+
In order to maintain the quality and availability of the Device Update service, Microsoft collects certain telemetry from your customer data that may be stored and processed outside of your Azure region. The following list contains the data points that Microsoft collects about the Device Update service:
1414

15-
In order to maintain the quality and availability of the Device Update service, Microsoft collects certain telemetry from your Customer Data which may be stored and processed outside of your Azure region. Below is a list of the data points that Microsoft collects about the Device Update service.
16-
* Device Manufacturer, Model*
17-
* Device Interface Version*
18-
* DU Agent Version, DO Agent Version*
19-
* Update Namespace, Name, Version*
20-
* IoT Hub Device ID
21-
* DU Account ID, Instance ID
15+
* Device manufacturer, model*
16+
* Device Interface version*
17+
* Device Update agent version, Delivery Optimization (DO) agent version*
18+
* Update namespace, name, version*
19+
* IoT Hub device ID
20+
* Device Update account ID, instance ID
2221
* Import ErrorCode, ExtendedErrorCode
2322
* Deployment ResultCode, ExtendedResultCode
2423
* Log collection ResultCode, Extended ResultCode
2524

26-
*For fields marked with asterisk, do not put any personal or sensitive data.
25+
*For fields marked with an asterisk, don't put any personal or sensitive data.
2726

28-
Microsoft maintains no information and has no access to data that would allow correlation of these telemetry data points with an individual’s identity. These system-generated data points are not accessible or exportable by tenant administrators. These data constitute factual actions conducted within the service and diagnostic data related to individual devices.
27+
Microsoft maintains no information and has no access to data that would allow correlation of these telemetry data points with an individual’s identity. These system-generated data points aren't accessible or exportable by tenant administrators. These data constitute factual actions conducted within the service and diagnostic data related to individual devices.
2928

30-
For further information on Microsoft's privacy commitments, please read the "Enterprise and developer products" section of the Microsoft Privacy Statement.
29+
For more information on Microsoft's privacy commitments, see the "Enterprise and developer products" section of the [Microsoft Privacy Statement](https://privacy.microsoft.com/en-us/privacystatement).
30+
31+
For more information about data residency with Device Update, see [Regional mapping for disaster recovery for Device Update](device-update-region-mapping.md).
Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
---
2-
title: Region mapping for BCDR for Device Update for Azure IoT Hub | Microsoft Docs
3-
description: Regional mapping for BCDR for Device Update for IoT Hub.
2+
title: Region failover mapping - Device Update for Azure IoT Hub
3+
description: Regional mapping for business continuity and disaster recovery (BCDR) for Device Update for IoT Hub.
44
author: andrewbrownmsft
55
ms.author: andbrown
66
ms.date: 08/31/2022
77
ms.topic: conceptual
88
ms.service: iot-hub-device-update
99
---
1010

11-
# Regional mapping for BCDR for Device Update for IoT Hub
11+
# Regional failover mapping for Device Update for IoT Hub
1212

13-
In cases where an Azure region is unavailable due to an outage, data contained in the update files submitted to the Device Update for IoT Hub service may be sent to a specific Azure region for the duration of the outage, for the purpose of anti-malware scanning and making the updates available on the Device Update service endpoints.
13+
In cases where an Azure region is unavailable due to an outage, Device Update for IoT Hub supports business continuity and disaster recovery (BCDR) efforts with regional failover pairings. During an outage, data contained in the update files submitted to the Device Update service may be sent to a secondary Azure region. This failover enables Device Update to continue scanning update files for malware and making the updates available on the service endpoints.
1414

1515
## Failover region mapping
1616

@@ -22,16 +22,13 @@ In cases where an Azure region is unavailable due to an outage, data contained i
2222
| Sweden Central | North Europe |
2323
| East US | West US 2 |
2424
| East US 2 | West US 2 |
25-
| West US 2 | East US |
26-
| West US 3 | East US |
25+
| West US 2 | East US |
26+
| West US 3 | East US |
2727
| South Central US | East US |
2828
| East US 2 (EUAP) | West US 2 |
2929
| Australia East | Southeast Asia |
3030
| Southeast Asia | Australia East |
3131

32-
3332
## Next steps
3433

3534
[Learn about importing updates](.\import-update.md)
36-
37-

0 commit comments

Comments
 (0)