A Failure at the Provider, a Problem for the Client

Is your organization prepared for this?

blog

Table of Contents

Introduction

When an external service stops working, we usually wait for the provider to fix the problem. From the perspective of an administrator or IT manager, though, that’s only half the trouble. The real questions begin when it turns out that the unavailability of one component triggers an avalanche of further complications inside the company.

On November 13, 2026, the Microsoft 365 and Exchange Online outage once again reminded us of a simple, though often ignored, law of engineering: a vendor outage becomes your problem. It’s worth looking at this without pointing fingers or dramatizing, but with full awareness of just how interconnected our IT environments really are.

What do cloud giant outages really expose?

Every major cloud service outage follows the same pattern: a sudden spike in support tickets, frustrated employees, and everyone waiting for the message that says “the issue has been resolved.”

We often focus on the simple fact of not having access to email or a network drive. In practice, however, the problem rarely ends with just the communication tool. A cloud system outage works like a line of dominoes – it topples pieces we don’t even think about on a daily basis.

Invisible dependencies in corporate IT

Imagine the main mail server or an authentication service at a third-party provider starts struggling. For an organization, this usually means much more than just missing new messages in the inbox:

  • No verification codes: Many internal and external systems use corporate email to send one-time passcodes (OTP).
  • Silent notifications: Monitoring systems, helpdesk platforms, or backup applications may stop sending error alerts.
  • Blocked business processes: Applications that appear to run locally can be tightly linked to cloud-based identity. If a user can’t log in to their base account, no other tool will work either.

MFA and Access Continuity

A great example of these dependencies is multi-factor authentication (MFA). Requiring MFA is now a security standard, but the devil is in the technical details.

It’s worth remembering that even government institutions have long pointed out the limitations of email as an authentication channel. If access codes are sent exclusively via email, and that email sits on a server that has just stopped responding, the administrator is cut off from their own emergency tools.

For this reason, the choice of login method matters not only for the level of security, but also for business continuity (disaster recovery). Applications that generate codes locally (TOTP) eliminate dependency on email delivery, but in turn require a plan in case a user loses their phone. There are no approaches that are 100% resilient to everything. There are only deliberately chosen trade-offs.

What is TOTP and how does it work?

TOTP (Time-Based One-Time Password) is a one-time code generated directly in an app on your phone, such as Google Authenticator or Microsoft Authenticator. It works in a very simple way. During setup, the phone and the system you want to log into receive a shared secret key. Thanks to this, both devices can independently calculate the same code, without it being sent via SMS or email. The code usually consists of 6 digits and changes every 30 seconds. After that time, a new one appears, and the previous one stops being accepted (with a small time tolerance in some systems).

It can be compared to two watches that are synchronized and show the same changing password every 30 seconds. You have one watch on your phone, and the other in the system you’re logging into.

Importantly, generating TOTP codes does not require an Internet connection on the phone. It is enough for its clock to be set correctly.

How can an organization prepare for a worst-case scenario?

Business continuity planning doesn’t have to mean creating lengthy, multi-volume procedures that no one ever reads. Instead, it’s worth starting with a few specific questions within your own team:

  • Do we know the actual dependencies? Do we know which internal systems will fail if the Internet, external DNS, or cloud provider services go down?
  • How do administrators log in during a crisis? Does access to key tools depend on the very channel that just stopped working?
  • Do we have an alternative communication channel? If email and the company messenger fail at the same time, how will you notify employees about the outage and next steps?
  • Have the procedures been tested? Theory verified on paper or in someone’s head often falls apart at the first real test.

Where do inventory and asset management fit into all this?

To effectively prepare for a failure, you first need to know exactly what assets the organization uses and how they are interconnected. This is where ITAM and infrastructure monitoring tools, such as eAuditor, come to the rescue.

These systems help maintain up-to-date insight into the IT environment: from hardware to software and services in use. While such an inventory won’t resolve issues on behalf of the cloud provider, it gives administrators a foundation for business continuity planning and quickly identifying what is actually running across the company and where it draws its resources from.

The same applies to the security mechanisms themselves. For example, eAuditor Cloud supports authentication both via codes sent by email and through authenticator apps (TOTP). This is a technical detail that shows security and flexibility of access must go hand in hand.

Quick Checklist: 5 Questions for Your IT Department

  1. Do we know which key business processes depend on third-party cloud providers?
  2. Do administrators have a secure, alternative authentication method in the event primary channels become unavailable?
  3. Does an email or cloud outage block our access to emergency and diagnostic systems?
  4. Do we have an independent communication channel with the team in the event of a sudden crisis?
  5. When was the last time we verified our contingency procedures for key service outages?

Read more about how technology supports access management in our article dedicated toMFA configuration in eAuditor Cloud.

2026-11-16T10:04:57+01:00