Short answer: SharePoint has no built-in dictation in its page editor, lists, or comments. Because those are ordinary browser fields, a system-wide voice-to-text tool works everywhere on the site. On Mac, click into the text web part, hold your hotkey, and speak. On iPhone, use a voice keyboard's mic button.
SharePoint is where a lot of organizational writing goes to die. The intranet news post nobody wrote. The document library where every file has a title and no description. The policy page last updated three reorganizations ago. The list of projects where the "Notes" column is empty in every row.
None of this is a SharePoint problem exactly. It is a friction problem. Every one of those empty fields represents a moment where someone knew the answer, looked at the box, estimated the typing cost, and decided it was not worth it. Multiply that by an organization and you get an intranet full of structure with no substance in it.
Voice changes that calculation, because the cost of filling a box drops from "type four sentences" to "say four sentences." Most adults type around 40 words per minute and speak at 130 to 150. This guide covers how to dictate into SharePoint on Mac and iPhone, which of its many text surfaces are worth talking into, which fields you should keep typing, and the boundary you need to respect around internal company data.
SharePoint has no dictation of its own
Worth stating clearly so you stop hunting. SharePoint Online's modern page editor, its list forms, its comment boxes, and its document metadata panes do not include a microphone button or a voice input mode. The dictation feature that Microsoft ships in Word and Outlook does not extend to the SharePoint page canvas, and there is no add-in you can install to put one there.
The practical answer is not to look for a SharePoint feature at all. SharePoint runs in a browser, and its text inputs are ordinary web fields. A tool that types at your system cursor works in all of them with no integration, no add-in, and no admin approval. That last part matters in an enterprise: nothing gets installed into your tenant, nothing needs a Microsoft 365 admin to consent to it, and there is no app registration to explain to IT.
This is the same reason dictation works in Confluence and ServiceNow without either vendor supporting it. Text at the cursor is text at the cursor.
Setting up on Mac
- Open your SharePoint page, list, or library in the browser and put it in edit mode.
- Click into the specific text box you want to fill. The rich text web part, the list item field, the comment box, whichever. The cursor must be blinking in that field before you speak.
- Hold your dictation hotkey, say the sentence, and release. The words appear where the cursor is.
- Read the result on screen, then save or publish.
With Voice Keyboard Pro on Mac, that hotkey is system-wide, so the same gesture works in the SharePoint page editor, in a Teams message about the page, and in the Word document the page links to. Nothing is per-app.
Two setup notes specific to SharePoint. First, choose a hotkey that does not collide with your browser or with SharePoint's own editor shortcuts, which claim a fair number of modifier combinations in the page canvas. A key you never press otherwise is the safe pick.
Second, click deliberately. SharePoint's modern page editor is a canvas of separate web parts, and it is easy to have focus in a different box than the one you are looking at. If your text lands in the wrong web part, that is almost always what happened.
Setting up on iPhone
The SharePoint mobile app and mobile browser both accept a third-party keyboard, which makes them useful for the class of SharePoint writing that happens away from a desk: adding a note to a list item after a site visit, commenting on a news post while commuting, updating a project status from a client office.
Tap into the field, switch keyboards with the globe key, tap the microphone, and speak. If you have not enabled a third-party keyboard before, it is Settings, then Keyboards, then add it and turn on Full Access so the mic can function.
Voice Edit is the iPhone feature that matters most for this. Repositioning a cursor in a small browser field with a thumb to fix one word is the reason mobile intranet updates do not happen. Speaking the correction instead removes the step people quit at. And for organizations that span languages, the two-way translation across 24 languages means a note can be captured in the speaker's language and posted in the site's working language.
The SharePoint surfaces worth dictating
1. News posts and announcements
The intranet news post is the highest-value thing on this list and the one most often skipped. Someone has news, opens the editor, sees a blank canvas, and decides to send an email instead. The email reaches thirty people once. The news post reaches the department indefinitely and is searchable.
Talk the post the way you would explain the news to a colleague standing at your desk: what happened, why it matters to the reader, what they need to do, and who to ask. Say "new paragraph" between those beats. That is under two minutes of speaking for a post that would otherwise not exist.
2. Page text web parts
Site pages, team home pages, process documentation, onboarding guides. These are long-form writing surfaces where the difference between speech and typing compounds most. Dictate the body, then use the editor for structure: headings, links, images, and the layout the text sits in.
3. Document metadata and descriptions
This is the quiet win. A document library with a Description or Summary column is dramatically more useful than one without, and search results improve when files carry real prose about what they contain rather than a filename. Nobody fills those columns in because typing a sentence per file across forty files is an afternoon.
Dictated, it is a pass. Open the details pane, click the field, say one sentence about what the document is and who it is for, move to the next. The library goes from a folder to something a new hire can navigate.
4. List item notes and status fields
Project trackers, issue logs, request lists, asset registers. Every one of them has a multi-line text column that is empty in most rows. That column is where the context lives that makes the list worth keeping: why this was deprioritized, what the vendor said, what to check before closing it.
Type the choice fields and dates. Speak the note. That split is the whole discipline of dictating into structured tools.
5. Comments and page conversations
SharePoint comments on news posts and pages are where feedback would happen if the feedback were cheap enough. Short, frequent, low-stakes writing is exactly the profile that dictation speeds up most, because the fixed cost of getting started dominates the total.
6. Site descriptions, navigation labels, and hub copy
The small connective text that makes an intranet legible. Site descriptions and section blurbs get written once at launch as placeholders and stay that way. Speaking a real one takes ten seconds.
Speak the sentences, type the settings
The reliable rule for any structured enterprise tool: dictate prose, type anything a system will parse.
Dictate: news post bodies, page copy, document descriptions, list notes and status commentary, comments, policy explanations, meeting summaries pasted into a page.
Type: URLs and links, file names, column names and internal field names, choice-column values that must match exactly, dates, numbers and IDs, permission group names, JSON in column formatting, anything in a Power Automate flow expression, and search or filter syntax.
The reason is not that dictation cannot produce those strings. It is that a transcription engine writes plain language, so spoken symbols and identifiers come out as words with spaces in them, and in a structured tool an almost-right value is worse than a missing one. If you do need to speak addresses or links occasionally, the technique has real quirks worth knowing, and we covered them in dictating email addresses and URLs.
A three-pass workflow for building a page
Trying to write, format, and configure at the same time is why intranet pages take an hour. Split it.
Pass one, talk it through. Drop a text web part on the page and speak the whole thing start to finish without stopping to fix anything. Wrong words, repeated sentences, missing structure, all fine. You are producing raw material at speaking speed.
Pass two, build the page. Now do the things hands are good at. Cut the third of the text that was throat-clearing. Break the block into headings. Add the links, the images, the web parts, the audience targeting. Set the page properties.
Pass three, read it aloud. Read the final page out loud before publishing. Dictated writing fails in a particular way: fluent enough to skim past a sentence that never actually landed. Reading catches it immediately. On an intranet this matters more than usual, because the audience is your colleagues and the page will sit there for two years.
Making dictated intranet copy sound right
Speak in full sentences
Dictating word by word, as though helping the software along, actually lowers accuracy. Transcription leans on surrounding context, so a complete sentence at a normal pace transcribes better than the same words delivered one at a time.
Say the paragraph breaks
A news post that arrives as one dense block is a news post nobody reads. Say "new paragraph" as you go and the structure survives into the editor.
Aim one notch more formal than conversation
Speech is warmer than typed corporate writing, which is usually an improvement on an intranet full of passive-voice boilerplate. But it also produces filler and hedging. The cut in pass two is where that comes out.
Watch tone on anything sensitive
Policy changes, incident write-ups, and reorganization announcements carry the emotion of the moment straight from your voice onto a page that many colleagues will read. Dictate the honest draft, then reread it as the audience before publishing.
Smart Vocabulary is what fixes your org's jargon
The transcription errors that persist in an enterprise setting are almost entirely proper nouns: internal system names, product code names, acronyms specific to your company, team names, and the surnames of the people you write about weekly. A general transcription engine has no reason to know any of them, so it substitutes the nearest ordinary word, consistently, forever.
No microphone fixes this, because it is not an audio problem. Smart Vocabulary on Mac is the tool for it: add the terms once with the spelling your organization uses, and they come out correctly from then on. For SharePoint work the list is short and pays for itself in a week — your site and hub names, your internal application names, your team acronyms, and the department names people spell inconsistently.
Related quirk worth knowing: acronyms and initialisms behave differently depending on whether you say them as a word or spell them out, which is covered in the guide linked above.
Meetings, and where SharePoint pages actually come from
A large share of intranet content is the residue of a meeting. Decisions get made in a call, someone volunteers to "put it on the SharePoint site," and three weeks later nothing is there because reconstructing the discussion from memory is harder than attending it was.
On Mac, Meeting Mode captures notes with speaker detection and produces AI notes, and calendar meeting detection means it can be ready when your scheduled meeting starts. The workflow that closes the gap is: capture in the meeting, then paste and shape into the SharePoint page the same day, while the decisions are still legible. The page gets written because the hard part was already done. If your meetings run in Teams, the same idea applies alongside dictating in Teams itself.
Privacy and your employer's policy
SharePoint holds internal company material, and that deserves a direct answer rather than a marketing one.
Voice Keyboard Pro's servers store only operational pings. No audio and no transcript content is stored server-side.
That is our side of it. Your side is your organization's policy. Enterprises differ enormously in what third-party tools they permit near internal data, and a regulated industry may have rules that go beyond preference. Nothing here installs into your Microsoft 365 tenant or requires admin consent, which removes the usual procurement obstacle, but it does not decide the question for you. If your work involves confidential, regulated, or client-privileged material, check with IT or security before dictating it. That is their call to make, not ours.
Frequently asked questions
Does dictating in SharePoint require an admin to approve anything?
No. A system-wide dictation tool runs on your Mac and types into the browser like a keyboard does. There is no SharePoint add-in, no app registration, and nothing added to your tenant. Whether your employer permits the tool on a managed device is a separate question worth asking.
Does Microsoft's own dictation work in SharePoint?
The dictation button Microsoft ships in Word and Outlook is a feature of those apps, not of the SharePoint page editor. If you open a document from a SharePoint library in Word for the web or the desktop app, you are dictating in Word at that point, not in SharePoint. The page canvas, list forms, and comment boxes have no such button.
Can I dictate into a SharePoint list on my iPhone?
Yes. Both the SharePoint mobile app and mobile Safari accept a third-party keyboard, so the mic button works in list fields and comment boxes the same way it works anywhere else on iOS.
What about SharePoint Server on-premises?
The classic on-premises page editor is still a browser text field, so cursor-level dictation works there too. The surfaces differ from SharePoint Online, but the underlying approach does not.
Will dictated text break SharePoint formatting?
No. Dictation inserts plain characters at the cursor, exactly as typing does. Formatting comes from the editor, which is why the three-pass workflow puts formatting in a separate pass after the words exist.
Is it accurate enough for something the whole company reads?
With the read-back step, yes. The failures that survive are proper nouns and occasional homophones, both visible on one careful read. Smart Vocabulary removes most of the first category. Never publish an intranet page you have not read, dictated or typed.
The bottom line
Most of what is wrong with a company intranet is not architecture. It is the accumulated cost of every empty text box that somebody decided was not worth typing into. Dropping the cost of filling those boxes is a smaller intervention than a migration and does more.
An intranet is only as good as the sentences people bothered to write in it. Make the sentences cheap and the intranet gets better on its own.
Voice Keyboard Pro works system-wide on Mac and as a keyboard on iPhone, so it covers the news post you write at your desk and the list note you add from a site visit. There is a free tier with daily limits; Pro is $4.99 a month or $34.99 a year.