Azure-docs: Create a Resource Manager template for each environment- Fill in the values step details on connection strings are not clear

[saulcruz]

In this section https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment#create-a-resource-manager-template-for-each-environment

when trying to fill in the "Custom Deployment Settings" values I'm unable to identify the format of a connection string, for example what if I access a SQL server database on-prem using a windows authentication service account and a password, I know how to do this in ADF itself but unable to get the right format in these settings, same question for the other data source types.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 1e22e4d6-366f-fbf8-e141-8905ca7ab7ae
• Version Independent ID: 5be2acf2-66e7-cadf-6666-5a85a65b9771
• Content: Continuous integration and deployment in Azure Data Factory
• Content Source: articles/data-factory/continuous-integration-deployment.md
• Service: data-factory
• GitHub Login: @douglaslMS
• Microsoft Alias: douglasl

[jason-j-MSFT]

@saulcruz
Thanks for the feedback! We are currently investigating and will update you shortly.

[douglaslMS]

@saulcruz For the properties of a SQL Server linked service, see Copy data to and from SQL Server using Azure Data Factory | Linked service properties. Connection strings for other linked services are documented in separate pages for each service.

The easiest way to verify the correct connection string for a linked service is to

1. Create the linked service in the Data Factory UI,
2. export the linked service as a Resource Manager template, and
3. check the connection string in the template.

I'll be adding a notation to the article with this suggestion.

[saulcruz]

Douglas, the link provided helped me to figure out the notation. I was actually trying to get the connection string from the steps that you mentioned, however the connection strings are not generated in the same format.

all I needed was this:

Data Source=<servername>\\<instance name if using named instance>;Initial Catalog=<databasename>;Integrated Security=False;User ID=<username>;Password=<password>;

Much appreciated

[douglaslMS]

@saulcruz Thanks for the info. This is not something that I've experimented with personally. Are you saying that if you create the linked service in the UI and generate an ARM template for it, that the connection string doesn't work? Or simply that the format isn't identical?

[saulcruz]

correct, the format isn't identical, it looks like this:

 {
            "name": "[concat(parameters('factoryName'), '/ls_sql_dev_MyName')]",
            "type": "Microsoft.DataFactory/factories/linkedServices",
            "apiVersion": "2018-06-01",
            "properties": {
                "annotations": [],
                "type": "SqlServer",
                "typeProperties": {
                    "connectionString": "[parameters('ls_sql_dev_MyName_connectionString')]",
                    "userName": "[parameters('ls_sql_dev_MyName_properties_typeProperties_userName')]",
                    "password": {
                        "type": "SecureString",
                        "value": "[parameters('ls_sql_dev_MyName_password')]"
                    }
                },
                "connectVia": {
                    "referenceName": "iriisvm",
                    "type": "IntegrationRuntimeReference"
                }
            },
            "dependsOn": [
                "[concat(variables('factoryId'), '/integrationRuntimes/iriisvm')]"
            ]
        }

[douglaslMS]

@saulcruz Uh ... I see. Let me ask for clarification about the advice that was passed on to me.

[douglaslMS]

@saulcruz Apparently I received out-of-date advice, and - as is obvious in your example - the exported ARM template is now parameterized as much as possible. One alternative way to check the connection string in the UI is by opening the code view for the resource. In this view, however, the password or account key portion of the connection string is removed.

[saulcruz]

Correct, I understand why this is parameterized as much as possible, thanks a lot though for taking the time to look this up, your link really solved my problem @douglaslMS

[douglaslMS]

@saulcruz Thanks to your question, we have added a bit of guidance to the article. Please see the paragraph titled "Connection strings" at the end of the section. Continuous integration and deployment in Azure Data Factory | Create a Resource Manager template for each environment. We're now going to close this issue.

[douglaslMS]

please-close