Skip to content

Commit 06e3a5a

Browse files
authored
Merge pull request #178359 from MartinJaffer-MSFT/patch-30
Update apache-spark-secure-credentials-with-tokenlibrary.md
2 parents 516fc7c + b73641f commit 06e3a5a

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/synapse-analytics/spark/apache-spark-secure-credentials-with-tokenlibrary.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,8 @@ Accessing data from external sources is a common pattern. Unless the external da
1919

2020
Synapse uses Azure Active Directory (AAD) passthrough by default for authentication between resources. If you need to connect to a resource using other credentials, use the TokenLibrary directly. The TokenLibrary simplifies the process of retrieving SAS tokens, AAD tokens, connection strings, and secrets stored in a linked service or from an Azure Key Vault.
2121

22+
AAD passthrough uses permissions assigned to you as a user in AAD, rather than permissions assigned to Synapse or a separate service principal. For example, if you want to use AAD passthrough to access a blob in a storage account, then you should go to that storage account and assign blob contributor role to yourself.
23+
2224
When retrieving secrets from Azure Key Vault, we recommend creating a linked service to your Azure Key Vault. Ensure that the Synapse workspace managed service identity (MSI) has Secret Get privileges on your Azure Key Vault. Synapse will authenticate to Azure Key Vault using the Synapse workspace managed service identity. If you connect directly to Azure Key Vault without a linked service, you will authenticate using your user Azure Active Directory credential.
2325

2426
For more information, see [linked services](../../data-factory/concepts-linked-services.md?context=/azure/synapse-analytics/context/context).

0 commit comments

Comments
 (0)