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

    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

    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

    VS Code Planning mode

    After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
    Read more