Merge pull request #278297 from andrewbrownmsft/docs-editor/device-update-region-mapping-1718382301

Update device-update-region-mapping.md

Author: v-dirichards

articles/iot-hub-device-update/device-update-region-mapping.md

@@ -8,26 +8,37 @@ ms.topic: conceptual
 ms.service: iot-hub-device-update
 ---
 
-# Regional failover mapping for Device Update for IoT Hub
-
-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.
-
-## Failover region mapping
-
-| Region name |  Fails over to
-| --- | --- |
-| North Europe | West Europe |
-| West Europe | North Europe |
-| UK South | North Europe |
-| Sweden Central | North Europe |
-| East US | West US 2 |
-| East US 2 | West US 2 |
-| West US 2 | East US |
-| West US 3 | East US |
-| South Central US | East US |
-| East US 2 (EUAP) | West US 2 |
-| Australia East | Southeast Asia |
-| Southeast Asia | Australia East |
+# Device Update for IoT Hub regional mapping for scan and failover 
+
+When you're importing an update into the Device Update for IoT Hub service, that update content may be processed within different Azure regions. The region used for processing depends on the region that your Device Update Instance was created in.
+
+## Anti-malware scan
+
+When you're using the Azure portal for importing your update, there's now an option to enable anti-malware scan. If you select the option to enable anti-malware scan, your update is sent to the Azure region that corresponds to the "Default scan region" 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 is processed in the same region as your Device Update Instance, but it isn't scanned for malware. **Optional anti-malware scan is in Public Preview**.
+
+If you're using the Azure CLI or directly calling Device Update APIs, your update isn't scanned for malware during the import process. It's processed in the same region as your Device Update Instance.
+
+## Failover and BCDR
+
+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.
+
+## Region mapping for default and failover cases
+
+
+| Device Update Instance region|Default scan region|Failover scan region |
+| -------- | -------- | -------- |
+| North Europe | North Europe   | Sweden Central  |
+|West Europe   | North Europe | Sweden Central  |
+| UK South| North Europe   | Sweden Central |
+|Sweden Central|Sweden Central| North Europe  |
+|East US| East US   |East US 2 |
+|East US 2| East US 2  |East US  |
+|West US 2|West US 2| East US 2   |
+|West US 3| West US 2| East US 2  |
+|South Central US|West US 2| East US 2 |
+|East US 2 (EUAP)|East US 2| East US|
+|Australia East|North Europe| Sweden Central|
+|Southeast Asia | West US 2| East US 2  |
 
 ## Next steps