Skip to content

Commit 710c6aa

Browse files
Minor correction for clarity
1 parent dce9811 commit 710c6aa

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/synapse-analytics/sql/tutorial-external-tables-using-managed-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ To enable your managed identity to access data on ADLS Gen2 accounts, you need t
4040
Your workspace identity is now a member of the Storage Blob Data Contributor role and has access to the source folder.
4141

4242
> [!NOTE]
43-
> These steps also apply to secure ADLS Gen2 accounts that are configured to restrict public access. If your storage account is associated with a secured ADLS Gen2 account or associated with a VNet, you must authenticate using a managed identity. To learn more about securing your ADLS Gen2 account, see [Configure Azure Storage firewalls and virtual networks](/azure/storage/common/storage-network-security).
43+
> These steps also apply to secure ADLS Gen2 accounts that are configured to restrict public access. If your storage account is associated with a secured ADLS Gen2 account or associated with a VNet, the external table or COPY INTO command must use a managed identity. To learn more about securing your ADLS Gen2 account, see [Configure Azure Storage firewalls and virtual networks](/azure/storage/common/storage-network-security).
4444
4545
## Ingest data using COPY INTO
4646

0 commit comments

Comments
 (0)