You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-hub-device-update/device-update-region-mapping.md
+21-20Lines changed: 21 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,30 +14,31 @@ When importing an update into the Device Update for IoT Hub service, that update
14
14
15
15
## Anti-malware scan
16
16
17
-
If you are using the Azure portal for importing your update, you will see an option to enable anti-malware scan. If you select the option to enable anti-malware scan, your update will be sent to the Azure region that corresponds to the "Normal" column table in the **Region mapping for normal and failover cases** section. If you don't select the option to enable anti-malware scan, your update will be processed in the same region as your Device Update Instance, but it won't be scanned for malware. **Optional anti-malware scan is in Public Preview**.
17
+
If you are using the Azure portal for importing your update, you will see an option to enable anti-malware scan. If you select the option to enable anti-malware scan, your update will be sent to the Azure region that corresponds to the "Default" column table in the **Region mapping for default and failover cases** section. If you don't select the option to enable anti-malware scan, your update will be processed in the same region as your Device Update Instance, but it won't be scanned for malware. **Optional anti-malware scan is in Public Preview**.
18
18
19
-
If you are using the Azure CLI or directly calling APIs, your update will not be scanned for malware during the import process and will be processed in the same region as your Device Update Instance. The optional scan functionality will be added to the Azure CLI and exposed via API in a future release.
19
+
If you are using the Azure CLI or directly calling Device Update APIs, your update won't be scanned for malware during the import process. It will be processed in the same region as your Device Update Instance. The optional scan functionality will be added to the Azure CLI and exposed via API in a future release.
20
20
21
21
## Failover and BCDR
22
22
23
-
As an exception to the previous section, 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 for processing. This failover enables Device Update to continue scanning update files for malware if you select that option. This will occur whether you select the option to enable anti-malware scan or not.
24
-
25
-
## Region mapping for normal and failover cases
26
-
27
-
| Region name | Fails over to
28
-
| --- | --- |
29
-
| North Europe | West Europe |
30
-
| West Europe | North Europe |
31
-
| UK South | North Europe |
32
-
| Sweden Central | North Europe |
33
-
| East US | West US 2 |
34
-
| East US 2 | West US 2 |
35
-
| West US 2 | East US |
36
-
| West US 3 | East US |
37
-
| South Central US | East US |
38
-
| East US 2 (EUAP) | West US 2 |
39
-
| Australia East | Southeast Asia |
40
-
| Southeast Asia | Australia East |
23
+
As an exception to the previous section, 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 for processing. This failover enables Device Update to continue scanning update files for malware if you select that option.
24
+
25
+
## Region mapping for default and failover cases
26
+
27
+
28
+
| Device Update Instance region|Default scan region|Failover scan region |
0 commit comments