Skip to content

Commit 4a016b5

Browse files
committed
Tweak format and wording
1 parent 1b2c3a4 commit 4a016b5

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -123,10 +123,7 @@ The IR Location defines the location of its back-end compute, and essentially th
123123

124124
### Azure IR location
125125

126-
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.
127-
128-
>[!TIP]
129-
>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.
126+
You can set a certain location of an Azure IR, in which case the activity execution or dispatch will happen in that specific region.
130127

131128
If you choose to use the auto-resolve Azure IR, which is the default,
132129

@@ -137,6 +134,9 @@ If you choose to use the auto-resolve Azure IR, which is the default,
137134
- 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.
138135
- When copy data to Salesforce of which the region is not detectable, copy activity is executed on IR in East US.
139136

137+
>[!TIP]
138+
>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.
139+
140140
- 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 uses the IR in the data factory region.
141141

142142
- For Data Flow, ADF uses the IR in the data factory region.

0 commit comments

Comments
 (0)