Send Microsoft 365 traffic direct from the branch

The problem

When every branch sends its internet traffic through one exit, Microsoft 365 takes the long way round. Teams calls pick up latency and jitter, and a head-office line carries traffic that never needed to go there. Microsoft itself recommends local breakout for this traffic.

How Weft does it

• The list comes from Microsoft. Weft reads Microsoft's published Microsoft 365 endpoint list and checks it for a new version every hour.
• You choose the categories. Break out the latency-sensitive Optimize category, or add Allow as well. The console shows exactly which address ranges are in effect.
• A bad update cannot rewrite your network. Because the list is external, an update that suddenly grows or claims private address space is held: the last good list stays in force and you are told.
• Everything else is unchanged. Breakout is a named exception. Other internet traffic still follows your normal route, including through your firewall.