Would on-premises email have kept businesses working?

Microsoft 365 Outage and On-Premises Email: Would Moving Back Actually Help?

Microsoft 365 Outage: Would Moving Email Back On-Premises Have Helped?

By Matt Rose

On Thursday, I joked on LinkedIn that if you were waiting on an email from me, I was happy to let Microsoft take the blame.

By Friday, Microsoft 365 was still recovering, and I joined Hayden Wiggs on FOX 35 Orlando to discuss what the outage meant for businesses.

You can also watch the full FOX 35 interview on YouTube.

As people waited for their inboxes to come back, two suggestions appeared almost immediately:

Move to Google.

Bring email back on-premises.

Both sound reasonable when Microsoft 365 has been down for hours. Neither is as simple as it sounds.

The short answer

An on-premises email server might have kept your company's own email available during this particular Microsoft outage.

It would not have brought Microsoft 365 back online for your customers, vendors, banks or other businesses you needed to communicate with.

It also would have made your company responsible for maintaining, securing, backing up and recovering that email system.

You may solve one dependency while creating several new ones.

What caused the Microsoft 365 outage?

The outage began Thursday, November 12, and primarily affected Exchange Online, the service behind Outlook email and calendars.

Because so many Microsoft 365 services are connected, the impact extended beyond email. Some calendar functions, meeting scheduling, Copilot features and other Microsoft tools were also affected.

Microsoft later said the outage was caused by a technical issue introduced during an earlier network capacity upgrade that surfaced after a more recent network change.

The company also confirmed that the outage was not caused by a cyberattack, artificial intelligence or AI agents.

That clarification matters. During the outage, there was plenty of speculation about cybersecurity and AI. Once Microsoft provided more information, the explanation became much less dramatic: a change inside an extremely complicated system caused a much larger problem than expected.

Would on-premises email have kept businesses working?

For some businesses, it would have helped.

If your company operated its own email server and everything inside your environment was functioning properly, employees may have retained access to their inboxes. Internal email between coworkers could also have continued.

But having access to email does not mean business continues normally.

If the customer who needs to approve an order uses Microsoft 365, you are still waiting.

If the vendor confirming a shipment cannot access Outlook, you are still waiting.

If the bank, insurance company or government agency you need to reach is affected, you are still waiting.

That was one of my main points during the FOX 35 interview:

"Even if you had an on-premise server, that's great. You had full access to it, but you were talking to almost nobody."

Your company does not operate in isolation. Business continuity depends on the systems used by the people and organizations around you too.

On-premises email creates different risks

Bringing email back inside the business gives you more control.

It also means someone must take responsibility for:

  • Maintaining the server
  • Installing security updates
  • Monitoring the system
  • Protecting it from cyberattacks
  • Managing storage
  • Backing up the data
  • Testing recovery
  • Keeping it available during a power, internet or hardware failure
  • Responding when something breaks after hours

A single email server sitting in an office may avoid a Microsoft outage. It can also become its own single point of failure.

Creating an on-premises system with the kind of redundancy businesses expect from a major cloud provider requires additional equipment, backup power, multiple internet connections, off-site protection and people who know how to maintain it.

That can make sense for organizations with specific regulatory, operational or data-control requirements.

For many small and midsize businesses, it would add significant cost and responsibility without guaranteeing that the business could continue operating during a widespread outage.

Would moving to Google Workspace solve it?

Moving to Google Workspace would have kept a business outside this specific Microsoft outage.

Its own email may have continued working.

But the customers and vendors using Microsoft 365 would still have been unavailable. The business would also be replacing its dependency on Microsoft with a dependency on Google.

Google has outages too. So does Amazon Web Services. So does Cloudflare. So does nearly every major technology provider.

Moving platforms may make sense because of licensing, collaboration tools, usability or a company's long-term technology strategy.

Making that decision because of one bad day is different.

A move affects employee training, security settings, applications, file storage, retention policies and the way people work. It should be based on the needs of the business, not the frustration of repeatedly refreshing Outlook.

Backup and business continuity are not the same thing

The outage also restarted the conversation about Microsoft 365 backups.

A backup protects data. It can help recover an email, file or mailbox after accidental deletion, corruption, ransomware or another destructive event.

A backup does not normally give employees a second working inbox while Microsoft 365 is unavailable.

That is the difference between data recovery and business continuity.

Businesses should understand:

  • What Microsoft 365 information is protected
  • How long that information is retained
  • How quickly it can be restored
  • Who is responsible for starting a recovery
  • Whether the recovery process has ever been tested

Having Microsoft 365 does not automatically answer those questions. Having a backup product does not automatically answer them either.

Your IT partner should be able to explain exactly what is protected and what would happen if information needed to be recovered.

What should businesses do after the outage?

The best response is not immediately buying another platform.

Start by identifying what actually stopped inside the business.

Which work could not continue?

Look at orders, approvals, customer communication, scheduling, payments and any other work that depended on Microsoft 365.

Who were you waiting for?

Your own systems may have been working while customers, vendors or other outside organizations were unavailable.

Those dependencies should be part of the plan.

Is there another way to communicate?

Employees should know what approved communication method to use if email is unavailable.

That alternate method should not require the same Microsoft account or service that may be down.

Can employees reach important contacts?

Critical customer, vendor and employee contact information should be available through a secure method that does not depend entirely on email.

Do you understand your backup?

Know what can be restored, how long it would take and who is responsible for making it happen.

Has the fallback plan been tested?

A backup plan that no one can find, access or use during an outage is not much of a plan.

Testing does not need to become a major company project. Even walking through one business day without email can reveal where the real problems are.

The bigger lesson from the Microsoft outage

There is no perfect platform.

Microsoft 365 is complicated. Google Workspace is complicated. Running email inside your own business is complicated.

Every option involves risk.

The important question is not whether cloud or on-premises technology is always better. The question is what your business needs to keep operating, how much downtime it can accept and which protections are worth the cost.

For many small and midsize businesses, Microsoft 365 will still provide a better balance of availability, security and cost than running email internally.

That does not mean businesses should simply hope the next outage is shorter.

A good IT partner should help you understand your dependencies, protect your information and create a practical plan for when an important provider becomes unavailable.

You should not have to become the person managing the outage, chasing your IT company for answers or wondering whether anyone has a plan.

If the Microsoft 365 outage left you wondering what would happen to your business during the next disruption, talk with Tech Rage IT. We can help you understand what is protected, what is dependent on Microsoft 365 and what a practical continuity plan should look like.

Frequently asked questions

Would on-premises Exchange have kept working during the Microsoft 365 outage?

It may have kept internal email available if the company's servers, network, power and other systems remained healthy. Communication with customers or vendors affected by the Microsoft 365 outage could still have been delayed.

Is on-premises email more reliable than Microsoft 365?

Not automatically. A properly designed on-premises system can be highly reliable, but a single server in one office creates its own risks. Reliability depends on redundancy, maintenance, security and recovery planning.

Would Google Workspace have prevented the outage?

Google Workspace would have avoided this particular Exchange Online failure for the business using it. It would not have restored service for customers, vendors or partners using Microsoft 365.

Does Microsoft 365 include backup?

Microsoft 365 includes resiliency, retention and recovery features. Microsoft and third-party providers also offer additional backup services. Businesses should verify what they have licensed, what is protected and how restoration works.

What should a business do after a Microsoft 365 outage?

Identify which work stopped, review outside dependencies, confirm backup coverage, establish another way to communicate and test the fallback plan before the next outage.