Deploy Azure Standard LogicApp & Its Workflows

Question

Deploy Azure Standard LogicApp & Its Workflows

Anonymous

Hi,

I am trying to deploy a workflow to an Azure Standard LogicApp. I have created the ARM Template for provisioning the LogicApp and then deployed it via Azure DevOps Pipelines. Later I created the CI/CD Pipelines for Workflow Deployment. Most of the Workflow parameters are passed using the APP SETTINGS of LogicApp. Inside the Workflow, we are using a Blob Connection to get data from an external Storage Account. This has been handled using an API Connection. The API Connection to BLOB Storage is getting created with the LogicApp Provisioning ARM Template. We are using the "Access Key Authentication" in the API connection for getting data from BLOB.

Now the problem is, we can see the API Connections under the LogicApp and its showing the status as connected. Here is the screenshot of it.

Screenshot 2023-07-28 at 12.04.45 PM

But every time when the workflow is re-deploying after the changes, the BLOB CONNECTOR in the workflow is crashing with an error. Here is the screenshot of it.

Screenshot 2023-07-28 at 12.04.04 PM

Even we have a valid API Connection in the LogicApp, the Workflow is not using the existing connection, rather it is attempting to create a new one.

Any thoughts on this.

Regard

Accepted answer

1 additional answer

Your answer

Answer 1

navba-MSFT 27,540 Microsoft Employee Moderator

@Anonymous Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

I see that you are encountering the error Unable to initialize operation details for swagger based operationwith your LogicApp workflow.

Could you please try out the old designer link to access your azure Logic App and see if that helps ?

Link to Old designer is here https://aka.ms/lafallback . Once you click on this link, Navigate to the concerned LogicApp workflow designer and then see if the same issue.

Hope this helps.

**
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Anonymous

2023-07-31T03:57:52.9733333+00:00

@navba-MSFT Is there any update on the above one. Will be a great help if you can look into this.

Answer 2

Anonymous

Many Thanks for this.

Now I am getting a different error.

Please find the code view of connector.

Screenshot 2023-07-28 at 1.29.36 PM

Here is the new error I am getting.

Screenshot 2023-07-28 at 1.30.38 PM

I have already shared the screenshot of API connection in the original question. Not sure why its failing.

navba-MSFT 27,540 Reputation points Microsoft Employee Moderator

2023-07-31T04:23:32.0166667+00:00
@Anonymous Based on the information provided, it seems that the LogicApp is unable to use the existing API connection to Blob Storage, and instead, it is attempting to create a new one, resulting in a "connector not found" error. You can try the following steps and check if that helps:

I understand that API connection status is successful and says Connected. But still try adding the connection again, just to make sure.

Check if the API connection is correctly referenced in the workflow. You can verify this by navigating to the LogicApp Designer and selecting the "Code View" option from the top menu. Look for the "connections" section in the JSON code and ensure that the API connection to Blob Storage is correctly referenced.

Check if the API connection is correctly provisioned in the ARM template. You can verify this by reviewing the ARM template used to provision the LogicApp and ensuring that the API connection to Blob Storage is correctly defined. You can refer to the Azure documentation on creating API connections as needed for more information on how to define API connections in ARM templates.

Check if the API connection is correctly authenticated. You mentioned that you are using "Access Key Authentication" to authenticate the API connection to Blob Storage. Ensure that the access key is correctly configured and has the necessary permissions to access the Blob Storage account.

If the issue persists, you can try recreating the API connection to Blob Storage and updating the LogicApp workflow to use the new connection. You can also refer to the Azure documentation on custom connectors to create a custom connector for Blob Storage if needed. Also refer to the Standard logicApp workflow limitations here.

Hope this helps.

Sharing another issue link here for "connector not found error": https://learn.microsoft.com/en-us/answers/questions/774695/workflow-was-running-fine-now-i-get-connector-not?page=1&orderby=newest
Anonymous

2023-07-31T15:41:35.5633333+00:00

@navba-MSFT Thanks for the detailed note. I will look into that. Also there is one more thing I would like to Ask you. I am deploying the Logicapp using ARM template and I am trying to use an existing app insights with this logicapp and I have the app insights Instrumentkey and Connection String Passed under the app settings of Logicapp. But still when I go to Application Insights in Logicapp, its asking me to "Turn On Application Insights". What is the issue with that.
Anonymous

2023-07-31T15:44:46.43+00:00

@navba-MSFT Thanks for the detailed note. Let me follow this. There is one more thing I wanted to ask you.

I am deploying this logicapp using ARM template. For the Application Insights I am trying to use an existing one which I am passing "Instrumentation Key" and "Connection String" as App Settings while the time of provisioning the LogicApp. But even then when I go to "Application Insights" in LogicApp, its asking me to "Turn On Application Insights" Button. I am not getting what I am doing wrong. Can you help me with this.
Anonymous

2023-08-01T05:09:26.8933333+00:00

@navba-MSFT can you please review the above one as well. Thankyou

navba-MSFT 27,540 Microsoft Employee Moderator

@Anonymous Thanks for getting back. Ensure that you have the added within your parameters as shown below:

 "parameters": {
        "logicAppName": {
            "type": "string",
            "metadata": {
                "description": "The name of the Logic App to create."
            }
        },
        "appInsightsInstrumentationKey": {
            "type": "securestring",
            "metadata": {
                "description": "The instrumentation key of the existing Application Insights resource."
            }
        }
    }

Within the resources section ensure that you use this paramater:

 "resources": [
{
    "type": "Microsoft.Logic/workflows",
    "apiVersion": "2017-07-01",
    "name": "[parameters('logicAppName')]",
    "location": "[resourceGroup().location]",
    "properties": "[variables('logicAppDefinition').properties]",
    "dependsOn": [],
    "tags": {}
},
{
    "type": "Microsoft.Insights/components/workflows",
    "apiVersion": "2015-05-01",
    "name": "[concat(parameters('logicAppName'), '-insights')]",
    "location": "[resourceGroup().location]",
    "properties": {
        "ApplicationId": "[parameters('appInsightsInstrumentationKey')]"
    },
    "dependsOn": [
        "[resourceId('Microsoft.Logic/workflows', parameters('logicAppName'))]"
    ],
    ```

Share via

Deploy Azure Standard LogicApp & Its Workflows

1 additional answer

Your answer