Skip to content

Commit 069af97

Browse files
Merge pull request #226615 from lrtoyou1223/shirbranch22
Add a note about on-prem to on-prem scenario
2 parents 84296ec + 25da7b2 commit 069af97

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/data-factory/create-self-hosted-integration-runtime.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -454,6 +454,8 @@ For example, to copy from an on-premises data store to a SQL Database sink or an
454454
> [!NOTE]
455455
> If your firewall doesn't allow outbound port 1433, the self-hosted integration runtime can't access the SQL database directly. In this case, you can use a [staged copy](copy-activity-performance.md) to SQL Database and Azure Synapse Analytics. In this scenario, you require only HTTPS (port 443) for the data movement.
456456
457+
If all your data source and sink and self-hosted integration runtime are in on-premises environment, then the copied data will not go to cloud but strictly remain within on-premises.
458+
457459
## Credentials store
458460
There are two ways to store the credentials when using self-hosted integration runtime:
459461
1. Use Azure Key Vault.

0 commit comments

Comments
 (0)