How to deploy an Azure resource using Terraform when it is not available in the AzureRM official provider
This post is going to walk you through the options available when we want to create or update a service on Azure using Terraform, but it is not available on the AzureRM Terraform provider.
The purpose of this post is to try out the new Azure DNS Private Resolver resource. To test it, we’re going to try to solve one of the current issues that Azure VPN has right now: when connected over an Azure P2S VPN the private DNS zone resolution does not work. This becomes quite problematic when you’re using private endpoints to secure some private resources, because there is no easy way to resolve the private endpoint DNS when connected to a P2S VPN.
Deploying infrastructure as code on Azure using Azure Pipelines and Terraform requires a minimal bootstrap process. This process can be done manually, but you’ll have to do it every time you want to start deploying resources into a new subscription. So, having some kind of automation seems the way to go here. And that’s exactly what I want to show in this post, how to programmatically bootstrap an Azure subscription and an Azure DevOps project to start deploying Infrastructure as Code with Terraform.
On today’s post I want to test the Azure DevOps Terraform provider and that’s why I’ll be trying to automate the setup of an Azure DevOps organization using it.
Today I want to try to use Terraform to automate the app registration process in Azure Active Directory.