Generate Deployment Script for Logic App fails if there is an email using Office 365 step

[KennyAtInsight]

Does this occur consistently? Yes

Repro steps:

1. Create a Logic App with a workflow that includes a step that using an Office 365 connector to send an email.

   2.Select "Generate deployment scripts…" option from the menu in the Explorer pane.

2. Select region, Logic App name, storage account name and any other required settings.
3. The process will fail with an error that the artifact file office365.parameters.json is missing.

NOTE: I have encountered this issue with Standard Logic Apps. I have not tried it with Consumption Logic Apps yet.

Action: azureLogicAppsStandard.generateDeploymentScripts

Error type: Error

Error Message: Error during deployment script generation: Error: The deployment artifact file 'office365.parameters.json' expected at path '/Users/redacted:username/learn/azure/LogicApps/deployment/MyLogicApp/infrastructure/office365.parameters.json' is missing.

Version: 4.107.3

OS: darwin

OS Release: 23.6.0

Product: Visual Studio Code

Product Version: 1.95.1

Language: en

Call Stack

¨NBSP;

[lambrianmsft]

Hi @KennyAtInsight,

Did you have multiple vscode instances up and running? Do you still happen to have the call stack before this error message popped up on the output window? Usually, I believe that it extracts the parameters to the wrong location and a restart of vscode solves this issue. We have had trouble replicating this so any info that you can provide will be useful!

Generate deployment script is a feature that is only for Logic App Standard so this is not applicable to consumption.

[KennyAtInsight]

Hi @KennyAtInsight,

Did you have multiple vscode instances up and running? Do you still happen to have the call stack before this error message popped up on the output window? Usually, I believe that it extracts the parameters to the wrong location and a restart of vscode solves this issue. We have had trouble replicating this so any info that you can provide will be useful!

Generate deployment script is a feature that is only for Logic App Standard so this is not applicable to consumption.

I do not have multiple instances of VS Code up, but I do have multiple windows each with their own project. Also I just noticed there is a pending VS Code update. I'll try doing that, restarting VS Code and then see where that gets me.

[KennyAtInsight]

I've applied all available updates and even rebooted my system. I'm still hitting the same error. One odd thing I noticed. The office365.parameters.json file is available in the path that the "Create deploy scripts" tool is expecting. The file looks like this. Locally, the location and logicAppName are in local.settings.json. In the deployed version in Azure, I have these set up as environment variables in the Logic App runtime configuration.

{
  "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "location": {
      "value": ""
    },
    "logicAppName": {
      "value": ""
    },
    "connectionName": {
      "value": "office365"
    },
    "connectionDisplayName": {
      "value": "office365"
    }
  }
}

[lambrianmsft]

Can you elaborate on what you mean by having multiple windows each with their own project?

[KennyAtInsight]

Can you elaborate on what you mean by having multiple windows each with their own project?

I had done "File" => "New Window" in VS Code and had my Logic App open in one window and a different project open in another. I was just trying to call this out in case this would have the same impact as having multiple VS Code instances running.