Azure data factory

Question

Hello,

I have configure a azure data factory with private link(private network) following the doc below using the test connection feature from the linked service I tested the communication and looks fine but when I run my pipeline I am getting the error below.

The test pipeline I have done is getting a file from a storage account to cosmosDB.

https://learn.microsoft.com/en-us/azure/data-factory/tutorial-copy-data-portal-private

Failed to decrypt sub-resource 'None' payload on cloud with error: Failed to decrypt sub-resource payload {
  "properties": {
    "connectVia": {
      "referenceName": "managed-integration-runtime",
      "type": "IntegrationRuntimeReference"
    },
    "type": "AzureBlobStorage",
    "annotations": [],
    "typeProperties": {
      "connectionString": "********************",
      "servicePrincipalId": "********************",
      "servicePrincipalKey": "********************",
      "tenant": "********************",
      "encryptedCredential": "********************"
    }
  },
  "name": "storage_account"
} and error is: Cloud stored credentials cannot be found with retry, please check whether related resource had been deleted before. Value is: {
  "Version": "2017-11-30",
  "ProtectionMode": "Key",
  "SecretContentType": "Plaintext",
  "CredentialId": "DATAFACTORY@*************"
}, type is Plaintext and credentialId is DATAFACTORY@************.., status code: BadRequest.

Answer 1

@Anonymous

Welcome to the MS Q&A platform.

As per the error message "Cloud stored credentials cannot be found with retry, please check whether related resource had been deleted before", there is an issue with the credentials used to access the Azure Blob Storage account. It seems that the sub-resource payload could not be decrypted, and the stored credentials could not be found.

Please check the below.

Check the credentials used to access the Azure Blob Storage account are correct. Make sure that the service principal ID, service principal key, and tenant ID are all correct.

and since you're using a private link, please check the private endpoint is correctly configured and that the necessary network configurations are in place.

I hope this helps.