Skip to content

Commit 315d8c0

Browse files
Merge pull request #212882 from jonburchel/pr98242
Pr98242
2 parents 7766e0e + 30400d0 commit 315d8c0

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/data-factory/transform-data-using-custom-activity.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -129,6 +129,9 @@ The following table describes names and descriptions of properties that are spec
129129
> [!NOTE]
130130
> If you are passing linked services as referenceObjects in Custom Activity, it is a good security practice to pass an Azure Key Vault enabled linked service (since it does not contain any secure strings) and fetch the credentials using secret name directly from Key Vault from the code. You can find an example [here](https://github.com/nabhishek/customactivity_sample/tree/linkedservice) that references AKV enabled linked service, retrieves the credentials from Key Vault, and then accesses the storage in the code.
131131
132+
> [!NOTE]
133+
> Currently only Azure Blob storage is supported for resourceLinkedService in custom activity, and it is the only linked service that gets created by default and no option to choose other connectors like ADLS Gen2.
134+
132135
## Custom activity permissions
133136

134137
The custom activity sets the Azure Batch auto-user account to *Non-admin access with task scope* (the default auto-user specification). You can't change the permission level of the auto-user account. For more info, see [Run tasks under user accounts in Batch | Auto-user accounts](../batch/batch-user-accounts.md#auto-user-accounts).

0 commit comments

Comments
 (0)