Not a concept that Meraki has.   If you make a change that results in a loss of access, Meraki will automatically roll it back. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Behavior_during_Connection_Loss_to_Cisco_Meraki_Cloud   You can consult the change log to roll back. https://documentation.meraki.com/General_Administration/Organizations_and_Networks/Organization_Menu/Organization_Change_Log   You can duplicate a network prior to making a change so you have an identical copy. https://documentation.meraki.com/General_Administration/Organizations_and_Networks/Cloning_Networks_and_Organizations_in_Dashboard   You can use Meraki provided backup/restore scripts. https://github.com/meraki/automation-scripts/tree/master/backup_configs   I know it is common place in Cisco Enterprise land to do this, but I don't have any customers who have transitioned across to Meraki who keep this concept anymore.  With the automatic roll back and documented change log - what is their left to protect against? ... View more