Linked service authentication options for SQL Server are different amongst ADF within same subscription

Question

In the same Azure subscription, I have several resource groups and each has data factories, however, the linked service authentication options are not the same among them, why?

Here is an example:
ADF1: SQL SERVER Linked service authentication options:

And then I have the "Inline" option

But in ADF2, I only have these options:

And no "Inline" option.

What can I do to set these configurations inline, so I can have a secret with the connection string with all necessary properties?

Answer 1

@Gonçalo J P Carvalho

Thanks for reaching out to Microsoft Q&A.

The difference in linked service authentication options between your two data factories (ADF1 and ADF2) is likely due to the following:

• Azure Data Factory Version: Different versions of Azure Data Factory might have varying sets of features and authentication options. If ADF1 is on an older version, it might have the "Inline" option that's no longer available in newer versions (like the one used by ADF2).
• Azure SQL Server Version: The version of SQL Server database you're connecting to can also influence the available authentication methods in the linked service. Newer SQL Server versions might have updated security features or authentication protocols that aren't supported by older Azure Data Factory versions.

  consider checking the below steps and confirm us.

Check ADF Version:

Go to the Azure portal and navigate to your data factories (ADF1 and ADF2).

In the overview page for each data factory, check the "Version" under the "Essentials" section. If the versions differ significantly, consider upgrading ADF2 to a newer version that supports the "Inline" option.

Check SQL Server Version:

Ensure that the SQL Server database you're connecting to in both ADF1 and ADF2 is a compatible version. Check the SQL Server documentation for supported authentication methods based on the specific version.

Review Configuration Settings: Examine the configuration settings of both ADFs to ensure they are set up similarly. This includes checking for any differences in the JSON definitions of the linked services

Check Regional Features: Sometimes, certain features are rolled out to different regions at different times. Verify if the “Inline” option is available in the region where ADF2 is deployed.

Consider a Different Approach:

If upgrading isn't feasible, you can consider an alternative approach to managing your connection string secrets:

Azure Key Vault: Store your connection string in Azure Key Vault and access it securely through a managed identity or service principal. This is a more robust and secure way to manage sensitive data.Tsitive data.

Review the official Microsoft documentation for any recent updates or changes in the linked service authentication options that might affect your ADF configurations.

please do let us know after these checks if the issue persists.