Copilot Voice not working: microphone and audio checks

If Copilot Voice is not working, test microphone input and audio playback separately, then retry a short session before changing account settings. Microsoft’s current voice-and-vision instructions↗ (opens in a new tab) use Start a new voice chat in the Message Copilot prompt box and require microphone permission for Vision. The checks below help you identify where the failure occurs without promising one universal fix. fenbs can keep the successful checks and next step so you do not have to repeat the investigation.

What should you test first?

Start with a harmless sentence and one short request. Do not use a long work discussion as your audio test. Write down whether you cannot start voice, cannot be heard, or cannot hear the reply; each symptom points to a different check.

1. Play a familiar audio clip on the same device. Confirm that you can hear it through the speaker or headphones you intend to use.
2. Make a short recording with a recording tool you already trust. Play it back and check that the intended microphone captured your voice.
3. Return to Copilot and check the site or app’s microphone permission in your device or browser settings. Allow access only if you want to use it.
4. Start a short voice session using the control documented for your account. Ask a simple question and note whether input or output fails.
5. Change one thing, then repeat the same test. Keep the result so you know which change helped.

These are general audio checks, not evidence that a particular Copilot version has a particular settings panel. Avoid changing several devices, permissions, and accounts at once. You want a result you can explain and repeat, rather than a session that briefly works for an unknown reason.

What if Copilot cannot hear you?

If the separate recording is silent too, investigate the microphone before the Copilot session. Check a physical mute switch, the selected input device, and whether your headset is actually connected. Read any device permission message rather than dismissing it and retrying the same request.

If a recording works but the voice session does not, compare the microphone permission granted to that specific site or app. A working microphone in one application is useful evidence, but it does not tell you what another application is allowed to access. Retry the short test after making a deliberate permission change.

• Speak close enough for the recording test to capture clear words.
• Try the device’s built-in microphone to separate a headset problem from the rest of the setup.
• Note whether the failure starts before you speak or after you finish the request.
• Keep permission changes limited to the application you are testing.

For a normal voice walkthrough rather than diagnosis, see how to use Copilot Voice. Stay with one short test here until you can tell whether the input is reaching the session.

What if the microphone works but replies are silent?

Treat this as an output problem first. Check the volume and mute state for your device and the app or browser you are using. If you have headphones connected, confirm that sound is not being sent to a different device.

Repeat the familiar audio clip after each change. If that clip also becomes silent, you have evidence of a broader playback problem. If it remains audible while the voice session stays silent, save that distinction for the next troubleshooting step or support request.

Ask a typed question as a separate comparison. Record whether an ordinary text answer works, but do not treat that as proof that spoken replies should work in the same session. It narrows the problem without pretending to identify the cause.

A small table in your own notes is enough: microphone recording works; ordinary audio works; typed request works; spoken reply remains silent. This is much more useful than “Copilot is broken.” It also gives a connected assistant in fenbs a clear account of what you already checked.

Could your account or the wrong Copilot product explain it?

Identify the product and account before following a tutorial. Microsoft Copilot, Microsoft 365 experiences, Copilot Studio, and GitHub Copilot should not be treated as interchangeable settings screens. For the wider work-account context, see Microsoft 365 Copilot.

Microsoft’s Vision getting-started guide↗ (opens in a new tab) has specific account and license prerequisites. Those apply when diagnosing Vision during voice; they do not establish that every standalone voice failure requires the same subscription. Check the detailed requirements for the feature you are actually trying to use.

Do not infer availability from a broad “all experiences” banner. Also avoid treating a language list as a promise that every account receives every feature. Microsoft’s supported-language page↗ (opens in a new tab) is the place to check current language guidance rather than relying on a fixed list in an old tutorial.

What if voice starts but the session fails later?

Write down the last successful action and the exact error text, if there is one. Was the microphone test successful before the session stopped? Did playback fail only after switching audio devices? Compare the same short request in a fresh session before rebuilding a long discussion.

If you were also sharing visual input, distinguish ending that input from ending voice. Microsoft documents Stop sharing as ending visual sharing while leaving the voice conversation running. It also says Vision conversations cannot be resumed and do not reuse earlier screen or camera inputs. Keep a written summary when the visible state matters to the next attempt.

Do not try to repair an audio failure by deleting remembered facts. Copilot memory troubleshooting addresses a different problem. Likewise, finding Copilot history helps with saved sessions, rather than proving that a live audio connection is healthy.

If the checks leave the problem unresolved, prepare a short report: product, account type without personal identifiers, device, input test, output test, exact symptom, and the last change. Leave passwords, authentication codes, and private conversation content out of the report.

How to keep your voice troubleshooting with fenbs

Keep the checks that matter so you can carry on from exactly where you left off, on any device and in any other AI. Save what happened, what helped, and the one thing to try next.

1. Create a free account.
2. Write the problem in one sentence, such as “Voice input works, but I cannot hear the reply.”
3. Save each useful check and its result. Mark the problem unresolved until a repeat test works.
4. Use the connections page to connect an AI that can read the saved work. This is separate from fixing ordinary Copilot audio.
5. Before you stop, save the next step. Ask your next connected AI to read where you left off before suggesting more checks.

fenbs does not repair microphones or add an undocumented custom-tool field to ordinary Copilot. If this is a one-time audio issue, a short local note may be enough. For recurring work across assistants, keeping the checked result can save another round of explanation. Find more practical workflows in the AI at work guides.