Updated August 29, 2026 · By Sumbat.T

If you have spent ten minutes hunting through the Teams message box for a microphone icon, stop looking. It is not hidden behind a setting, it is not gated behind your organisation's license, and you have not missed an update. Microsoft Teams has no dictation feature in the chat compose box, and it never has.
The confusion is completely reasonable, because every other Microsoft app you use all day does have one. Word, Outlook, PowerPoint and OneNote all put a Dictate button in the Home tab of the ribbon, and it works well. Teams sits in the same Microsoft 365 subscription, wears the same badge and lives in the same launcher, so the reasonable assumption is that it has the same feature somewhere. It does not. Teams was built as a communications product rather than a document editor, and the Office dictation feature was never ported into it.
Worth knowing
Microsoft's own support answers point people to Windows voice typing for this. When users have asked in the Microsoft Q&A forums how to use speech to text in Teams, the recommended answer is the Win+H shortcut rather than anything inside the Teams interface, and Microsoft's documentation confirms the Dictate feature belongs to the Microsoft 365 apps rather than Teams.
There is a second source of confusion worth clearing up in the same breath, because it sends a lot of people down the wrong path. Teams does have speech features, and they are well documented. Live captions turn what people say in a meeting into on-screen text, and meeting transcription produces a written record of a call afterwards. Both are genuinely speech to text. Neither one lets you dictate a message.
The distinction matters because the two features solve opposite problems. Dictation is input: you speak, and text appears in a field you chose, replacing typing. Transcription is a record: the meeting is captured and written down afterwards, replacing note-taking. Turning on transcription in a call will not help you write a chat message, and no amount of searching the transcription settings will produce a dictate button.
Once you accept that Teams will not do this itself, the problem gets much simpler, because the answer is the same one that works everywhere else in Windows. You do not need Teams to support dictation. You need a dictation tool that types into whatever text field currently has your cursor, and the Teams message box is just a text field.
That is how all of the methods below work, the free built-in one included. None of them plug into Teams, none of them need an admin to approve an app, and none of them care which version of Teams you are running. They put text where the cursor is. Teams is not special to them, which is exactly why they work.
| Method | How you start it | Cost | Cleans up your speech |
|---|---|---|---|
Windows voice typing | Win+H in the message box | Free, built in | None, types you literally |
BlabbyAI | Ctrl+Space anywhere in Windows | Free tier, then $8.49/mo | Yes, and you write the rules |
Teams mobile keyboard | Mic key on the phone keyboard | Free, built in | None |
Wispr Flow | Shortcut, types into focus | $15/mo, $12 billed annually | Yes, automatic |


This is the method Microsoft support staff recommend and it is the right place to start, because it costs nothing, installs nothing, and is already on the machine in front of you. It ships with Windows 11 and Windows 10.
Click into the Teams message box
Open the chat, channel or meeting chat you want to post in, and click into the compose box so the cursor is blinking there. This step is the one people skip and it is the one that matters, because voice typing types wherever the cursor is, not wherever you are looking.
Press Windows key + H
The voice typing bar appears near the bottom of the screen with a microphone in the middle. The first time you use it, Windows may ask for microphone permission, which you grant under Settings, Privacy and security, Microphone.
Speak your message
The words appear in the Teams box as you talk. You do not need to click the microphone icon first on Windows 11, it starts listening when the bar opens.
Turn on automatic punctuation
Click the settings gear on the voice typing bar and switch on automatic punctuation. Do this once and it sticks. Without it you have to say "comma" and "full stop" out loud, and Windows 10 does not offer it at all.
Stop, read it back, then send
Press Win+H again or say "stop listening". Read the message before you press Enter. Voice typing does not send anything for you, which is a feature rather than a limitation.

Source: Microsoft Windows. The Win+H voice typing bar. It floats above whatever app you are in, so the Teams message box behind it receives the text.
That is the whole method, and for a fast reply to a colleague it is genuinely good. It is free, it is unlimited, and it is two keystrokes away in an app you already have open.
Windows voice typing has one design decision at its centre that shapes everything about how it feels to use: it transcribes you literally. Every word that comes out of your mouth goes into the message box, in the order you said it.
That sounds like exactly what you asked for until you listen to how people actually speak. Nobody talks in finished sentences. You start a thought, realise halfway through that the second half should have come first, and start again. You say "um" while you think. You repeat a word. Spoken out loud between two people none of this registers, because the listener discards it automatically. Written into a Teams channel post, all of it is still there.
The practical test
Dictate a real message to a real colleague with Win+H and then read it before sending. If you find yourself editing it, that editing is the time you thought you were saving. For a two-line reply it is nothing. For a channel post or a message to a client, it is most of the benefit.
There are three smaller limits worth knowing about before you commit to it as your only method:


The second category of tool works the same way at the keyboard level, types into the same focused field, and needs no more integration with Teams than Win+H does. What it adds is a step between the transcription and the typing: your speech goes through a language model before anything lands in the message box.
BlabbyAI is the one we build. The mechanics in Teams are the same five steps as above, with the shortcut being Ctrl+Space rather than Win+H: cursor in the message box, press it, speak, press it again, and the finished text is typed in. It works in one to one chats, channel posts, thread replies and the meeting chat panel, because all of those are text fields.
Dictate into Teams



Speak the message, send what you meant
BlabbyAI types into any Teams chat, channel post or meeting chat, with the filler stripped out and the punctuation already there. 60 free credits a week, no card required.
The difference between the two methods is not accuracy. Modern speech models all transcribe ordinary speech well, and Windows voice typing is no exception. The difference is what happens to the transcript before it becomes your message.
In BlabbyAI this is called a mode, and a mode is a plain-English instruction that you write yourself and assign to a shortcut. The instruction runs on every recording made in that mode. It is not a menu of preset options, it is a free-form prompt, so it does roughly whatever you could ask a language model to do to a block of text.

The mode editor. The instruction on the left runs on every recording made in that mode, so a Teams mode can be tuned to how your team writes.
For Teams specifically, a few instructions earn their keep immediately:
Strip the thinking out loud
"Remove filler words and false starts. If I begin a sentence and restart it, keep only the final version." This is the one that makes dictated messages sendable without editing.
Your own spoken commands
"When I say ‘new paragraph’, insert a paragraph break instead of writing those words. When I say ‘bullet point’, start a new list item." You define the vocabulary rather than learning a fixed list.
Match the register of the channel
"Rewrite this as a short, direct Teams message. Keep it friendly and under four sentences." A second mode on a second shortcut can be the formal one for client-facing channels.
Speak one language, post another
"Translate what I said into English, fix the grammar, and format it as a Teams message." All three in one pass, on one shortcut, which is the case built-in dictation cannot cover at all.
How this actually behaves
Your speech is the input, not a request. If a tidy-up mode is active and you say "tell the team the deploy is delayed", you get that sentence cleaned up, not an announcement written for you. To get the message, speak the message: "hey everyone, the deploy is slipping to Thursday, the migration took longer than we planned and I would rather not rush it". Rambling is fine, that is the point. The mode shapes what you said, it does not answer it.
There is also a custom spelling feature, which is the answer to the vocabulary problem Win+H has no solution for. You teach it how to spell your colleagues' names, your product names and your team's acronyms once, and they come out right in every message after that.

Each mode gets its own shortcut, so a casual internal one and a formal client-facing one are a different key press rather than a settings change.
Teams runs on everything, and the dictation answer changes with the operating system rather than with Teams itself, since Teams is not involved either way.
On a Mac, dictation is a system setting. Open System Settings, go to Keyboard, turn on Dictation and note the shortcut it assigns. Put the cursor in the Teams message box, press it, and speak. The behaviour matches Windows voice typing closely, including the part where it types you word for word.
On a Chromebook, or in Teams on the web, you have two routes. ChromeOS has built-in dictation on Search+D once you enable it under Accessibility. Or, since Teams on the web is a browser tab like any other, a dictation Chrome extension works in it directly. That route is worth knowing about for a second reason: on a locked-down work laptop where IT will not let you install an executable, a browser extension usually installs where a desktop app will not.
On the Teams mobile app, there is no dictate button either, but you do not need one. Tap into the message box and use the microphone key on your phone's own keyboard, which is the same feature you use for text messages. It is the most reliable dictation on any platform for short replies, and it is the reason a lot of people answer Teams messages from their phone even while sitting at their desk.
Almost every failure here has a cause outside Teams, which is good news, because it means the fix is outside Teams too. In rough order of how often each one is the culprit:
The cursor is not in the message box
This is the most common one by a wide margin. Voice typing types into the focused field, so if a notification stole focus or you clicked a channel in the sidebar after starting, the words go somewhere else entirely. Click back into the compose box and start again.
Teams is holding the microphone
If you are in a call, Teams has the microphone and Windows voice typing may not be able to share it. Leave the call, or use your phone's keyboard for the message instead.
Microphone permission is off
Go to Settings, Privacy and security, Microphone. Confirm microphone access is on and that desktop apps are allowed to use it. Both switches have to be on, and the second one is easy to miss.
Another app has captured Win+H
If the voice typing bar does not appear at all, in any app, the shortcut is being intercepted. Close recently installed utilities one at a time and test again in Notepad, which rules Teams out entirely.
The wrong microphone is selected
If the bar appears but hears nothing, Windows is probably listening to a headset that is switched off or a webcam mic across the room. Check Settings, System, Sound and set the input device you actually speak into.
If you want the longer version of this, we have a full guide to voice typing not working on Windows, and a separate one for when the Dictate button fails in Word, which is the app people usually try next.
The honest answer is that most people who dictate in Teams a lot end up using more than one of these, because the right tool depends on who is going to read the message.
A one-line reply to a teammate
Win+H. It is free, it is already there, and nobody minds a stray "um" in a two-line answer to a colleague you talk to daily.
A channel post the whole team reads
A tool with a cleanup step. This is where literal transcription costs you, because the editing pass is longer than typing it would have been.
Messages in a second language
A mode that translates and fixes grammar in one pass. Built-in dictation transcribes the language you spoke and stops there.
A locked-down work laptop
Win+H, since it is part of Windows, or a browser extension with Teams on the web if IT blocks installers.
One thing worth saying plainly, because it is the reason dictation is worth setting up at all in a chat app: the value is not that speaking is faster than typing, although it is. It is that talking through a thought is easier than composing it. Most people can explain a situation out loud in fifteen seconds that would take three minutes to write, because writing forces you to get the structure right on the first pass. Dictation with a cleanup step lets you do the explaining and hands the structure to the machine.
If Teams is one of several apps you type into all day, it is worth picking a method that covers all of them at once. Anything that works at the keyboard level works in Gmail, Outlook, Word and Notion the same way it works in Teams, because none of them are special to a tool that simply types where the cursor is.
Click into the Teams message box so the cursor is blinking there, then press Windows key + H. The Windows voice typing bar appears, and everything you say is typed into the Teams message box. Press Win+H again or say "stop listening" when you are done, read the message back, and press Enter to send. There is no Dictate button inside Teams itself, so the dictation always comes from outside the app: either Windows voice typing, or a third-party dictation tool that types into the focused field the same way. BlabbyAI is that kind of tool: press Ctrl+Space, speak, press it again, and the text lands in the Teams box already punctuated. On a Mac, the equivalent built-in option is turning on Dictation in System Settings and pressing the shortcut you assign there.
Not in the chat compose box. Teams has speech features, but they are for meetings rather than messages: live captions and meeting transcription both turn spoken audio into text during a call. Neither one lets you dictate a chat message. Word, Outlook and PowerPoint all have a Dictate button in the ribbon, and Teams does not, which is why so many people go looking for one and cannot find it. The workaround Microsoft support staff themselves recommend is Windows voice typing on Win+H, which works in the Teams message box because it works in any text field in Windows. Third-party dictation apps such as BlabbyAI work the same way and add automatic punctuation and cleanup on top.
There is no Dictate button in Teams. This is not a setting you have failed to enable or a feature restricted by your license, it simply does not exist in the product. The Dictate button you are thinking of belongs to the Microsoft 365 apps, Word, Outlook, PowerPoint and OneNote, which have it in the Home tab of the ribbon. Teams was built as a communications app rather than an Office document editor and never received it. On mobile, the Teams app has no dictate button either, but your phone keyboard has a microphone key that does the same job. On desktop the practical fix is a dictation tool that adds the button Teams never shipped: BlabbyAI puts one in every text field, Teams included.
Voice typing is built into Windows 11 and Windows 10 and needs no installation. Click into any text field, including the Teams message box, and press Windows key + H. On first use Windows may ask for microphone permission, and you grant it under Settings, Privacy and security, Microphone. In Windows 11 you can also turn on automatic punctuation from the settings gear on the voice typing bar itself, which is worth doing straight away because without it you have to speak every comma and full stop out loud. Windows 10 has no automatic punctuation at all, which is one reason Windows 10 users often reach for a third-party tool like BlabbyAI, where punctuation is automatic on both versions.
The three common causes are all outside Teams. First, focus: voice typing types into whatever field has the cursor, so if you clicked away from the message box or a notification stole focus, the words go somewhere else. Click back into the compose box and start again. Second, the microphone: if Teams is in a call it may be holding the microphone, and Windows voice typing cannot always get it at the same time. Third, permissions: check Settings, Privacy and security, Microphone and confirm both microphone access and desktop app access are on. If Win+H does nothing at all, the shortcut may be captured by another running app, which is worth checking before you assume Windows is broken. Tools with their own configurable shortcut, BlabbyAI among them, sidestep that particular clash because you can reassign the key.
Yes. Anything in Teams that accepts typed text accepts dictation, because the dictation tool is typing into the focused field rather than integrating with Teams. That covers one to one chats, group chats, channel posts, replies to a thread, the meeting chat panel during a call, and the search box. The one thing worth knowing about channel posts is that the formatted composer, the expanded one with the subject line and formatting toolbar, is still just a text field, so you can dictate the subject and the body separately by clicking into each one first. This is true of any field-level dictation tool, BlabbyAI included.
It is accurate enough to get the words down and usually not clean enough to send without a read-through. Windows voice typing transcribes you literally, so filler words, false starts and repeated phrases all land in the message exactly as you said them. On Windows 11 with automatic punctuation on, the result is usually readable. What you do not get is any tidying: if you started a sentence, changed your mind and started again, both attempts are in the box. For a quick reply to a colleague that is fine. For a message to a client or a post to a whole channel, most people end up editing, which is where the time saving disappears. This is the gap AI dictation fills: BlabbyAI runs what you said through a custom mode, so the filler words and false starts are removed before the text reaches the message box.
They solve opposite problems. Dictation is input: you speak and text appears in a field you chose, so it replaces typing. Teams transcription is a record: during a meeting it captures what everyone said and produces a transcript afterwards, so it replaces note-taking. Turning on transcription in a meeting does not help you write a chat message, and dictating a chat message does not produce a meeting record. People searching for how to dictate in Teams often land on transcription documentation by mistake, because both features are described as speech to text. BlabbyAI is a dictation tool, so it belongs to the first category: it types what you say into the field you chose.
On a Mac, dictation is a system feature: open System Settings, Keyboard, and turn on Dictation, which lets you set a shortcut. Press it with the cursor in the Teams message box and speak. On a Chromebook, if you use Teams in the browser, ChromeOS dictation is Search+D once you enable it under Accessibility. In both cases the built-in tool has the same limitation Windows voice typing has, which is that it types you word for word with no cleanup. Browser-based dictation extensions are the usual answer on those two platforms, because they work in a Chrome tab regardless of which operating system is underneath. The BlabbyAI Chrome extension is one of them, and it needs no install beyond the extension itself.
It can write down what you say and then reshape it, but it cannot invent content you did not speak. This is the distinction that trips people up with AI dictation tools. If you activate a tidy-up mode and say "tell the team the deploy is delayed", you get that exact sentence cleaned up, not a written announcement about a delayed deploy. To get the message, you speak the message: say what you would actually type, rambling and out of order is fine, and the AI layer turns it into something worth sending. That is the real time saving, because talking through a thought is faster than composing it in a text box. In BlabbyAI you decide what the tidy-up does by writing the mode yourself, so a "Teams message" mode can keep it short and drop the filler.
Teams has no Dictate button and is not going to grow one, so every answer to this question comes from outside the app. Windows voice typing on Win+H is the free one, it works in every Teams field, and it is the right first thing to try. Turn on automatic punctuation the first time you open it.
Where you go after that depends on what happens when you read your messages back before sending. If you are not editing them, you are done and you have spent nothing. If you are editing every one, the editing is the cost, and a tool with a cleanup step is what removes it. That is what BlabbyAI does in the Teams message box: same shortcut-and-speak flow, with an instruction you wrote running on the transcript before it is typed, so the filler is gone and the message reads like you meant to write it.
For the wider picture, our best AI dictation apps roundup compares the field with prices, and voice typing on Windows goes deeper on Win+H itself, including every voice command it accepts. If your team lives in chat, the same approach covers Discord and every other message box you touch.
Try it on your next Teams message
60 credits a week, no card and no account setup. Put the cursor in a Teams chat, press the shortcut, and see how much of the message you would have edited.