Understanding the one that rules them all
Before jumping into our declarative deployment options, it is important to first step back and understand what is the single endpoint that rules everything.
No matter which tool or language you choose, they will ultimately all talk to the same Azure API, namely, the Azure Resource Manager (ARM) endpoint. The commercial endpoint is https://management.azure.com/. Any call to this endpoint requires the caller to provide a valid access token, retrieved from Azure Active Directory. Remember, in our Understanding the ARM template deployment scopes section, we discussed the least privilege approach and the empowerment of the deployment tools. That is what this access token will be validated against, for any interaction with the ARM API.
Terraform, Azure Bicep, native ARM templates, and imperative client tools all talk to the ARM endpoint. This is important, because if a feature is not exposed through the ARM endpoint, none of the tools will...
