Hello George S. (IT Admin)
To troubleshoot this issue, can you please cross verify the below things.
- Please verify the new public IP and Meraki private subnets (Address Spaces) on the Azure Local network gateway.
- Since Meraki typically uses Policy-Based VPNs, ensure the Azure VPN gateway and Meraki have the same VPN type.
- Re-create the new VPN connection under the virtual network gateway and link it to the new local network gateway.
- Check if any NSG and firewall rules properly allow traffic to the new Meraki IPs.
- Ensure the IPsec policies on the Azure VPN gateway exactly match those on Meraki.
- Use the "Connection Troubleshoot" tool on the Azure portal to test from source to destination, validating that the traffic is reaching Meraki. Please share the output results in a screenshot to understand the connectivity flow.
Refer: Configure custom IPsec/IKE connection policies for S2S VPN and VNet-to-VNet: Azure portal
Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.