Cloud OnRamp for SaaS is enabled for a SaaS company's Microsoft 365 traffic. One branch has only an MPLS transport and no local internet exit. Local probes for that site stay absent. Why?
Select an answer to reveal the explanation.
Short Explanation
You cannot time a drive down a road your site does not have. This branch has MPLS and no local internet exit, so it cannot send a local Microsoft 365 probe, even though a gateway that does have internet can still be measured.
Full Explanation
Cloud OnRamp for SaaS builds a local measurement only from a site that can reach the application on the internet. A branch whose only transport is MPLS, with no direct internet exit, has no interface from which to send that local probe. The absence of local probes is expected until the site has a local internet path. The feature can still use probes from a gateway that does have internet, and the branch may be steered toward that gateway. An AWS virtual private gateway does not originate Microsoft 365 probes for Catalyst SD-WAN. Disabling OMP would remove the overlay routes the site needs and is not a prerequisite for SaaS probing. The zone-based firewall does not generate those probes, and taking every tunnel administratively down would blackhole the overlay rather than start a measurement. Exam caveat: adding a local internet exit later is not enough if policy then forces Microsoft 365 back to the gateway. The probe and the steering policy have to agree. Operational check: confirm the branch transport list has no internet color with a working NAT exit, then compare a site that does. The second site should show a local probe for the same application.