(807) 700-7111 Free Assessment
← Back to blog

DVGVoIP Business Continuity

Will your phones ring when Microsoft 365 goes down?

7 min read
On this page

On 12 November 2026, a Microsoft 365 incident took Outlook and Exchange Online out from under a great many businesses and ran into the following day. The question we fielded most that week was not about email. It was simpler: if that happens again, will the phones still ring?

It is a fair question and it has a real answer, but the answer depends on how your phone system is put together. Below is what broke, what the vendors’ own documentation says depends on what, and the short list of things worth setting up before the next one.

What Microsoft said was affected

The umbrella incident, MO1550821, tracked the services that depend on Exchange Online; a companion incident, EX1550543, covered Exchange Online mailbox connectivity itself. Microsoft’s service health updates listed Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365 and Microsoft Defender XDR among the potentially affected services, and attributed the trouble to a process on the affected servers responsible for establishing secure connections becoming overwhelmed, so the servers stopped processing requests. Microsoft also said it had no evidence of malicious activity.

For phones, the important line in those updates was the split. Microsoft reported that core messaging and online meetings remained largely functional — “Most of the core functionality including joining calls, meetings, group chats, and channel messages are not impacted” — while calendar-related failures with scheduling, invites, viewing and meeting edits were part of the impact, along with the creation of live or virtual events.

That is not a small detail. It is the shape of the whole problem: calling held up, and the features sitting on top of Exchange did not.

Where Teams Phone touches Exchange Online

If your calling runs on Teams, the dependency is documented plainly by Microsoft. From Set up Cloud Voicemail on Microsoft Learn:

“Voicemail messages generated by Cloud Voicemail are delivered to and stored in the user’s Exchange mailbox, either in Exchange Online or in Exchange Server. There’s no specific or additional storage for voicemail.”

The same page notes that the clients people use to reach voicemail — Outlook, Teams, Skype for Business — “do so through the Exchange mailbox and the APIs provided,” that delivery happens over SMTP from noreply@skype.voicemail.microsoft.com, and that Cloud Voicemail “doesn’t support third-party email systems.”

So a Teams Phone deployment keeps taking calls while Exchange is unwell, and that is genuinely good engineering on Microsoft’s part. What you may not get is the voicemail that lands behind it, the calendar that drives your availability, and the meeting invites your day was built around. If you want the longer comparison, we wrote one: 3CX vs Microsoft Teams Phone.

Where a hosted 3CX system touches Microsoft 365

A hosted 3CX system is built the other way around. Calls arrive on a SIP trunk, hit the 3CX server, and ring your deskphones and apps. Microsoft 365 is not in that path — which is also why a 3CX system has its own Microsoft 365 dependencies to know about, because they are real, just elsewhere.

3CX’s own Microsoft 365 integration documentation lists exactly what the integration does:

  • Sync user accounts from Microsoft 365 — one way, M365 to 3CX, running nightly, up to 650 users
  • Microsoft single sign-on so people log in to the 3CX Web Client with their Microsoft account
  • Contact sync from personal and shared mailboxes into the 3CX phonebooks, one way
  • Presence sync between 3CX and Microsoft Teams, in either or both directions
  • Sending 3CX’s email notifications through your M365 account

Read that list as a list of what you could lose. User sync is nightly, so a day without it changes nothing operationally. Presence may go stale. Single sign-on is the one to think about: if Microsoft sign-in is impaired, staff who log in to the web client with their Microsoft credentials feel it — while a registered deskphone and the trunk behind it are not in that conversation at all. And if you have 3CX set to send its email notifications via M365, those notices queue behind your mail platform like everything else. Note too that 3CX states the integration requires Microsoft 365 accounts with an Exchange subscription plan.

None of this is an argument that one platform is careless and the other is bulletproof. It is an argument for knowing where each feature lives.

Five things worth setting up before the next outage

1. Set your forwarding rules now, not during the incident. 3CX’s call forwarding settings let each extension decide where calls go per status, including to a colleague’s extension, to a queue or ring group, to an external number, or to “My mobile” — with a rebound option that announces the call so you can accept or reject it. There is also a Busy or Not Registered rule, which is the one that matters when a deskphone cannot reach the server, and an “Also ring my mobile” checkbox. Decide these in a calm meeting and they work automatically at 2 p.m. on a bad Thursday.

2. Get the mobile app on phones before you need it. An app that is already installed and logged in is a working extension on cellular data when the office network is the problem. See apps and features.

3. Have a second path to the internet. For most Northern Ontario sites this is a cellular backup on the router, and for multi-site operations it is worth planning per building — see deployment options. Our post on whether your internet is ready for VoIP covers what to measure on each connection.

4. Know where the status pages are. Microsoft publishes tenant-specific detail in the Microsoft 365 admin center under Health > Service health, and documents a separate service status page for when you cannot sign in to the admin center. You can also subscribe up to two addresses to email notifications per admin, or use the Microsoft 365 Admin app for push alerts. Do the same for every provider you depend on, including us.

5. Keep your 911 information current regardless. Emergency calling has its own rules and its own addressing, and an outage is the worst time to discover a stale service address. See 911 information.

If you are not sure which of your phone features depend on Microsoft 365, that is a twenty-minute conversation and a good use of a free assessment. Call (807) 700-7111, or open a support ticket by emailing support@dvgvoip.com before calling — this helps us resolve your issue faster.

FAQ

Does a Microsoft 365 outage stop my phones from ringing?

It depends where your calls are routed. During the November 2026 incident Microsoft reported that core Teams calling, meetings and chat were largely unaffected, while features depending on Exchange Online failed. On a hosted 3CX system, calls travel over your SIP trunk to the 3CX server, so Microsoft 365 is not in the call path at all.

Why does Teams voicemail stop working when Exchange Online does?

Because that is where it lives. Microsoft Learn states that Cloud Voicemail messages are delivered to and stored in the user’s Exchange mailbox, with no separate voicemail storage, and that clients reach them through the mailbox and its APIs.

What does hosted 3CX actually use Microsoft 365 for?

Per 3CX’s documentation: nightly one-way user sync, Microsoft single sign-on for the web client, one-way contact sync, presence sync with Teams, and optionally sending 3CX’s email notifications through your M365 account. Call routing is not on that list.

What is the single most useful thing to set up in advance?

Forwarding rules, especially the “Busy or Not Registered” rule and ringing a mobile. They are configured once per extension and they fire without anyone having to think about it during an incident.

Sources, verified 16 November 2026: Microsoft Learn, Set up Cloud Voicemail and How to check Microsoft 365 service health; 3CX, Microsoft 365 Integration and Call Forwarding; Microsoft Service Health updates for MO1550821 and EX1550543 as reproduced by ENow Software and Is It Up Or Down. Not a contract.

Ask AI

Accessibility