Skip to main content

Migrate IP Address from one Azure VM to another

Introduction:

In the previous blog, we saw that you can migrate Data from crashed VM to a new VM. Generally, if a machine is re-setup, the IP address of the machine changes implying that whichever services consumed the services from the original machine has to be reconfigured.

In this blog, we will see how to migrate IP Address (Network Interfaces) from one Azure VM to another Azure VM.

Pre-requisites:

  • Understanding of Azure
  • Azure Subscription

Demonstration:

1. Disassociate your Network Interface:
Disassociating the Network Interface will disable the networking connectivity with a specific IP. Please note that your existing work has to be saved to avoid disturbed Network Connectivity.
Disassociating works similarly to physically disconnecting your machine from your gigabit ethernet.
Goto VM(to disconnect from) > Public Address > Overview > Hit the Disassociate Button

Goto Public Address on Azure VM

Network Interface - Overview - Disassociate


2. Associate the Network Interface:
Associating the Network Interface to a specific machine will let you connect the VM through that specific network.
In this case, you will need to go to Network Interface and associate with the VM to which you want to connect.
Goto Network Interface > Associate > Select the VM Resource Group.
Network Interface to Associate

Associate with the VM Resource Group

All of your IP Addresses from the previous VM are migrated to the new VM.

In order to reflect your changes with VM, it is ideal to restart the VM. However, most of the changes are real-time in nature.

Conclusion:
The purpose of this blog was to keep all the configurations outside the same as this can be tideous and time consuming.
I hope this blog helps you from multiple reconfigurations when your Azure VM fails. 

NOTE: For Production VMs, it is recommend to have Business Continuity and Disaster Recovery Setup. Refer to my blog https://www.olisterr.blogspot.in/2021/05/setup-sql-server-backups-for-business.html

Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe