Use case · Microsoft 365
Microsoft 365 local internet breakout at every branch
Teams calls, Outlook and SharePoint go straight out of each branch's own internet line instead of being hauled back to head office and out again, while everything else still goes through your firewall.
What local internet breakout is, and why Microsoft asks for it
When every branch sends its internet traffic through one exit, usually the head-office firewall, Microsoft 365 takes the long way round: out of the branch, across to head office, through the firewall, and only then to Microsoft, which may well have a front door nearer the branch than head office is. Local internet breakout sends that traffic out of the branch's own line instead.
Microsoft recommends exactly this for its most latency-sensitive traffic. Teams calls pick up delay and jitter on the detour, and the head-office line carries traffic that never needed to go there. Microsoft protects these connections at its own end, which is why it asks for them not to be routed through a proxy or inspected on the way.
Microsoft's three categories
Microsoft publishes the addresses its services use, sorted into three categories, and says how each should be treated:
| Category | What it covers | Microsoft's advice |
|---|---|---|
| Optimise | The most performance-sensitive traffic, such as Teams media, Exchange Online and SharePoint | Send directly from each office, without proxies or inspection |
| Allow | Other Microsoft 365 services, including sign-in | Send directly where you can |
| Default | Everything else Microsoft 365 uses | Can go the normal way, through your firewall or proxy |
Most organisations start with Optimise, which is where the benefit is, and add Allow if they are happy for more to bypass the firewall.
How Weft does Microsoft 365 breakout
- The list comes from Microsoft. Weft reads Microsoft's published Microsoft 365 endpoint list and checks it for a new version every hour. You do not maintain address lists by hand.
- You choose by service and category. Tick Optimise for Exchange, SharePoint and Teams, say, and the console shows exactly how many address ranges each covers and which are in effect.
- One choice, every branch. It applies to every site at once, and each change, including Microsoft's own updates, goes to a test site first before it reaches the rest.
- 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 head-office firewall.
What happened when we turned it on
In a real test, a branch was sending all its internet through head office's firewall, and a PC there opened Outlook on the web every ten seconds. Within half a minute of choosing Optimise for Exchange, SharePoint and Teams, the firewall stopped seeing Outlook traffic from the branch, and over the next seven minutes the PC opened Outlook 48 times without a single failure. Microsoft's sign-in service, which is in Allow, carried on through head office as chosen. Microsoft 365 local breakout at every office has the full run.
Not only Microsoft 365
Other call and desktop services can break out locally the same way, from the address ranges each vendor publishes: Zoom Meetings and Zoom Phone, Webex, Google Meet, Slack huddles, RingCentral, 8x8, and Windows 365 and Azure Virtual Desktop. You can add your own list too. Weft recognises this traffic by where it is going, not by looking inside it, and it can also learn a service's addresses from the names devices look up through the site.
Two lines at a branch
If a branch has two internet lines, you can choose which line each service prefers: Microsoft 365 on the fibre, say, and Zoom on the other. When the line a service uses fails, its traffic moves to the other in about a second, and moves back only after the line has been up for 90 seconds. Two internet lines, and Teams keeps working shows it with a line cut mid-call.
IPv4 today. Microsoft also publishes IPv6 ranges; Weft applies the IPv4 ranges, so a device that reaches Microsoft 365 over IPv6 takes its usual path. IPv6 support is planned.
Questions
Does local breakout weaken our security?
It means your head-office firewall no longer sees that traffic, which is what Microsoft recommends for Optimise. If you rely on the firewall to log or filter Microsoft 365, tick less: only what you choose leaves locally.
Does each branch need its own internet line?
Yes. Local breakout leaves by the branch box's own line; a site with no line of its own has nowhere local to send it.
What happens when Microsoft changes its addresses?
Weft picks up the new list within the hour and rolls it out like any other change, test site first. An update that looks wrong is held and you are told.
Can we break out Teams only?
Yes. Choose by service and category, so Teams (listed by Microsoft under Skype) can break out on its own.