Skip to content

Commit 1d81b80

Browse files
committed
Added one more Note
1 parent ebe1c19 commit 1d81b80

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/data-factory/data-movement-security-considerations.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -153,6 +153,9 @@ The following images show the use of self-hosted integration runtime for moving
153153
> [!NOTE]
154154
> For details about data access strategies through Azure Data Factory, see [this article](https://docs.microsoft.com/azure/data-factory/data-access-strategies#data-access-strategies-through-azure-data-factory).
155155
156+
> [!NOTE]
157+
> You might have to manage ports or set up allow list for domains at the corporate firewall level as required by the respective data sources. This table only uses Azure SQL Database, Azure SQL Data Warehouse, and Azure Data Lake Store as examples.
158+
156159
#### Firewall requirements for on-premises/private network
157160
In an enterprise, a corporate firewall runs on the central router of the organization. Windows Firewall runs as a daemon on the local machine in which the self-hosted integration runtime is installed.
158161

0 commit comments

Comments
 (0)