Microsoft Teams’ pre-join mic and speaker test: a small fix for the most common Teams complaint
Anyone who’s ever joined a Teams call and spent the first two minutes asking “can you hear me?” will recognise the problem this fixes.
Teams is adding a proper mic and speaker test to the pre-join screen, so people can confirm their audio works before they’re actually in the meeting, rather than discovering a problem once everyone else is already waiting.
What’s changing
This one has a more complicated timeline than most, worth reading properly rather than skimming.
Targeted release begins in early May 2026, completing by mid-May. General availability for commercial tenants worldwide begins mid-May and is now expected to complete by late June 2026, revised from an original late-May estimate. GCC and GCC High now begin in late June, pushed back from an original mid-May date, and DoD environments begin then too, completing by early August 2026, revised from an original mid-July estimate (Microsoft 365 Roadmap ID 560074).
Every stage of this rollout has slipped since the original announcement in April, so treat these dates as Microsoft’s current best estimate rather than a fixed schedule.
Once it lands, users will see a “Test mic and speaker” option on the pre-join screen before entering a meeting. Selecting it lets them record and play back a short audio clip, confirming both the microphone and speaker are working and that the correct devices are selected.
The feature is enabled by default, requires no admin configuration, and doesn’t change any existing meeting audio settings or policies, it’s purely a pre-join check.
Quick summary
Microsoft Teams is adding a mic and speaker test to the pre-join screen, rolling out from May 2026, covering:
- a “Test mic and speaker” option on the pre-join screen, letting users confirm their audio devices before entering a meeting
- recording and playing back a short audio clip to check the microphone and speaker are working correctly
- enabled by default, with no changes to existing meeting audio settings or policies
- no admin configuration required, and no compliance considerations identified
This is a small, sensible fix for one of the most common meeting complaints there is: joining late, or joining with the wrong microphone selected. The one thing worth knowing before you plan around it is that Microsoft has already revised this rollout’s timeline twice since announcing it in April.
Why this matters
There’s genuinely very little risk here, which makes it worth being straightforward about rather than manufacturing a concern that doesn’t exist. Two practical points are worth knowing:
- This rollout has already been delayed twice, and Microsoft flagged the most recent revision as recently as 20 July 2026. If you’re communicating this to users, avoid quoting a specific date with confidence, “coming this summer” holds up better than a month that Microsoft itself has already moved.
- The ADMIN IMPACT tag doesn’t mean admin action is required. Microsoft’s own recommendations say plainly that admins don’t need to do anything here. The tag appears to flag general relevance to admins rather than a required configuration step, worth keeping in mind so tagged updates aren’t automatically read as “something to configure.”
Who’s affected
- All Microsoft Teams users across Commercial, GCC, GCC High and DoD environments
- Helpdesk teams, who may see fewer “my mic isn’t working” tickets once this reaches users, since the pre-join test catches the issue before the meeting starts
What we’d recommend doing now
No admin action is required, and the preparation here is genuinely light:
- Let users know it’s coming, without committing to a specific date, given the rollout has already shifted twice.
- Update internal documentation or helpdesk guidance to reflect the new pre-join option, so it’s recognised as expected behaviour rather than flagged as unusual.
- Treat the ADMIN IMPACT tag as informational here, not as an instruction to configure anything, since Microsoft has explicitly said no admin action is needed.
Where this fits with your wider Microsoft Teams support approach
This is worth mentioning to anyone who handles Teams support tickets, since “can’t hear me” and “wrong microphone selected” are among the most common meeting complaints organisations deal with.
A pre-join test doesn’t eliminate every audio issue, but it catches the most preventable ones before they interrupt a meeting.
If Teams audio issues are already a recurring support burden for your organisation, we can help:
- Get in touch with our support team if recurring Teams audio or meeting issues are generating more helpdesk tickets than they should.
- Explore our Managing Microsoft Teams course if your admins would benefit from a wider refresher on Teams meeting configuration.
Learn more
- IT Admins – Use OneDrive policies to control sync settings – Microsoft Learn
Frequently Asked Questions
Why is my audio not working on Microsoft Teams?
Audio issues are usually caused by the wrong microphone or speaker being selected, rather than a fault with Teams itself. This new pre-join test is designed to catch exactly that, letting users confirm their devices are working correctly before they join a meeting.
How do you test your microphone on Microsoft Teams?
From May 2026, a “Test mic and speaker” option will appear on the pre-join screen before entering a meeting. Selecting it lets you record and play back a short audio clip to confirm your microphone and speaker are working correctly.
Does this change any existing Teams meeting or audio policies?
No. Microsoft has confirmed this update doesn’t modify meeting audio settings or policies, and no compliance considerations have been identified. It’s a pre-join convenience feature only.
Do admins need to configure anything for this to work?
No. The feature is enabled by default and requires no admin action, despite carrying Microsoft’s ADMIN IMPACT tag.
When is this rolling out?
Targeted release begins in early May 2026. General availability for commercial tenants worldwide is now expected to complete by late June 2026, with GCC, GCC High and DoD environments following through to early August 2026. All of these dates have already been revised at least once, most recently on 20 July 2026, associated with Microsoft 365 Roadmap ID 560074.
This update is based on Microsoft 365 Roadmap ID 560074, last updated 21 July 2026. Rollout dates are provided by Microsoft and may change.