Cloud OnRamp for SaaS scored the gateway better for Microsoft 365, then a data policy was added that pins that application to the local internet exit. Users are on the worse local exit. Why is the score ignored?
Select an answer to reveal the explanation.
Short Explanation
The measurement said use the gateway, and a later policy nailed the application to the bad local door. You pinned Microsoft 365 with a data policy, and that specific pin overrides the OnRamp score. Some other unrelated data policy is not what forced the local exit.
Full Explanation
Cloud OnRamp for SaaS selects a path from its scores unless a data policy forces the application to an exit. This policy pins Microsoft 365 to the local internet exit, so users stay on the worse path even though the gateway scored better. Remove or change the pin if the score should win. OnRamp does not discard every gateway win just because any data policy exists. A policy that does not match Microsoft 365 leaves the score in charge. The local exit does not have to be shut before a better gateway score can be used. A zone-based firewall does not replace OnRamp scores with a lossy exit. Exam caveat: the pin may have been added on purpose for a site with no acceptable gateway. On this site the gateway is the better score, so the pin is the mistake. Operational check: after the data policy no longer matches Microsoft 365 to the local exit, the application should move to the gateway.