How to use/create ARM templates for deployments
I was building a lab for the creation of a Hybrid Connection Manager (HCM) link between an Azure App Service and an Azure VM within a VNET. In most cases, yes, you use HCM to access resources hosted within a another network (not always on Azure), but I didn’t have one of those and therefore created the VNET with a HCM and WEB server within it. As seen in Figure 1, I have a VNET, a VM, an App Service and all the other required features necessary to support those Azure features.
Figure 1, automatic deployment on Azure using ARM templates
Figure 2, download automatic deployment on Azure using ARM templates
There is a very nice description of how to then use these scripts to deploy here. See the other related articles as well on that same page where it discusses not only deploying using PowerShell, but also using CLI and via the portal.
Once I downloaded the script, I deleted the resource group.
Figure 3, upload automatic deployment on Azure using ARM templates
Figure 4, upload and save automatic deployment on Azure using ARM templates
After selecting Save, review the output, agree to the Terms and Conditions, then select the Purchase button. After some modifications:
Figure 5, deploy automatic deployment on Azure using ARM templates
Although it did take some time, it completed successfully and was a happy person.
To get a overview of the project I worked on, read the following articles as well.
- Required parameter ‘adminPassword’ is missing (null).
- osDisk.managedDisk.id’ is not allowed
- Creating an Azure App Service Hybrid Connection
- How to deploy to Azure using an ARM template with PowerShell
- How to use/create ARM templates for deployments
- Deployment template validation failed: Circular dependency detected on resource
- How to Azure Function App with Hybrid Connection
- Troubleshooting App Service Hybrid Connection Manager