Error Deploying ADF with Arm Template RRS feed

  • Question

  • Getting error in Azure Data Factory V2.  When using the keyvault in the parameters for a linked service tied to a Self Hosted IR ...  also verified it happens when I just throw in the connection string

    example param with keyvault

    "connectionString": {
      "reference": {
    "keyVault": {
      "id": "/subscriptions/..../resourceGroups/Develop/providers/Microsoft.KeyVault/vaults/vault"
    "secretName": "ConnectionString"


    [{"code":9218,"message":"The data source credential'6077a...1' had been deleted from current Integration Runtime node with payload '' when you delete the link service on Azure Portal, or the task has the wrong payload, please create new link service with your credential again."}]

    Thanx, Adam

    Thursday, May 3, 2018 11:44 PM

All replies

  • Hi Adam,

    This is an example about how to reference a secret stored in key vault.

    Store credential in Azure Key Vault

        "name": "DynamicsLinkedService",
        "properties": {
            "type": "Dynamics",
            "typeProperties": {
                "deploymentType": "<>",
                "organizationName": "<>",
                "authenticationType": "<>",
                "username": "<>",
                "password": {
                    "type": "AzureKeyVaultSecret",
                    "secretName": "<secret name in AKV>",
                        "referenceName": "<Azure Key Vault linked service>",
                        "type": "LinkedServiceReference"
    Hope it helps.

    Friday, May 4, 2018 1:43 AM
  • I can't do that one.   Its an issue with having to assign security principals in the arm templates for the Key Vault which makes it a pain because the principal id is kind of hidden and as I spin up a new ADF I need to add it now and redeploy the keyvault.  Plus ADF opens a get on the the whole key vault's secrets for query by the ADF because there no "group - secret" security.  

    So I was down to passing in the key as a parameter as a build.

    Key vault aside...

    Even if I do normal credentials without a key vault I get the error above where I didn't in the past?  All the other datasources (Azure SQL) are fine, its just the one with the Self-Hosted IR (on Prem) that is now screwed up to where I have to reset the credential every time.

    Thanx, Adam

    Friday, May 4, 2018 3:16 PM