Skip to main content

Generate Terraform configuration files from your Azure resources

While everyone is focusing all the announcements at Build 2025, I'm still processing some of the older recently announced features. A feature that I am happy that is finally available in preview is the Terraform export functionality in the Azure Portal.

A similar feature already exists for some time for ARM and Bicep but now we can finally export to Terraform configuration files as well.

Let’s give it a try…

A short walkthrough

  • Go to the Azure portal and browse to a specific resource. From there go to the Automation section and click on Export template.

  • Click on the Terraform tab. The first time I did this I got the error below:

 

  • The reason is that you first need to register the Microsoft.AzureTerraform resource provider at the subscription level.
  • Go to your Subscription in Azure. There open the list of Resource Providers.

 

  • Search for Microsoft.AzureTerraform resource provider and click on Register.

 

  • It can take some time before the resource provider got registered so be patient.

 

  • Once registration has completed, go back to the resource. Click on Export template again in the Automation section and this time you should get a Terraform configuration file on the Terraform tab:

 

    More information

    Announcing Public Preview of Terraform Export from the Azure Portal | Microsoft Community Hub

    Azure/aztfexport: A tool to bring existing Azure resources under Terraform's management

    Overview of the Azure Terraform Resource Provider | Microsoft Learn

    Labels:

    Popular posts from this blog

    Azure DevOps/ GitHub emoji

    I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
    Read more

    Kubernetes–Limit your environmental impact

    Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
    Read more

    Podman– Command execution failed with exit code 125

    After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
    Read more