Can I use AI to create and deploy an Azure Logic Apps with Business Central connector?

Today I’ve decided to do with AI a test that I’ve never done before: creating an Azure Logic App workflow that uses a connector, more specifically the Business Central connector.

Requirements for the challenge:

• Login to my Azure subscription
• Deploying all the needed Azure resources
• Creating the Azure Logic App workflow, with trigger and actions.

All the steps must be performed with AI without any corrections by me (II put a blindfold on myself and accepted everything that AI proposes to do in an ignorant way).

DISCLAIMER: never do that in the real-world! Always ask AI to maintain you in the loop and to create comprehensive implementation plan before writing a single line of code.

The prompt:

The prompt was an easy text-based prompt (ignorant way as per initial conditions), with the requirements as follows:

Log in to Azure, promopt me to select the subscription and on the selected subscrption create a new resource group called “testaigenerationrg” in the West Europe region.
Then create a new Consumption-based Logic App named “la-testaigeneration” in the previously created resource group.
When created, add an HTTP Request trigger accepting a POST request with the following JSON body:
{
“test”: true
}

Then add the Business Central Connector with the “Find Records” action.
Then add an HTTP response and for the Response Body in the HTTP Response, set the input from the HTTP Request.
Save the Logic App.

Let’s see AI at work…

Here is the first problem discovered by the AI: to create a Logic App workflow, also a storage account is needed:

Et voilà. Storage Account created. Let’s go…

second problem detected: to create a Logic App, you also need an App Service plan. The AI is not able to immediately create the app service plan (syntax not well known) but it’s able to autonomously call the help and discover the right syntax:

And here is where the AI had another problem. It selected the Free SKU (F1) for the app service plan but Logic Apps in this SKU are not supported. The AI then deleted the previosuly created app service plan and created a new one correctly:

Let’s go…

Wonderful! I have now my Azure Logic App instance created in the Azure Portal.

Now the AI needs to create and deploy the workflow definition… and here is where the problem starts and where the AI started to sweat

Work finished! The Logic Apps workflow is now deployed.

This is what I can see from the Azure Portal, in the Logic Apps designer:

The workflow’s trigger is the “When an HTTP request is received” trigger, with the correct JSON body as per requirements:

The HTTP Response action has the body of the HTTP Request as output, exactly as per requirements:

The problem is the workflow’s action with the Business Central connector as reference. The AI has not correctly added the connector’s reference in the workflow definition:

As you can see from the AI-generated workflow definition, the Business Central connector was added as an ApiConnection but with wrong parameters:

Correct parameters are the following:

Final verdict?

AI did a decent job on deploying the needed Azure resources, but when you need to deploy Logic Apps workflow referencing external connectors (like the Business Central connector) it usually fails. Probably with a better prompt explaining the needed parameters to reference the Business Central connector in a Logic App workflow’s definition file it can do the job, but this was outside the scope of this test.

Original Post https://demiliani.com/2025/08/19/can-i-use-ai-to-create-and-deploy-an-azure-logic-apps-with-business-central-connector/