You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I edit a Logic App Standard Workflow in the Azure Portal, add a new action, and search for Azure Function:
I can see both Azure Function Operations (in-app) and Local Function Operations... in other orders, there are two connectors. That is the correct behavior.
However, if I edit my workflow inside Visual Studio Code, I'm only able to use the Local Function Operations:
This is a bug and a huge limitation! How can I call an Azure Function using the in-app connector from VS Code? Why is there this difference?
Plan Type
Standard
Steps to Reproduce the Bug or Issue
Open VS code and try to search for Azure Function
Do the same inside Azure Portal
Workflow JSON
Screenshots or Videos
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi @sandroasp thanks for raising this issue. I just gave it a try and I was able to see both of them. I have a couple of follow up questions
Which version of the vscode extension do you have?
If you look at this path on your computer, which is the latest version you have installed? /Users/<your-username>/.azure-functions-core-tools/Functions/ExtensionBundles/
Inside your project, does your local.settings.json has your subscription value in the following property? WORKFLOWS_SUBSCRIPTION_ID
Describe the Bug
If I edit a Logic App Standard Workflow in the Azure Portal, add a new action, and search for Azure Function:
I can see both Azure Function Operations (in-app) and Local Function Operations... in other orders, there are two connectors. That is the correct behavior.
However, if I edit my workflow inside Visual Studio Code, I'm only able to use the Local Function Operations:
This is a bug and a huge limitation! How can I call an Azure Function using the in-app connector from VS Code? Why is there this difference?
Plan Type
Standard
Steps to Reproduce the Bug or Issue
Open VS code and try to search for Azure Function
Do the same inside Azure Portal
Workflow JSON
Screenshots or Videos
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: