How to move Meraki vMX to a new subscription

Question

I need to move my Meraki vMX to a new subscription in Azure. I would like to know if anyone has done this and what the steps to do so. I'm trying to see if there's other option then deleting the vMX and then redeploy from scratch.

Any help is greatly appreciated.

Thanks

Kit Cheng

Answer 1

Hi ,

Thanks for reaching out to Microsoft Q&A.

Azure does not natively support moving resources such as vMX appliances between subscriptions due to their dependencies and configurations. Here are the key steps you can take to achieve this:

Option 1: Redeploying the vMX (Recommended Approach)

This is the most common and straightforward approach:

1. Backup Configurations:
   • Log in to your Meraki dashboard and back up your current vMX configuration, including IP addresses, routes, NAT rules, and any other custom settings.
2. Remove vMX from the Current Subscription:
   • Delete the current vMX resource group from the source Azure subscription.
3. Deploy vMX in the New Subscription:
   • Go to the Meraki dashboard and create a new vMX license or reassign the existing license to the new instance.
   • Deploy the vMX in the new Azure subscription using the deployment guide provided by Meraki.
4. Reconfigure Network Settings:
   • Use the backup from Step 1 to reapply settings such as VPN configurations, subnets, and routes.
5. Test Connectivity:
   • Verify that the vMX is functional in the new subscription and that all associated connections are operational.

Option 2: Explore Resource Migration (Advanced and Limited)

If deleting and redeploying is not ideal, you may explore these advanced steps. Note that this method requires significant manual intervention and is not officially supported for vMX by Azure or Meraki.

1. Export Template and Settings:
   • Use Azure Resource Manager (ARM) templates to export the configuration of the vMX and its associated resources.
   • Save these templates and note the dependencies like virtual networks, subnets, and public IPs.
2. Deploy Resources in the New Subscription:
   • Modify the exported ARM template to fit the new subscription’s requirements (e.g., resource group, region, etc.).
   • Deploy the template in the new subscription using Azure CLI or the Azure Portal.
3. Reconnect vMX:
   • Reconfigure the Meraki dashboard to point to the new deployment, including updating public IPs and VPN settings.
4. Test the Setup:
   • Validate that the new deployment is functioning as intended.

Things to Note:

• Azure Limitations: Azure does not support direct subscription transfer for resources like vMX, as it involves dependencies on networking components.
• Downtime: Expect some downtime if you choose to redeploy or reconfigure.
• Support: Contact Meraki Support for guidance on license reallocation or any specific concerns related to your deployment.
• Cost Implication: Review the costs of redeployment and ensure proper scaling in the new subscription.

While redeploying the vMX may seem inconvenient, it ensures a clean setup and avoids unforeseen issues that might arise from partial migrations.

Please feel free to click the 'Upvote' (Thumbs-up) button and 'Accept as Answer'. This helps the community by allowing others with similar queries to easily find the solution.

Answer 2

• 1. Prepare the New Subscription:
  • Ensure the new Azure subscription is set up, with the appropriate permissions and networking resources (like virtual networks, subnets) available.
  • Create a new Resource Group within the target subscription, if necessary.
  2. Deploy a New vMX in the New Subscription:
  • In the new subscription, deploy a new Meraki vMX instance using the Azure Marketplace.
  • Make sure the new vMX instance is deployed in the same virtual network (vNet) and subnet as the old vMX, ensuring consistency in your network configuration.
  3. Configure the New vMX in the Meraki Dashboard:
  • Log in to the Meraki Dashboard and remove the old vMX instance from your network.
  • Add the newly deployed vMX in the new subscription to your Meraki network, configuring it as required (IP settings, security policies, etc.).
  4. Update VPN and Network Settings:
  • Site-to-Site VPN: If you're using site-to-site VPN, update the configuration in the Meraki Dashboard to use the new vMX instance.
  • Public IP Addresses: If the new vMX instance has a different public IP, update any external services or VPN peers that rely on the public IP.
  5. Test the New vMX Setup:
  • Test the connection to the Meraki vMX, ensuring that all VPNs and network settings are functioning correctly.
  • Verify that there is no network downtime or disruptions during the switch over.
  6. Decommission the Old vMX:
  • Once the new vMX is up and running with all configurations in place, you can safely decommission the old vMX in the previous subscription.