I recently upgraded my Public IP SKU in Azure from Basic to Standard as Microsoft suggested. Right after the upgrade, my VPN tunnel to Azure went down, and I've opened a support ticket, but the reps haven't been very helpful—just suggesting I reboot everything. They seem to think the issue might be with my Cisco equipment (I'm using a Firepower ASA on-prem and vASA in Azure), but the only thing that changed was the IP upgrade. I'm looking for advice from those with more Azure experience on what might have gone wrong and how to guide support. Thanks in advance!
3 Answers
Did you happen to use the migration script mentioned in Microsoft's guidance for the upgrade? It might help to avoid any further issues.
Do you have a Network Security Group (NSG) attached to your VM's NIC? It’s usually necessary to allow traffic. What type of Azure endpoint are you using for your VPN?
Yes, there's an NSG attached that was working fine before the upgrade. I think there might be additional configurations needed now. The Azure endpoint is a Cisco virtual ASA VM.
If you had read the instructions, you would have seen that there was expected downtime. The IP needed to be disassociated. Did you even check the guidelines before proceeding?
I appreciate the reply, but I did follow the documentation for the SKU upgrade. Downtime is expected when you dissociate the IP, but it shouldn't persist after re-association once the upgrade is complete. That's the issue I'm facing.
No, I just followed the standard procedure in the Microsoft documentation, which involved disassociating the IP from its NIC before upgrading and then re-associating it. It seemed straightforward, but my tunnel dropped immediately afterward.