Hello bear with me as i am a nooby, I’m working on a task to export Azure resources and resource groups into Terraform scripts and state files using the aztfexport tool and saving them in azure blob as backup. The goal is to automate this process using powershell script with Read only privileges and avoid exporting sensitive information (e.g., secrets).

azurerm_public_ip.TestGeraldVm: Importing from ID “C:/Program Files/Git/subscriptions/3476gjkfe7-73ed-3444-2124-n8e6ad00jr1z/resourceGroups/henry/providers/Microsoft.Network/publicIPAddresses/TestVm-ip”…

I have a modul which is responsible to create azure private endpoints. For one resource I would like to create two private enpoints, hence I use terraform forech loop as following:

I have following Terraform code running:

While applying my terraform script, I’m getting the following error:

Terraform does not make it easy to loop through subnet IDs. How can you add multiple subnet ids to the cosmos db azurerm resource virtual_network_rule block? I’m able to pass each subnet id, but this error shows up for all of them:

I have a azurerm_linux_web_app reource configured wiht dotnet stack 6.0:

I struggle with the way terraform handles for each loops and counts, i cant seem to figure out how to utilize the locals block to achive this. How can i grab the data disks ids from the reosurce created from a for_each loop? The vm is also from a for_each loop, i cant seem to obtain the value of managed_disk_id to be passed down to the azurerm_virtual_machine_data_disk_attachment resource block.

I’m struggling to find and obtain the secretURL used for the disk encryption key encryption block for the azurerm_managed_disk resource block in terraform. Anyone know how to obtain this? The docs states this, but not sure how to get the secret of the key in the key vault.

Anyone ever run into an issue with terraform and azure key vault access policy? I have an issue where the key vault gets created with a module that sets some default access policies on the key vault. Then when I create another resource that needs to set the system assigned identity access to the key vault, like synapse for example. Terraform will add the azurerm_key_vault_access_policy once the resource is created, however, this will work on the first apply, after that the key vault module and azurerm_key_vault_access_policy will be in a destroy/recreate loop each time I plan depending on which was applied last.