By: Marc Schwartz, President of Ozone IT Services
On November 12, 2026, a failure at Microsoft left people around the world unable to reach their email. According to Al Jazeera’s reporting, Outlook was hit hardest, Teams and Copilot were disrupted, and the problems spread to more than 70 countries. Wikipedia’s summary of the incident describes most Microsoft 365 services as affected and puts full restoration on the morning of November 14. The Anderson Economic Group estimated lost productivity at about $7 billion.
Microsoft said it saw no sign of a cyberattack, and it pointed to a network configuration change that overloaded servers. Neither report mentions lost data. Microsoft has not yet published a final root-cause review, so details may change.
For manufacturers, the lesson isn’t about Microsoft. Every company depends on a vendor that can fail. The real question is whether your business keeps moving when one does.
An Outage Is Not A Data Loss Event
Many leaders hear “outage” and think “backup.” That’s understandable, and it’s only half right.
- Backups protect your data. They matter when information is deleted, corrupted, or encrypted by ransomware. Immutable, tested backups are still one of the most important foundations in IT.
- Continuity planning protects your ability to work. It matters when the data is fine but the systems that deliver it are unavailable.
In this outage, the data was reported intact. A backup could not have brought back email, Teams, or a calendar while the service was down. What would have helped is a plan for how people communicate, approve orders, talk to suppliers, and keep the plant running in the meantime.
Why Manufacturers Feel It More
In an office, an outage means frustrating hours. In a plant, it can mean:
- Orders and approvals stalled. Purchase orders, quotes, and change requests often travel by email.
- Supplier and carrier coordination breaks down. A late-arriving message can mean a missed truck.
- Shift handoffs lose information. Supervisors rely on messages, shared files, and schedules.
- Quality and compliance records are delayed. Customers and auditors still expect documentation on time.
- Customer commitments slip. Delivery promises don’t pause because a vendor’s server did.
None of this requires a cyberattack. It only requires a dependency nobody planned around.
Practical Business Continuity Planning Tips
- Map your dependencies.
List the systems your operation can’t run without, then ask what each one depends on. Email, identity sign-in, file storage, ERP, scheduling and EDI often share more connections than anyone realizes. If a single vendor appears in many places, that’s a risk to plan for.
- Decide how much downtime each process can tolerate.
Not every system needs the same protection. Set two numbers for each critical process: how long you can be without it (recovery time) and how much recent work you can afford to lose (recovery point). Spend more where the answers are short.
- Keep an out-of-band way to communicate.
If the tool you use to announce a problem is the one that’s down, you have a gap. Agree in advance on a backup: a group text or phone tree, a second messaging tool, or a status line employees can call. Keep an up-to-date contact list somewhere that doesn’t depend on your email.
- Plan for email continuity.
Email is the most common single point of failure. Options include a continuity service that queues and delivers mail, or gives users temporary access, when your main service is unavailable. At a minimum, make sure key people can reach customers, suppliers and carriers another way.
- Enable offline access on workstations.
Small settings make a real difference:
- Run Outlook in cached mode so people can still read and draft messages. Reports from the November outage noted that desktop Outlook could still show email that had already downloaded.
- Sync critical folders to the device so important files are available without a connection.
- Keep local installs of the applications people use every day.
- Keep production separate from office cloud services.
Your ERP, scheduling and shop-floor systems should keep working when office applications don’t. Review how operational technology connects to your business network and identity systems, and make sure routine production doesn’t depend on a cloud service being reachable. - Build paper and manual fallbacks.
Printed work instructions, a manual order form, a downtime checklist and a phone list of key customers, suppliers and carriers cost almost nothing. They are what a supervisor needs at 6 a.m. when the screens don’t load.
- Set up independent status monitoring
Don’t rely on the affected service to tell you it’s affected. Subscribe to vendor status alerts through a separate channel and agree who decides when to declare an incident and notify the team.
- Create break-glass access
Keep emergency administrator accounts, stored securely and tested regularly, so your IT team can still manage the environment when normal sign-in paths are disrupted.
- Write the plan, assign owners, and test it
A plan nobody has rehearsed is a hope. Name an owner for each step, keep the document where it can be found offline, and run a tabletop exercise at least once a year. Update it whenever you add a major system, supplier or site.
Don’t Swing Too Far the Other Way
An outage can tempt companies to buy a second system for everything. That’s expensive and rarely necessary. A fit-for-purpose approach spends the most on what would hurt most, accepts reasonable risk elsewhere, and documents the decision. Balancing a budget doesn’t mean taking an unplanned risk, and “secure enough” is a red flag when nobody has actually tested what happens next.
A Quick Business Continuity Check for Executives
Bring these questions to your next leadership or budget meeting:
- Which three systems would stop shipments if they were unavailable for a day?
- If email is down, how do we reach customers, suppliers and carriers?
- Can employees work offline on their devices for several hours?
- Does the shop floor keep running if office cloud services don’t?
- When did we last test our downtime plan, and who owns it?
- Are our backups immutable, and have we timed a restore?
- Who is watching our systems overnight and on holidays?
If you can’t answer most of these confidently, that’s a useful finding, and it’s cheaper to learn now than during an incident.
Where to Start
Ozone IT Services works with U.S. manufacturers as an extension of their IT teams, helping them find gaps and build practical, budget-conscious continuity, backup and security plans. A short conversation is often enough to identify the biggest gaps.
Ready to check your continuity plan? Contact Ozone IT Services at 978-807-6464 or click below to schedule a conversation.
Ozone IT Services partners with manufacturing and mid-size organizations across the U.S. to build the secure, well-supported IT foundation company needs while acting as an integrated extension of internal IT teams.