Error deploying parameterized connections.json

Does this occur consistently? Yes

1. create entry in connections.json

"managedApiConnections": {
    "azurefile": {
        "api": {
            "id": "/subscriptions/@parameters('SubscriptionId')/providers/Microsoft.Web/locations/germanywestcentral/managedApis/azurefile"
        },
        "authentication": {
            "parameter": "@appsetting('BMVSTORAGE_KEY')",
            "scheme": "Key",
            "type": "Raw"
        },
        "connection": {
            "id": "/subscriptions/@parameters('SubscriptionId')/resourceGroups/xxx-stage/providers/Microsoft.Web/connections/azurefile"
        },
        "connectionRuntimeUrl": "https://sss.03.common.logic-germanywestcentral.azure-apihub.net/apim/azurefile/xxx",
        "displayName": "storage1"
    }
  },

Action: azureLogicAppsStandard.deploy Error type: Error Error Message: Error in creating access policy for connection in reference - ‘azurefile’. Error: Error in getting connection - /subscriptions/@parameters(‘SubscriptionId’)/resourceGroups/—/providers/Microsoft.Web/connections/azurefile. Error: The provided subscription identifier ‘@parameters(‘SubscriptionId’)’ is malformed or invalid.

Version: 1.0.12 OS: win32 OS Release: 10.0.22000 Product: Visual Studio Code Product Version: 1.64.2 Language: de

Call Stack

extension.bundle.js:2:4376961extension.bundle.js:2:4376961
rejected extension.bundle.js:2:4372108
processTicksAndRejections task_queues.js:93:5

The same works when editing connections.json in Azure portal.

AB#16678677

[PratikT29]

@sven5 I was facing exactly same issue, referencing subscription and resource group from app settings directly works fine in connections.json

This works fine: “connection”: { “id”: “/subscriptions/@appsetting(‘AzSubscription’)/resourceGroups/@appsetting(‘AzResourceGroup’)/providers/Microsoft.Web/connections/azuredatafactory” },

While referencing subscription as @{appsetting(‘AzSubscription’)} doesn’t work.

[ShreeDivyaMV]

@Sven5, Sorry for the delay in getting back on this. Currently we have an issue with transitive reference of app settings in Parameters. The product group is working on the fix. As of now, the template doesn’t work if,

1. A Param in parameters.json which reads value from app-settings using @appsetting() expression
2. Referring the above param in connections.json file using @parameters()

We would update this thread once it is fixed. Meanwhile please check if the app setting can be directly used in the template for this requirement.