CodexBloom - Programming Q&A Platform

Azure Data Factory Pipeline scenarios with 'Invalid Resource ID' scenarios When Using Linked Services

πŸ‘€ Views: 243 πŸ’¬ Answers: 1 πŸ“… Created: 2025-07-15
azure data-factory blob-storage sql-database json

I'm upgrading from an older version and After trying multiple solutions online, I still can't figure this out..... I'm currently working on an Azure Data Factory pipeline that involves copying data from an Azure Blob Storage to an Azure SQL Database. However, during testing, I'm working with an behavior: `Invalid Resource ID` when the pipeline attempts to connect to the linked services. I've double-checked the connection strings and the authentication settings, but everything seems correct. Here’s a snippet of how I configured my linked services: ```json { "name": "AzureBlobStorage", "type": "AzureBlobStorage", "typeProperties": { "connectionString": "DefaultEndpointsProtocol=https;AccountName=myAccount;AccountKey=myKey;EndpointSuffix=core.windows.net" } } ``` And for the SQL Database linked service: ```json { "name": "AzureSqlDatabase", "type": "AzureSqlDatabase", "typeProperties": { "connectionString": "Server=tcp:myserver.database.windows.net,1433;Database=mydatabase;User ID=myuser@myserver;Password=mypassword;Encrypt=True;" } } ``` I am using Azure Data Factory V2 and I have also ensured that the firewall settings on the SQL Database allow connections from the Data Factory. I've tried recreating the linked services multiple times, checking for typos in the resource IDs, and even adjusting the authentication method from SQL authentication to Managed Identity, but I still face the same scenario. The behavior occurs right at the activity that references the Azure SQL Database linked service. Any insights on what could be causing this behavior or how I can debug this scenario further would be greatly appreciated. What's the best practice here? This is for a application running on Ubuntu 20.04.