Sometimes you create a server in Azure and only find out afterwards you need to change the Virtual Network is resides in. From the official Microsoft Documentation, we learn that this is normally a difficult task and, in some cases, unsupported or requires a redeployment of the server.
Recently at a customer I had a chance to try something new, using Terraform to Move a Server Nic from one Virtual Network Subnet to a different virtual network subnet. Let’s look at how the process works,
We will use main.tf to create the server (If not created already) by running the azure-pipelines.yml Pipeline
We will run a second Pipeline called azure-pipelinesAfter.yml that calls the PowerShell.ps1 file that will delete the computer object, and call the mainAfter.tf file which will change the NIC Subnet and add the server back to the original OS Disk.
The second pipeline and mainAfter.tf file is in a separate folder otherwise terraform will just combine the two “.tf” files and try and build both scenarios
Disclaimer The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.