This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 12%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
I am trying to deploy my ADF templates from dev to test. Since the size of the ARMTemplateForFactory.json got increased to more than 4MB due to recent changes in the data factory, we decided to use the linkedTemplates for deployment.
So I created an additional step in the pipeline for copying the linkedTemplates to the storage account and set the containerUri and containerSasToken parameters. However the Azure Resource Group Deployment step with Create or Update Resource Group as the Action fails with the following error :
InvalidContentLink: Unable to download deployment content from 'https://abc.blob.core.windows.net/adf-arm-templates/ArmTemplate_0.json?***Sanitized Azure Storage Account Shared Access Signature***'. The tracking Id is 'some_id'. Please see https://aka.ms/arm-deploy for usage details.
I verified that the agent I am using for deployment and the storage account are under same VNet. Also I generated SAS token from both at container level and from the storage account level too. But still I am getting the same error.
The pipeline steps :
@Luis Rodriguez @AnnuKumari-MSFT @KranthiPakala-MSFT Hello , can you please help me with the above issue?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 70%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
Hello and welcome to Microsoft Q&A @Aayush Suresh Jain
As I understand, the ask is for help in resolving the InvalidContentLink error during ARM deployment.
Unfortunately, this error does not highlight the exact cause (404 not found vs unauthorized or other specifics). The troubleshooting guide says:
InvalidContentLink
You've most likely attempted to link to a nested template that isn't available. Double check the URI you provided for the nested template. If the template exists in a storage account, make sure the URI is accessible. You might need to pass a SAS token. Currently, you can't link to a template that is in a storage account behind an Azure Storage firewall. Consider moving your template to another repository, like GitHub.
I believe the order of things in the process of getting the file is:
We can eliminate #3 by adding a step before Azure resource group deployment. Something to simple try reading the file.
Invalid link is different from invalid permissions. I don't think #2, #4 or #5 is the issue.
@MartinJaffer-MSFT The storage account URI is accessible I have verified that. I have also tried using a storage account without any firewall restrictions and I am still getting the same error. Also, can you help me with the documentation of using repository( Azure repos) to store the templates there and access it.
@MartinJaffer-MSFT Hi, I have regenerated the SAS token for the storage account without firewall rules and it is working now for me. Although the old SAS token have not expired yet and have the same permissions to that of new one. I am testing it now and will see if everything gets deployed correctly.
@Aayush Suresh Jain so the problem was a bad SAS token? and it works now?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 73%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGS%3C/text%3E%3C/svg%3E)
hi ayush, how you were able to generate sas token without the firewall restriction as i am also facing the same issue.
i am also facing the same issue as the same sas tokens are used before to put the template in blob storage then why the same sas tokens throws an error when downloading the data from blob storage
Hi @Gupta3, Satyam , when you create your SAS token, did you grant appropriate permissions? Also, for me - I had to give my Service Connection Azure Blob Data Contributor role for this issue and it worked for me.
Hi @Gupta3, Satyam While creating the SAS token, did you set the appropriate permissions? Also, you'll need to give the Azure DevOps service connection Storage Blob Data Contributor role.