Microsoft Teams desktop client delays and Mac call‑joining problems, what you need to know

When a meeting is scheduled, many organisations count on the Teams desktop client to launch instantly and let participants join with a click. Over the past few days Microsoft has confirmed two separate issues that can break that expectation, one affecting Windows users and another hitting macOS users. The problems are recognised as known issues and are being investigated, but they can still disrupt daily collaboration if you are not prepared.

Why the issue matters for your business

• Productivity loss, a two‑minute start‑up delay may seem small, but in a busy office it can cascade into missed calls and delayed decisions.
• Customer‑facing impact, support teams that rely on Teams for live chat or video calls may appear unresponsive.
• Device diversity, the same organisation may have Windows desktops and Mac laptops, meaning the two issues can hit different parts of the same workforce.

What is happening on Windows?

Microsoft says the delay is not tied to a specific version of the client; it can affect any Windows installation that runs the current Teams desktop build. The company is analysing service logs and telemetry data, the automated records that Teams sends back to Microsoft about performance, and has reached out to a handful of affected users to help pinpoint the root cause.

What is happening on macOS?

Some Mac users report that the Join call button is disabled or that meetings fail to start altogether. The issue was initially blamed on a recent code change, but further review suggests the change may not be the cause. Microsoft is therefore reassessing the underlying trigger while keeping the problem classed as a known issue.

What caused the recent crashes after August security updates?

In August 2026 Microsoft released a set of Windows security updates (the regular "Patch Tuesday" roll‑out). A bug linked to those updates caused Teams and the new Outlook client to crash or fail to launch for a subset of users. Microsoft has confirmed the bug and has since issued a fix.

Photo by Tiger Lily on Pexels

What has Microsoft fixed before?

• April 2026, Teams Free chat and call outage, a separate problem that blocked free‑tier users from chatting or calling was resolved after a few days.
• August 2026, Crash after security updates, the bug described above has been patched.

These prior resolutions show that Microsoft can move from identification to remediation within weeks, but they also illustrate how quickly a new update can introduce unexpected side‑effects.

What is Microsoft doing now?

• Log and telemetry analysis, engineers are combing through the data to find patterns that distinguish affected from unaffected machines.
• User outreach, a small group of customers have been contacted for deeper diagnostics.
• Root‑cause reassessment for macOS, the team is re‑examining the code‑change hypothesis and will publish an update when the cause is clear.

No public timeline has been given for a permanent fix, so the safest approach is to adopt the work‑arounds while monitoring Microsoft’s service‑health dashboard for updates.

What should you do today?

1. Switch to the web or mobile client for any urgent meetings. The web version runs in a browser and is not affected by the desktop start‑up delay.
2. Inform affected users, send a quick internal note explaining the symptom, the work‑around, and that Microsoft is investigating.
3. Monitor the service‑health portal, Microsoft posts status alerts at admin.cloud.microsoft under the Teams service.
4. Test critical workflows, if your support desk relies on Teams for ticket handling, run a few test calls to confirm the web client works as expected.
5. Document any patterns, note operating‑system version, device model, or network configuration that seems common among the affected users. This information can be valuable if Microsoft requests further details.

Photo by Anna Tarazevich on Pexels

By taking these steps you can keep collaboration flowing while the vendor works on a permanent resolution.

Terms used in this article

• Telemetry, automated data that software sends back to its maker about usage and performance.
• Service logs, records kept by a service that detail events, errors and other operational information.
• Code change, a modification to the software’s source code that is released as part of an update.
• Patch Tuesday, the second Tuesday of each month when Microsoft releases security updates for Windows.
• Work‑around, a temporary method to avoid or mitigate a problem until a fix is available.

This article reflects Stratum’s independent analysis of publicly reported Microsoft Teams issues. Stratum is a Microsoft partner, and the relationship is disclosed here for transparency.