Microsoft Teams Unable to Make or Receive Calls Explained
If you searched for "Microsoft Teams unable to make or receive calls," the real picture is narrower than that phrase suggests. Microsoft reported two separate problems earlier this month, not one sweeping outage: some Windows users couldn't get the Teams desktop client to open, and separately, some Mac users were blocked from joining calls and meetings. Both surfaced within days of each other, according to incident reports Microsoft shared with BleepingComputer earlier this month.
This isn't a case of Teams calls not working across the board. The supplied incident descriptions do not establish a Teams-wide outage; Microsoft's notices don't say how many users or app versions were affected, and the two problems carry different incident numbers, symptoms, and guidance. What follows breaks down each Microsoft Teams calling issue by platform, what Microsoft said to do about it, and where the reporting leaves gaps.
If Teams won't open on Windows
Microsoft logged the Windows problem as incident TM1466820 at 4:45 p.m. EDT on a Thursday earlier this month, according to BleepingComputer.
"Specifically, when first opening Microsoft Teams on Windows devices, some users may be initially unable to load the client or may encounter loading delays of up to two minutes," Microsoft said in an incident report, according to BleepingComputer.
That's launch behavior, not a calling-feature bug. The quoted notice addresses opening the desktop app on Windows and does not mention call quality, audio, or meeting behavior once the client is running.
Microsoft said it was still analyzing service logs and telemetry, and had reached out directly to some affected users while working to identify the cause, according to BleepingComputer.
Microsoft's stated workaround for TM1466820 was Teams on the web or the Teams mobile app: "While we're focused on remediation, affected users may be able to avoid impact by using Microsoft Teams on the web or alternative Teams access methods such as the Teams mobile app," according to BleepingComputer. That's a hedged fix, "may be able to," not a guarantee, so treat it as a fallback Microsoft recommended rather than a confirmed cure.
Microsoft Teams cannot join calls or meetings on Mac: what Microsoft reported
The Mac issue is a separate incident, tracked as TM1466659 and confirmed at 8:32 a.m. EDT the following Sunday, according to BleepingComputer. Microsoft's wording is specific: "Users may be unable to join calls or meetings in Microsoft Teams for Mac," according to BleepingComputer.
That's narrower than "Teams calls not working" might imply. The notice describes joining calls or meetings specifically and doesn't establish whether the problem also touches placing outbound calls, receiving inbound calls outside scheduled meetings, or launching the Mac app in general. A Mac that opens Teams normally but fails specifically when joining a call is consistent with the description Microsoft published.
On root cause, Microsoft said it was "reassessing our root cause understanding and reviewing service logs to isolate the source of impact, so that we can determine our next steps regarding impact remediation," according to BleepingComputer. That's a statement about where Microsoft's investigation stood at the time, not evidence of what's actually causing the failure.
The supplied report does not identify a Mac-specific workaround. For an urgent meeting, testing another device or Teams for web is a reasonable step, but the report does not establish that either option bypasses this particular problem.
Which symptom matches which incident
- Windows desktop app won't open, or takes up to two minutes to load: matches the description Microsoft gave for TM1466820, with the web or mobile workaround Microsoft recommended.
- Mac app opens normally but fails specifically when joining a call or meeting: matches the wording Microsoft used for TM1466659; no confirmed workaround in the supplied report.
- Ordinary outbound or inbound calling outside of joining a scheduled meeting: not addressed by the supplied incident descriptions.
What the report doesn't tell you
Both incident notices describe impact on "some users," language that stops short of confirming a failure across all users. The BleepingComputer report did not identify an affected app version, an affected Windows or macOS build, or a resolution timeline for either issue. That's a gap in what was publicly reported as of earlier this month, not proof that a fix wasn't already underway.
For comparison, when Microsoft resolved a Teams Android issue that blocked some users from making outbound calls over the phone network, the final report named the exact client version involved, described the root cause as a code change that mishandled dialed-number formatting, and included a completed fix timestamp, according to NHSmail Support, citing a 2023 Microsoft service alert. Neither the Windows nor the Mac report reviewed here had reached that level of detail as of the September 4 snapshot Microsoft shared with BleepingComputer.
The report also mentioned two other Teams problems from earlier this year: an April fix for some Microsoft Teams Free users who couldn't chat or call others, and a bug causing Teams and New Outlook crashes after certain Windows security updates released since the August 2026 Patch Tuesday, according to BleepingComputer. Neither was identified as the cause of the Windows or Mac incidents described above; both are separate from these two incidents in scope and timing.
What to do now
Match the symptom guide above to what's actually happening on your device. If Teams won't open on Windows, or takes an unusually long time to load, Microsoft's own recommendation was switching to Teams on the web or the mobile app. If a Mac is failing specifically when joining a call or meeting, testing another device or Teams for web is worth trying, though the September 4 report did not identify a confirmed fix for TM1466659.
The reporting behind this article is a snapshot from earlier this month, not a live status page. For a current status, check Microsoft's official service-status channels or contact your organization's administrator before treating either incident as still active.
Comments
Be the first, drop a comment!