Merge pull request #109121 from linda33wj/master

Update ADF default Azure IR region for copy

Author: PRMerger6

articles/data-factory/concepts-integration-runtime.md

@@ -12,7 +12,7 @@ ms.workload: data-services
 
 ms.topic: conceptual
 ms.custom: seo-lt-2019
-ms.date: 03/11/2020
+ms.date: 03/26/2020
 ---
 
 # Integration runtime in Azure Data Factory
@@ -113,9 +113,17 @@ The IR Location defines the location of its back-end compute, and essentially th
 ### Azure IR location
 You can set a certain location of an Azure IR, in which case the data movement or activity dispatch will happen in that specific region. 
 
+>[!TIP]
+>If you have strict data compliance requirements and need ensure that data do not leave a certain geography, you can explicitly create an Azure IR in a certain region and point the Linked Service to this IR using ConnectVia property. For example, if you want to copy data from Blob in UK South to SQL DW in UK South and want to ensure data do not leave UK, create an Azure IR in UK South and link both Linked Services to this IR.
+
 If you choose to use the **auto-resolve Azure IR**, which is the default, 
 
-- For copy activity, ADF will make a best effort to automatically detect your sink and source data store to choose the best location either in the same region if available or the closest one in the same geography, or if not detectable to use the data factory region as alternative.
+- For copy activity, ADF will make a best effort to automatically detect your sink data store's location, then use the IR in either the same region if available or the closest one in the same geography; if the sink data store's region is not detectable, IR in the data factory region as alternative is used.
+
+  For example, you have your factory created in East US, 
+  
+  - When copy data to Azure Blob in West US, if ADF successfully detected that the Blob is in West US, copy activity is executed on IR in West US; if the region detection fails, copy activity is executed on IR in East US.
+  - When copy data to Salesforce of which the region is not detectable, copy activity is executed on IR in East US.
 
 - For Lookup/GetMetadata/Delete activity execution (also known as Pipeline activities), transformation activity dispatching (also known as External activities), and authoring operations (test connection, browse folder list and table list, preview data), ADF will use the IR in the data factory region.
 
@@ -126,9 +134,6 @@ If you choose to use the **auto-resolve Azure IR**, which is the default,
 
 You can monitor which IR location takes effect during activity execution in pipeline activity monitoring view on UI or activity monitoring payload.
 
->[!TIP]
->If you have strict data compliance requirements and need ensure that data do not leave a certain geography, you can explicitly create an Azure IR in a certain region and point the Linked Service to this IR using ConnectVia property. For example, if you want to copy data from Blob in UK South to SQL DW in UK South and want to ensure data do not leave UK, create an Azure IR in UK South and link both Linked Services to this IR.
-
 ### Self-hosted IR location
 The self-hosted IR is logically registered to the Data Factory and the compute used to support its functionalities is provided by you. Therefore there is no explicit location property for self-hosted IR.