vMX Public IP SKU change from Basic to Standard Azure

[Tarmahmood1]

Hello,

Anyone did the Public IP sku change from basic to standard in Azure. Will it work with migration tool "Upgrade to Standard SKU - Microsoft recommends Standard SKU public IP address for production workloads". I am suspecting maybe it wont change as resources are locked and managed by Meraki. Should i delete and redeploy the vMX? thanks

[alemabrahao]

Microsoft has not released a migration tool that supports changing the Public IP SKU for Meraki vMX deployments.

Re: Change SKU from basic to standard on IP address on Meraki VMx - The Meraki Community

In this case it is recommended that you redeploy vMX if you need to migrate to a standard SKU public IP.

[Tarmahmood1 · Accepted solution]

@Ale hello again, ok just now i have changed the SKU from basic to Standard without deleting the existing VM. so we dont need to redoply the vMX. It is to be noted that i have owner role on subscription level in Azure. maybe because of this it was possible.

1. First shutdown the vMX VM in azure. It will ask about to keep this Public IP save or delete. Save the PIP.

2. Go to to public IP addresses in Azure. look for the PIP associated to Meraki VM NIC.

3. Disassociate it. 

4. click on the alert message "Upgrade to Standard SKU - Microsoft recommends Standard SKU public IP address for production workloads" and within few seconds it will change the SKU from basic to standard.

5. Associate the Public IP again with Meraki NIC. Turn on the vMX vm.

[Mloraditch]

I could swear this was not previously possible and am wondering if Meraki updated something.  I've now tested and done this successfully and the shutdown is not even required. I end up with a traffic blip so small I see it on my live uplink graph.

So TYVM for trying and figuring it out as I had a much longer plan in place to redeploy over 100 vMXs.

[Tarmahmood1]

Ah ok, that's good to know it can happen without shutdown. 

[RavinderSingh]

We have Older Meraki vMX deployments in Azure which had locks on the managed application, managed resource group, and other resources that made it impossible to touch.

Any way around or need to delete the managed application from Azure and redeploy

[Mloraditch]

If Azure is blocking the action you are trying to take, you need to redeploy. Meraki can't/won't unlock anything. Some of oldest deployments were locked and needed redeployment, but very few.

[RavinderSingh]

Yes i am getting the lock on resource group where meraki vm is deployed, any way to find out whether its old deployment on new.

[Tarmahmood1]

I am not sure how to verify whether it is an ARM or classic deployment(maybe you can ask MS). However, I did upgrade to one of the vMX  that was deployed in November 2021, and I was able to change the SKU without redeploying. Before I tried it, a colleague mentioned that he had to redeploy the vMX because he encountered the same issue you are facing now. If you are certain that you have the Subscription Owner role but still cannot upgrade without deleting the vMX, then redeployment is the only option.

[RavinderSingh]

It doesn't looks be an Azure classic VM, but i am getting the below warning when trying to remove the IP for migration.

System deny assignment created by managed application /subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Solutions/applicationsxxxx at scope /subscriptions/xxxx/resourceGroups/xxxxx-20211023182933.

[Mloraditch]

There is no date I'm aware of that's ever been acknowledged. It's not all that relevant in that support can't change anything even if it's some sort of azure error. If you can't make the change due to a denial you have to redeploy. The whole process takes about 15-20 minutes usually.