Azure API Connections have a name and a display name. When you create a new API Connection via the Azure Portal, you are not able to specify the name of the API Connection. This name is actually used in Logic Apps however. Example: @parameters(‘$connections’)[‘sftp_1’][‘connectionId’] In this case sftp_1 is the name, not the display name.…
My colleague Eldert Grootenboer has written an excellent series of blog posts on deploying Azure API Management via Visual Studio Team Services (VSTS). This is a short summary. API Management can be deployed in three steps. Create API Management instance via ARM deployment. Create users, groups and products via ARM deployment. Create virtual service that you…
I received the following error when deploying a Logic App via Powershell/ARM: InvalidTemplate. Unable to process template language expressions in action ‘HTTP’ inputs at line ‘1’ and column ‘1420’: ‘The workflow parameter ‘ahakStorageConnectorName’ is not found.’. At the top of the Logic App Json file, I defined the parameters. The parameter values were contained in…
To deploy a logic app via Powershell, I used the following approach; Create a directory structure with two folders, i.e.: C:\Sources\PBaars\Deployment\Release1.5\AAA-DeployResources C:\Sources\PBaars\Deployment\Release1.5\ProcessPlanning Folder AAA-DeployResources contains reusable artefacts like a parameter file and a Powershell module with reusable code. In this case the reusable code uploads files for a Web App or API App to a…
If you deploy a logic app from Visual Studio, you may run into problems. In this specific case I entered a WDL expression as the body of a Http Action: @{decodeBase64(actionBody(‘GetDocument’)._buffer)} After deploying the Logic App from Visual Studio, I looked at the Logic App in the Azure Portal. The code view looked OK, but…