FortiGate load balances traffic across all members that meet the SLA targets, depending on the strategy used.
The outbandwidth hash mode can be selected with load-balancing strategies to distribute traffic based on flow characteristics.

Priority/failover in FortiSASE geofencing lets administrators prefer an on-premises FortiGate for users in specified countries and fail over to a FortiSASE security POP only if the on-premises device is unreachable.

Download from the FortiSASE portal: Administrators can provide users with access to the FortiSASE portal where they can directly download a pre-configured installer. This installer is uniquely tied to the organization's SASE instance, ensuring the client automatically registers to the correct cloud EMS upon installation.
Invitation Email: This is the most common administrative method. The FortiSASE portal (via its integrated EMS) allows administrators to send an invitation email to specific users or groups. This email contains direct download links for various operating systems (Windows, macOS, Linux) and the necessary invitation code for zero-touch registration.

The graph shows the latency history for the Corp_HC SLA, and port1's latency remained below the defined threshold during the past 60 seconds. This indicates that port1 continuously met the Corp_HC latency SLA and was therefore monitored as healthy.

In an SD-WAN rule, you can steer application traffic by using Internet Service Database (ISDB) entries. Facebook and LinkedIn are predefined ISDB objects in FortiGate, so the correct way is to select them in the Internet service field under Destination. This ensures that all traffic to these applications is matched and routed through the chosen (less costly) link.