A branch has a healthy local internet exit, and Cloud OnRamp for SaaS is enabled for Microsoft 365. This site was excluded from local probing. Traffic stays on the gateway path. Why is the local exit unused?
Select an answer to reveal the explanation.
Short Explanation
You cannot prefer a path you chose not to measure. Because you excluded this site from local probing, OnRamp has no local score to prefer and keeps Microsoft 365 on the gateway. Your healthy local exit is not disqualified for being healthy.
Full Explanation
Cloud OnRamp for SaaS can prefer a local exit only when the site is allowed to probe it. Because this branch was excluded from local probing, OnRamp has no local score to compare, so Microsoft 365 remains on the gateway path even though the local exit is healthy. Include the site in local probing if you want that exit to compete. A healthy exit is not disqualified until its loss is worse than the gateway; health does not require that comparison to make it eligible. Shutting down OMP is not required to use a local score, and doing so would disrupt the overlay rather than enable local probing. A SIG credential does not suppress local probes for every enabled SaaS application; it does not explain the missing score here. Exam caveat: allowing probes provides a local score, but the local exit is preferred only if that score wins. Practical check: remove the site from the local-probe exclusion, verify that a local Microsoft 365 probe and score appear, then confirm the path can move to the local exit when its score wins.