Azure Blob Storage Linked service fails while deployment to Production from develpoment

Question

I have a Azure Storage linked Service which breaks if any artifact is promoted from dev to production . The authentication tab gets reset to Account key and the details of the sas uri and sas creds are wiped off .

The idea is that i am creating a generic linked service which takes in the params of sas uri and sas token .

Code as below :

{
"name": "AzureBlobStorageLinkedService",
"properties": {
"type": "AzureBlobStorage",
"parameters": {
"blobsasurl": {
"type": "string"
},
"blobsastoken": {
"type": "string"
}
},
"typeProperties": {
"sasUri": {
"type": "Expression",
"value": "@linkedService().blobsasurl"
},
"sasToken": {
"type": "AzureKeyVaultSecret",
"store": {
"referenceName": "XXXXXXXXXX",
"type": "LinkedServiceReference"
},
"secretName": {
"value": "@linkedService().blobsastoken",
"type": "Expression"
}
}
}
}
}

Something as below :

Answer 1

While using the ARM template and Azure DevOps method to deploy ADF, consider below points

1) Are you uploading the ARM_Template_parameters.json file and does it have the Storage Account details as parameters

2) Have you created Variable Group in Azure DevOps

3) Are you over-riding the value present in parameter file with the parameters in Variable Group?

https://learn.microsoft.com/en-us/azure/data-factory/continuous-integration-delivery-automate-azure-pipelines

Answer 2

@Sumarigo-MSFT can you please help me here please ?

Answer 3

The issue stands solved now . Overriding the parameters the correct way did the job,