Skip to content

Commit 904d2f2

Browse files
authored
updated TLS version
1 parent 4d65994 commit 904d2f2

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,11 +51,14 @@ In this article, we review security considerations in the following two data mov
5151
- **Store credentials in Azure Key Vault**. You can also store the data store's credential in [Azure Key Vault](https://azure.microsoft.com/services/key-vault/). Data Factory retrieves the credential during the execution of an activity. For more information, see [Store credential in Azure Key Vault](store-credentials-in-key-vault.md).
5252

5353
### Data encryption in transit
54-
If the cloud data store supports HTTPS or TLS, all data transfers between data movement services in Data Factory and a cloud data store are via secure channel HTTPS or TLS.
54+
If the cloud data store supports HTTPS or TLS, all data transfers between data movement services in Data Factory and a cloud data store are via secure channel HTTPS or TLS .
5555

5656
> [!NOTE]
5757
> All connections to Azure SQL Database and Azure SQL Data Warehouse require encryption (SSL/TLS) while data is in transit to and from the database. When you're authoring a pipeline by using JSON, add the encryption property and set it to **true** in the connection string. For Azure Storage, you can use **HTTPS** in the connection string.
5858
59+
> [!NOTE]
60+
> TLS version used is 1.2.
61+
5962
### Data encryption at rest
6063
Some data stores support encryption of data at rest. We recommend that you enable the data encryption mechanism for those data stores.
6164

0 commit comments

Comments
 (0)