@RaphaelL yes exactly, when doing an inspect on that specific page we see there is a call on the dashboard link using the endpoint https://nxxx.meraki.com/o/xxxxxx/manage/support/firewall_configuration_json   We tried the same endpoint transforming it to https://api.meraki.com/organisations/:organisationId/manage/support/firewall_configuration_json and that is where we get the response {"mode":"login"} with status code 200.   Indeed it would be a great addition, in environments with very strict configurations (deny all by default inbound and outbound), we need to make constant manual checks and updates when required. ... View more