The tolerated pain
A business can have reliable connectivity for months and still have a fragile design if one circuit, provider path or edge device is the only route to critical work.
Operational consequence
During an outage, employees may remain present but unable to reach cloud systems, process transactions, communicate normally or serve customers. Recovery then depends on the provider rather than an operating choice.
How it becomes money
downtime exposure per hour = idle labour + delayed or lost contribution + recovery effort + customer/service impact
Use observed transaction and staffing data. Not every delayed sale is lost revenue, so scenario assumptions should distinguish delayed, recoverable and permanently lost activity.
Microsoft's continuity guidance for data gateways illustrates the broader principle: where a dependency can fail, high-availability or secondary capacity has to be designed deliberately rather than assumed.
Resolution
- Identify processes that genuinely require live connectivity.
- Calculate realistic outage exposure.
- Map provider, circuit, power and equipment single points of failure.
- Design an independent fallback where justified.
- Test failover under operating conditions.
- Document degraded-mode procedures.
Bottom line
Redundancy is not automatically worth buying. It becomes rational when the cost of an independent fallback is lower than the risk-adjusted interruption the business is already carrying.
Source
Microsoft Learn: Business continuity and disaster recovery guidance.