216 votesNiek Maarse commented
I would also like this. It would be great if when deploying an arm template you can also upload the linked templates with it. The arm template itself is uploaded to azure anyway so uploading the linked templates before execution would be great. doing this you can then source your template from you relative path on your local machine or with azure devops without having the hassle of making it available via an url.
The current way of referencing an url, which should be available to the azure resource manager is quite cumbersum. When using azure devops extra steps like an extra storage account need to be created first, which you create using an arm resource task. Then you need to have a copy step which copies the template you want to link to. And then you need to have a step which executes your arm template which calls the linked template.
If you want to experiment with the linked template you need to push your local linked template to the url which is used by your main template which is again cumbersome.
47 votesNiek Maarse commented
We are building a complete serverless solution on Azure. However We would like to have AAD with apimanagment. Both have a serverless consumptionbased solution. the documentation states the consumptionbased apimanagement does not support AAD.
This is a huge drawback for us to use apimanagement as have AAD integration on apimanagment really is a must for securing our application api's. However the apimanagement Tiers that do support AAD integration are way to expensive to use. The whole idea of serverless is to keep the cost down in case of of low utilization but with the current tier options it rules out apimanagment for us.
Can you add AAD for the consumption tier?