Stores in one city send Microsoft 365 through a Cloud OnRamp for SaaS gateway site on another continent. A store in the same city has a healthy internet exit and is not a gateway. What should change?
Select an answer to reveal the explanation.
Short Explanation
The score is being taken on another continent while a healthy exit sits in the same city. You make the city site a SaaS gateway so the stores stop hairpinning overseas. Shutting that exit would leave the long path as the only choice you have.
Full Explanation
Cloud OnRamp for SaaS compares the paths it is allowed to probe, including the configured gateway sites. These stores use a gateway on another continent, so Microsoft 365 rides that long path even though a store in the same city has a healthy internet exit and was never made a gateway. Add the city site as a SaaS gateway and let the local stores use it. Disabling OnRamp removes the measurement and leaves whatever static path remains, which is the overseas one. Shutting the city internet exit destroys the closer probe. VPN 512 does not select a SaaS exit for user traffic. Exam caveat: the city site needs a working NAT DIA exit or it still cannot probe. Naming it as a gateway does not create internet. Operational check: a store in the city should show the city gateway as the chosen path, and the overseas site should no longer carry that city's Microsoft 365.