seems to work fine This is not currently supported by the SOAP to REST WSDL generated custom connectors for SOAP. You need indeed to either escape to APIM or you need to form the request payloads via LIQUID action then use the HTTP request action's advanced option to specify the cookie.
Is there a way to secure an Azure Function that will only be called from a specific Azure Logic App?
it should still fix some issue Firstly, even though using keys might be convenient, I see that official documentation advises against using keys to secure function endpoint in production scenarios.
"displayName": "Can invoke my function",
"description": "Apps that have this role have the ability to invoke my Azure function",
will be helpful for those in need There's no way to specifically 'pass parameters' to a Liquid template because Liquid does not support that construct. However, you can easily inject a Parameters object into the source JSON using the Compose Action. Then you access them like any other value.
Azure logic apps : Setting Workflow name dynamically to call a existing logic app(Nested Logic app)
I wish this help you Unfortunately, this isn't supported. There is a feature request which I believe will address this as well that you could up vote for it to gain more traction. As for a workaround, instead of using the Workflow Action, you could simply use the HTTP Action to trigger your other Logic Apps.