Private Endpoints and DNS Part Deux: Azure Private DNS Zones
This is a second video on Azure Private Endpoints and DNS. Previously, we reviewed options for DNS name resolution with Private Endpoint that included
Author: Travis Roberts
Private Endpoints with Azure Storage File Shares
Azure services are publicly available over the internet by default. That works for many services, but sometimes we need to limit access to internal
Override File in Terraform and Azure
I try to find a useful example that demonstrates functionality when I create these posts and videos. Unfortunately, with Override files in Terraform, that
Dynamic Blocks in Terraform with Azure
Resources in Terraform are deployed as top-level resources. A server or App Service plan for example. These top-level resources include inline, or sub-resources; blocks
Private Endpoints and DNS in Azure
Private Endpoints in Azure provide a secure way to access resources over the private, internal network. But the options for configuring DNS for Private
Remote Backend State with Terraform and Azure Storage
Until now, we have developed our Infrastructure code as a single developer. As a result, our state file is created and maintained on the
Use Existing Resources with Data Sources in Terraform and Azure
Use Terraform long enough, and eventually, we’ll need to use an existing resource not managed by Terraform as part of the deployment. A typical
Use For_Each in a Terraform Module with Azure VNets and Bastion Host
You have laded on another post and video in a series on Terraform and Azure. This post and accompanying video looks at a more
