The Outage Was Not the Failure. The Missing Architecture Was.

What the Microsoft 365 collapse really exposed, and why change without an as-is state, a desired state, and a change kit is running blind

David Linthicum’s InfoWorld column, Microsoft’s outage should terrify every enterprise, makes the right call: the November 2026 Microsoft 365 failure was an architecture failure, not a technology hiccup. This article takes his argument one step further. The deeper problem is not bad architecture. It is the absence of architecture, hidden behind tools, diagrams, dashboards, reference models, and post-incident rituals that look like architecture but are not.

Every change to an enterprise is an architectural act. A network capacity upgrade, a configuration push, a new SaaS subscription, a vendor swap, and an AI rollout all change the structure of the enterprise. Changing structure responsibly requires three things:

  • An as-is state. A current description of what the enterprise actually is, including the things it depends on that it does not own.
  • A desired state. A description of what the enterprise must become, expressed as measurable goals rather than slogans.
  • A change kit. The explicit, governed means of moving from the as-is state to the desired state: the gaps, the initiatives, the sequence, the roles, the decisions, the containment limits, and the acceptance criteria.

Remove any one of the three and the enterprise is running blind. The Microsoft outage, the 2024 CrowdStrike update failure, and the 2025 Amazon Web Services disruption all show the same pattern: a change entered a system whose dependencies were not fully understood, with no agreed boundary on how far a failure could travel. The businesses downstream discovered their architecture by watching it fail.

The Enterprise Architecture Center Of Excellence addresses this directly. The EACOE Enterprise Architecture Methodology, built on the Enterprise Framework™, produces human-consumable as-is and desired-state architecture, organizes change into Business Initiatives with outcome-driven roadmaps, and governs every change through decision rights and traceability. That is real architecture. Anything less is a guess with a diagram attached.

 
Categories
 
 
Next
Next

AI Cannot Govern What No One Has Defined: Why AI-Ready Data Must Come Before AI-Enabled Data Management