Meraki Community

ChristinaFA · ‎Feb 27 2023

Turns out it was our L7 firewall Country Blocking policy. Some outlook-related hostnames (like outlook.ha.office365.com) were being resolved to IPs in countries that we block. Of course there is NEVER anything in the Meraki logs when a country block rule is hit, so we were flying blind. Although I think if you use syslog you can see something, is that right? Also, I thought white-listing a client source IP meant that IP; Is exempt from all firewall rules, both Layer 3 and Layer 7 (Applies to both the MX Security Appliance and the MR Access Points)

ChristinaFA · ‎Feb 27 2023

Yes, but I removed all content filtering categories and white-listed my test IP on the dashboard, but the issue remained.

ChristinaFA · ‎Feb 27 2023

We just experienced a Meraki network-wide outage (over 200 sites) this morning where users were unable to get to outlook.office365.com and outlook.office.com. All sites are configured to route to the internet directly out of their local ISP via an MX firewall. Did anyone else experience this? It lasted at least 2-3 hours. It just resolved by itself without any changes made to any configuration. During the troubleshooting, as a test, I set one network to have a default route via the site-2-site VPN at our hub site (which then routes to the internet via an FTD), with that configuration, the user was able to get to office365. What could have happened? Anyone know?

Meraki Community

About ChristinaFA

ChristinaFA

Community Record

Badges

Re: outlook.office365.com and outlook.office.com - outage via MX's

Re: outlook.office365.com and outlook.office.com - outage via MX's

outlook.office365.com and outlook.office.com - outage via MX's

Re: outlook.office365.com and outlook.office.com - outage via MX's

Re: outlook.office365.com and outlook.office.com - outage via MX's