ARM template concepts

So, now that we have successfully deployed our first resource, let's continue with expanding our template to include other resources. In this section, we will take a look at dependent resources within the same template and how to use template functions to create configuration values for these resources.

In order to demonstrate the dependencies between resources, let's introduce next the app service instance, which will be hosting the user's API. Technically, this app service only has a single dependency — the app service plan — that will be hosting the app service (that is, the ServerFarm resource type):

{ 
    "type": "Microsoft.Web/serverfarms", 
    "name": "[parameters('resourceNameServicePlan')]", 
    "kind": "app",
    // removed for brevity...