If your Friday morning involved refreshing Outlook, checking Teams and wondering whether Microsoft had finally given up, you weren’t alone.
A major Microsoft 365 outage affected organisations around the world last week, disrupting services including Outlook, Teams and Copilot. The problems lasted for around 18 hours before services began to recover on Friday, leaving businesses and public sector organisations looking for alternative ways to communicate and continue working.
The disruption offered a timely reminder of just how dependent modern organisations have become on cloud services. It also raised an important question: if one of the platforms your business relies on suddenly becomes unavailable, how prepared are you to keep operating?
Quick Summary
Friday’s Microsoft 365 outage disrupted everyday tools used by millions of people, forcing some organisations to fall back on phones and other alternative ways of working. While Microsoft confirmed the incident was caused by a technical issue rather than a cyber attack, the disruption highlights a broader lesson around resilience.
- Microsoft 365 services including Outlook, Teams and Copilot were affected by the outage.
- Organisations around the world experienced disruption, with communication and administrative processes particularly affected.
- Microsoft said it was not aware of any malicious activity linked to the incident.
- The outage highlights the importance of understanding which technologies your organisation depends on to operate.
- Business continuity plans should account for technical failures as well as cyber attacks and other major incidents.
- Regularly testing contingency and recovery plans can help teams respond more effectively when critical services become unavailable.
What Happened to Microsoft 365?
Problems with Microsoft’s services began on Thursday evening and continued into Friday, affecting users around the world.
Microsoft 365 applications including Outlook, Teams, Word, Excel and PowerPoint were affected, alongside services such as SharePoint, OneDrive and Copilot. Reports of problems were not consistent for every user, but the scale of the disruption quickly became apparent as organisations found themselves without access to some of the tools they rely on every day.
Microsoft later said a number of servers had become unexpectedly unavailable following problems during automated checks. The company confirmed that it had found no indication that the outage was connected to a cyber attack.
Services were gradually restored as Microsoft implemented fixes, with signs of recovery emerging on Friday.
A Reminder of How Much We Rely on Cloud Services
Cloud technology has transformed the way organisations operate.
Employees can collaborate from different locations, files can be accessed without relying on an office server and services can scale as businesses grow. Platforms such as Microsoft 365 have become central to everyday operations for organisations across almost every industry.
That convenience also creates dependencies.
Consider how many processes within your organisation rely on Outlook alone. Customer conversations, supplier requests, invoices, meeting invitations and internal communication are often tied to email. Add Teams, SharePoint, OneDrive and other cloud applications into the equation and the potential impact of an outage becomes much clearer.
When those services disappear unexpectedly, even temporarily, organisations can quickly find that familiar ways of working are no longer available.
Friday provided a very public example.
What Happens When Your Normal Tools Aren’t Available?
Some of the most interesting stories to come from the outage were the ways businesses adapted.
European exchange operator Euronext reportedly asked listed companies to contact its teams by phone while systems were affected. Insurance provider Aviva put alternative phone numbers in place and even used Bluetooth to transfer recordings while email was unavailable.
They may sound like unusually low-tech solutions for 2026, but they demonstrate an important principle of business continuity: organisations need another way to operate when their usual systems cannot be accessed.
The alternative does not always need to be technically sophisticated. What matters is that employees know what to do, which communication channels remain available and how critical processes can continue safely until normal services return.
Business Continuity Goes Beyond Cyber Attacks
Conversations around resilience frequently focus on ransomware, data breaches and other cyber threats. These remain serious risks, but they’re only part of the picture.
Microsoft stated that Friday’s disruption was caused by a technical issue and that there was no indication of malicious activity.
A service does not need to be compromised by an attacker to become unavailable.
Hardware failures, software problems, configuration changes, supplier outages, connectivity issues and human error can all disrupt business operations. Power failures, extreme weather and problems affecting physical locations can create similar challenges.
For businesses, the cause matters less in the first few minutes of an incident than the ability to respond.
Teams need to understand which services are critical, what happens if they become unavailable and which processes should be followed until systems are restored.
Do You Know What Your Business Depends On?
Most organisations could quickly name their largest IT platforms. Understanding the dependencies behind individual business processes requires a little more thought.
Imagine Outlook and Teams became unavailable tomorrow morning.
Could employees still contact customers?
Would your service desk remain accessible?
Could suppliers reach the right people?
Would employees know where to look for updates?
Could senior leadership communicate with the wider organisation?
Would core customer services continue operating?
The answers help identify where dependencies are concentrated and where contingency planning may need more attention.
This process should also extend further than Microsoft 365. Line-of-business applications, cloud hosting platforms, internet connectivity, telephony, identity services and third-party suppliers may all play a critical role in keeping an organisation operational.
Mapping those dependencies makes it easier to understand which failures would have the greatest impact and where additional resilience may be required.
Having a Business Continuity Plan Is Only the First Step
Most organisations understand the value of business continuity planning. The bigger question is whether the plan would actually work during a real incident.
A document written several years ago may reference employees who have since left, systems that have been replaced or communication channels that no longer exist.
Regular testing gives organisations an opportunity to find these gaps before an emergency does.
Testing could involve temporarily removing access to a particular system, running tabletop exercises with key stakeholders or simulating different outage scenarios. The aim is to understand how teams respond when the usual tools are unavailable.
Issues discovered during an exercise can then be addressed while there is still time to fix them.
Communication Matters During an Outage
Technical recovery is one part of incident response. Communication is another.
When employees cannot access the tools they normally use, uncertainty can spread quickly. People may repeatedly attempt to reconnect, contact IT individually or look for their own workarounds.
A clear communication process can reduce that confusion.
Organisations should establish alternative ways of reaching employees if primary communication platforms become unavailable. Depending on the business, this might include SMS notifications, phone trees, dedicated status pages or another approved communication platform.
Employees should also know where authoritative information will come from during an incident. That becomes particularly important when an outage affects email or collaboration platforms that would normally be used to issue updates.
Resilience Starts With Understanding Your Environment
Friday’s outage was outside the control of individual Microsoft 365 customers, but organisations can control how prepared they are for disruption.
That preparation begins with understanding the technology environment, identifying critical dependencies and considering what would happen if individual services became unavailable.
Managed IT and cloud specialists can help organisations review these dependencies, strengthen their Microsoft environment and identify areas where additional resilience or contingency planning may be required.
At Wanstor, we work with organisations to manage, optimise and secure their IT environments, helping businesses understand the technology they rely on and build an infrastructure that supports their wider operational needs.
The goal cannot be to guarantee that technology will never fail. Even global technology providers experience incidents. Instead, organisations should focus on reducing the impact when something does go wrong and ensuring that teams have a clear route forward.
What Should Businesses Take Away From Friday’s Microsoft Outage?
For many people, Friday’s disruption amounted to an inconvenient few hours without familiar tools. For organisations operating critical services or handling time-sensitive processes, the consequences can be much greater.
Cloud platforms have brought enormous benefits to modern workplaces, and the scale of Microsoft 365 means it will continue to sit at the centre of many organisations’ technology strategies.
Friday simply demonstrated why resilience needs to sit alongside that convenience.
Understanding your dependencies, establishing alternative processes and regularly testing business continuity plans can make the difference between a temporary technology problem and widespread operational disruption.
When the next major service outage happens, the most important question won’t be whether your organisation could have prevented it.
It will be whether you were prepared for it.
Frequently Asked Questions
What happened to Microsoft 365 on Friday?
Microsoft experienced a widespread service outage that affected users and organisations around the world. Services including Outlook, Teams, Copilot, SharePoint and OneDrive were among those affected, alongside other Microsoft 365 applications.
What caused the Microsoft 365 outage?
Microsoft said the outage was linked to a technical issue involving servers becoming unexpectedly unavailable during automated checks. The company implemented fixes as it worked to restore services.
Was the Microsoft outage caused by a cyber attack?
Microsoft said it had found no indication that malicious activity was responsible for the outage. The incident was attributed to a technical issue.
How long did the Microsoft outage last?
The disruption began on Thursday evening and continued into Friday, lasting around 18 hours before services began to recover. Restoration was carried out gradually as Microsoft worked to ensure services remained stable.
What is business continuity?
Business continuity refers to the processes and plans an organisation puts in place to maintain critical operations when a disruption occurs. This can include planning for cyber attacks, IT outages, connectivity failures, supplier disruption and other incidents that could affect normal operations.
How can businesses prepare for a Microsoft 365 outage?
Organisations should identify the Microsoft 365 services their critical processes depend on, establish alternative communication methods and document what employees should do if those services become unavailable. Business continuity and incident response plans should also be tested regularly so that teams know how to respond during a real outage.
Can Microsoft 365 outages be prevented?
Individual organisations cannot prevent an outage within Microsoft’s own infrastructure. They can, however, reduce the potential business impact through contingency planning, alternative communication channels, resilient IT architecture and regularly tested business continuity processes.