What a Microsoft 365 Outage Means for Your NetSuite ERP
On 12 and 13 November 2026, Microsoft 365 was down for about 24 hours. Outlook could not reach mailboxes, email delivery stalled, and services built on Exchange Online, including parts of Teams, SharePoint and Copilot, failed with it.
NetSuite stayed online the whole time. The ERP outage impact came from everything around it: the inboxes, approvals and integrations that connect NetSuite to Microsoft 365. This guide shows where NetSuite depends on Microsoft 365, what to check now, and how to keep NetSuite email notifications and workflows moving during the next outage.
What Happened to Microsoft 365
Microsoft’s preliminary post-incident report traces the outage to a defect in a Windows fix deployed to its networking gateway servers in July 2026. On 12 November, extra traffic and reduced capacity on those gateways triggered the defect, and at the lowest point more than 80% of the gateway servers were unresponsive. Customer impact ran from 4:20 PM UTC on 12 November to 4:10 PM UTC on 13 November.
Our live coverage of the Microsoft 365 outage has the full timeline of Microsoft’s updates.
NetSuite Email Notifications Kept Sending
NetSuite sends email from its own mail servers, not through your Microsoft 365 tenant. Invoices, statements, purchase orders and other NetSuite email notifications left NetSuite on schedule throughout the outage. The problems sat on the receiving end, inside Microsoft 365.
Where the Outage Reached NetSuite
1. Approval Requests Nobody Saw
A NetSuite workflow email asking a manager to approve a purchase order, vendor bill or expense report lands in that manager’s Outlook inbox. With Outlook down, the request sat unread and the transaction sat pending. Approvals that depend on email stopped for a full day.
2. Customer and Vendor Replies
When a customer or vendor replies to NetSuite email notifications, such as an invoice or a purchase order, the reply goes to your company address, and that address lives in Microsoft 365. Payment questions, disputes and order confirmations arrived late, after Exchange Online recovered.
3. Email Capture and Case Creation
Many companies forward a shared inbox, such as support@ or ap@, to a NetSuite email capture address that creates support cases or vendor bills. When that forwarding runs through Microsoft 365, nothing reached NetSuite during the outage, so no cases or bills were created.
4. NetSuite Connector for Outlook
The NetSuite Connector for Outlook syncs emails and calendar events to customer, contact and opportunity records. With Outlook unavailable, sales teams synced nothing, and those conversations are missing from NetSuite until someone syncs them.
5. Integrations That Read Mailboxes
Microsoft reported that Microsoft Graph requests for Exchange data, including mail, calendars and contacts, timed out during the outage. Any integration that reads an inbox through Microsoft Graph to create NetSuite records, such as an invoice-scanning flow, failed for the duration.
6. NetSuite Single Sign-On
If your team signs in to NetSuite through Microsoft Entra ID, NetSuite access depends on Microsoft’s identity services. Entra ID was not on Microsoft’s list of affected services this time, but an identity outage locks out every user on a SAML single sign-on role. NetSuite never lets the Administrator role sign in through SAML, so administrators keep direct access to fix problems.
What to Check in NetSuite Now
Clear the NetSuite approvals backlog: Find purchase orders, vendor bills, expense reports and journal entries created between 12 and 14 November that are still pending approval and route them to approvers.
Reconcile captured email: Compare the shared inbox with the cases and vendor bills created in NetSuite for the same dates and enter anything missing.
Re-run failed integrations: Check the error log of every integration that touches Microsoft 365 and reprocess the failed records.
Sync sales conversations: Ask sales teams to sync the emails and meetings from the outage days to their NetSuite records.
Follow up on late replies: Answer payment questions and disputes that arrived late before they turned into overdue invoices.
How to Reduce ERP Outage Impact Next Time
Approve inside NetSuite, not only by email: Add approval reminders to each approver NetSuite dashboard, so pending transactions are visible without Outlook.
Send vendor invoices straight to NetSuite: Give vendors the NetSuite email capture address directly, so bills skip the Microsoft 365 mailbox.
Alert integration failures outside email: Send failure alerts to a channel that does not run on Microsoft 365, such as SMS or a separate chat tool.
Keep administrator access ready: Confirm that at least two people hold the Administrator role and can sign in directly.
Map every dependency: List each place NetSuite sends to, receives or signs through Microsoft 365, and give each one an owner and a fallback.
Our NetSuite integration services team builds these fallbacks into existing integrations, and our NetSuite managed services team monitors workflows and integrations, so failures surface in minutes, not days. Learn more about how we support NetSuite end to end.
Conclusion
NetSuite stayed up during the Microsoft 365 outage, and NetSuite email notifications kept sending, but the approvals, replies and integrations around them stopped. Finding those gaps now costs far less than finding them during the next outage. Talk to our NetSuite team and we will map every Microsoft 365 dependency in your account, with a fallback for each.
