@praveensri, you're a genius! That was the problem. Removing those two
app settings has fixed the problem. I deploy this function via Azure
DevOps and can see those environment settings in my Bicep. I will be
removing them on Monday morning. You have made my Sunday a better day.
Thank you once again...
@Boschy If everything is working locally on VS Code surface it should
work in Azure as well, from the error it seems the API is not located in
the dlls, the most common reason is the Azure Logic App (check if it
already created) refers the official extension bundle instead of your
bits, check the ap...
@praveensri I have now successfully built a custom built-in connector
and in runs perfectly in VS Code. I can use Postman to trigger the logic
app and it successfully connects to the service I need and gets
data.However, when I deploy the logic app to Azure I get the following
error showing up in th...
@code1993 We do not have such feature at this point. Alternatively, you
could configure two logicapps(standard)(caller and calling) and
configure access policies between them.
A question here- Within the same logic app(standard), If I want to
authorize a workflow should be able to accessed by only a particular
workflow, how can it be done ?
Latest Comments