Logic App backends in ARM Templates able to be selected like in Portal
When setting up an APIM API and a backend in the portal, we are able to select a Logic App using an experience to find the logic app and the sub-resource. Then a radio button for Azure Logic App resource is selected with the name of the logic app and sub-resource. However, in an ARM template, this is impossible. Setting up the backend to point to the resourceId of the logic and deploying defaults this backend policy to HTTP and does not work unless fixed manually in the portal. Here is the snippet of the ARM template:
"name": "[concat(parameters('apiManagementServiceName'), '/', parameters('statusLogicAppProducerName'))]",
"protocol" enum only allows for http or soap, and this results in an non-working backend policy, so you must go to the portal and fix it. Not a great solution for a CI/CD pipeline without manual touches and RBAC in place for a production deployment.
Suggestion: Allow for selecting an azure resource in ARM Templates and match the experience in the Portal.