Azure Terrafy (Aztfy) has been rebranded to Microsoft Azure Export for Terraform (Aztfexport). The original name was catchy, and I enjoyed saying it. The new name is a mouthful, so I will refer to it as Terraform Export for Azure or Tea, as I am British and like tea. The PR for this change of name can be found <a target="_blank" href="https://github.com/Azure/aztfexport/pull/370">here</a>.
<h1 id="heading-does-this-change-the-functionality-of-the-tool">Does this change the functionality of the tool?</h1>
No, the tool still works as designed. This is just a rebrand and will not affect your use of it. But upgrading anything above v0.11.0 will result in the following changes:
<ul>
<li>The aztfyResourceMapping.json resource mapping file is now aztfexportResourceMapping.json
</li>
<li>The aztfySkippedResources.txt file for skipped resources is now aztfexportSkippedResources.txt
</li>
<li>The config directory has changed from .aztfy to .aztfexport
</li>
<li>And finally, the command used to call it is no longer aztfy but is aztfexport
</li>
</ul>
<h1 id="heading-so-what-happens-when-i-upgrade">So what happens when I upgrade</h1>
When you upgrade using the below providers, it should update the configurations:
<ul>
<li>Go
</li>
<li>Winget
</li>
<li>Homebrew
</li>
</ul>
However, these things do not always go to plan, so I recommend uninstalling and reinstalling using any of the above package managers, <a target="_blank" href="https://github.com/Azure/aztfexport">following the documentation provided by Microsoft</a>. Just make sure any existing projects to rename the configuration files to match.
<div class="hn-embed-widget" id="buymeacoffe-butyellow"></div>

Azure Terrafy (Aztfy) has been rebranded to Microsoft Azure Export for Terraform (Aztfexport). The original name was catchy, and I enjoyed saying it. The new name is a mouthful, so I will refer to it as Terraform Export for Azure or Tea, as I am British and like tea. The PR for this change of name can be found [here](https://github.com/Azure/aztfexport/pull/370).

# Does this change the functionality of the tool?

No, the tool still works as designed. This is just a rebrand and will not affect your use of it. But upgrading anything above v0.11.0 will result in the following changes:

* The **aztfyResourceMapping.json** resource mapping file is now **aztfexportResourceMapping.json**
    
* *The* **aztfySkippedResources.txt file** for skipped resources is now **aztfexportSkippedResources.txt**
    
* The config directory has changed from **.aztfy** to **.aztfexport**
    
* And finally, the command used to call it is no longer **aztfy** but is **aztfexport**
    

# So what happens when I upgrade

When you upgrade using the below providers, it should update the configurations:

* Go
    
* Winget
    
* Homebrew
    

However, these things do not always go to plan, so I recommend uninstalling and reinstalling using any of the above package managers, [following the documentation provided by Microsoft](https://github.com/Azure/aztfexport). Just make sure any existing projects to rename the configuration files to match.

%%[buymeacoffe-butyellow]

What you need to do to migrate

AZtfy is dead! Long live AZtfexport

James is a Microsoft MVP and MCT with more than a decade of career experience in the tech space. James's blog focuses on all areas of Cloud and DevOps.


Over 10 years of career experience in IT, I am focusing on developing and sharing my cloud and coding knowledge. My blog aim is to help grow and contribute to many communities.