Microsoft 365 Outage Hits Advisor Inboxes, Not Flights — Yet

A global Microsoft 365 outage that began at roughly 4.54am AEDT on Friday has knocked out Outlook, Teams, SharePoint and Copilot, cutting many travel advisors off from the supplier confirmations and client enquiries that run their business.

Microsoft was still working to restore access to its email and collaboration suite at the time of publication. Travel Weekly itself was among the businesses without email. That detail tells you the breadth: this is a workplace productivity failure, not a travel-sector failure.

And that's the key distinction. No airline, airport or booking platform has reported operational disruption from this incident. Unlike the July 2024 outage, which hit airline back-end systems and grounded carriers, this event appears confined to email and Microsoft apps. The risk for advisors is communication, not flights.

The July 2024 CrowdStrike-linked failure is the useful comparison here. That one broke check-in and dispatch systems. This one breaks the inbox — slower, quieter, but capable of costing a booking if a ticketing deadline slips past unnoticed.

What should advisors check first?

The immediate exposure is silent data loss. Email sent during the outage may have been delayed or bounced, so advisors should review confirmations, e-tickets and supplier notices due in the past 24 hours, and log in to supplier portals directly rather than waiting for an email to arrive.

Anything time-sensitive needs a phone call. For departures in the next few days, or bookings with a ticketing or payment deadline, advisors should call the supplier to confirm status. A missed confirmation email becomes a real commercial problem when it sits behind a dead server until Monday.

What about clients and internal work?

Advisors should post a phone number and alternative contact on their website, social channels and voicemail, and send a short message from another channel such as SMS where possible. Clients who can't reach their agent tend to reach the supplier direct next time.

Internally, if Teams is down, coordination should move to a phone call or a messaging app until service returns. Two advisors at the same desk is also a system, and it doesn't require a login.

Is there a security angle?

Yes, and it follows a familiar pattern. Outages are often followed by phishing emails posing as service updates. The defence is simple: don't open unexpected links, and go to Microsoft's own status page directly rather than trusting whatever lands in the inbox once it flickers back to life.

What's the longer-term lesson?

The resilience question is the one worth answering before the next outage. A personal email address is a poor backup for client data — the security and privacy exposure outweigh the convenience. Agencies that document a fallback process now, covering alternative contact routes and supplier-portal access, will spend the next outage working rather than improvising.

Microsoft has not yet given a firm restoration time for the affected services. Until it does, the trade's job is straightforward: audit the gaps, chase the deadlines, and pick up the phone.