Hello @PabloR , thanks for bringing this to our attention. Yes, tls1.2 should work for the customer as 1.0 is deprecated.   https://documentation.meraki.com/General_Administration/Cross-Platform_Content/FAQ%3A_Meraki_Authentication_to_Require_TLS_1.2_or_Later_Version ... View more

@Flembot Thanks for bringing this to be community. I would recommend establishing a baseline of the issue before requesting a firmware downgrade/rollback. Were you able to connect to the local status page of the spare MX(This should provide info on why the device is not showing up online)? If yes, what info was the MX reporting on its connection tab? Regarding WAN1 and WAN 2 flapping, were you able to confirm it was not related to an issue upstream? My assumption is there is an issue upstream causing the primary WAN link to go down and failover to the secondary. However getting a capture or data to confirm this would be the best approach. ... View more

@jcbrannan Thanks for taking the time to share this with the community. After a graceful failover, existing flows on the back-up link would continue to used that link until the flow is stopped or no longer exist, while new flows would start going out the active link. In terms of reporting(This would fall under a feature request), and the best way to see which traffic is going out through the backup WAN link would be to take a packet capture on that link. ... View more

Hello @thomasthomsen , thanks for bringing this to be community.   Yes, this should work. The two Orgs are different, and do not share information(such as route) on the Meraki infra. This should work A-okay as long as the route configuration is configured appropriately in Azure. ... View more