Meraki Dashboard URL Update - PCI Compliance

[MiriamK]

As part of our ongoing commitment to security and compliance, Cisco Meraki is rolling out an enhancement to our network infrastructure in alignment with Payment Card Industry (PCI) standards and to further protect your data.

This change involves an update to Meraki dashboard URLs and will begin rolling out on August 18, 2025.

What’s New

Some services accessed through the Meraki dashboard will begin using a new subdomain. For example:
• Current URL: n23.meraki.com
• New URL: n23.dashboard.meraki.com

The updated “.dashboard.meraki.com” subdomain will become the new standard moving forward. The original URLs will remain supported and automatically redirect.

As part of this effort, Meraki services will adopt a new certificate chain. This chain should be trusted by modern browsers, but older browsers or systems may require updates to stay compatible.

Action Required (if applicable)

Most customers will not need to take any action. However, if your organization uses:
• URL filtering
• Domain allowlisting

Please ensure the new dashboard.meraki.com subdomain is added to your allowlist by August 17, 2025 to avoid any disruption in dashboard access from end user devices in that network.

Timelines
• New URL rollout: August 18, 2025
• Note: The URL change will not impact any functionality or performance of the Meraki cloud platform.

Have more questions? Read more details in our documentation page and follow up with your Sales contact or reach out to the Meraki Support team.

[RaphaelL]

Will this affect customers that are not using the mega proxy for API usage ?

[spaladug]

Hi @RaphaelL  Great question. API requests sent to api.meraki.com, which is the only supported destination for API requests, will not be impacted. However, if customers are sending API requests directly to shard hostnames—an action not officially supported after the introduction of API megaproxy year ago—and their script cannot handle HTTP redirects, they will be impacted. Customers should use the officially supported API infrastructure and update their scripts to send API requests to api.meraki.com as per our documentation.

[RaphaelL]

Perfect ! Well aware this is not supported but when Mega proxy suffered issues years ago , some people made requests directly to the shard. In theory we have migrated all that code to the mega proxy but I will have to make sure. Thanks for the reply !

[spaladug]

Thanks for that context @RaphaelL and happy to help.

[rhbirkelund]

Will this also affect customers who have configured SSO for Dashboard login? If I recall correctly, SAML SSO uses shard urls. 

[spaladug]

Hi @rhbirkelund . Great question. It will not affect SAML users as the consumer URLs showing in Organization -> Settings will stay the same.