Outlook for Mac Font Bug: What Broke and How to Work Around It
A stable-channel update to Outlook for Mac broke font selection during email composition, and as of The Register's July 9 report, no fix had reached affected users. The Outlook for Mac font bug is straightforward to describe: pick any non-default font in the formatting toolbar, and the app ignores the choice entirely, continuing in the default typeface as though nothing happened. A forum moderator acknowledged the problem two days before The Register's coverage, on July 8, without a patch following.
The Register described the delay as roughly four weeks with still no fix, calling it "astonishing" for a regression it characterized as fundamental enough that it should never have cleared unit testing.
What the Outlook for Mac font issue actually is
The failure is limited to the compose window. Everything in the font selector looks functional the dropdown works, the options are all there but none of it takes effect. The app keeps using its default typeface regardless of what the user selects.
Users who dug into the underlying HTML found what appears to be the root cause: stray quote characters inserted in places they don't belong, which break font attribute injection at the markup level, The Register reported. That matters because it rules out a configuration fix. There is nothing to toggle, no setting to reset. A corrected build would need to arrive to resolve it.
The practical cost depends on what you're sending. For general correspondence, typing in whatever font Outlook defaults to is an inconvenience. For developers and technical communicators who routinely share terminal output or code snippets, it's a genuine block. One affected reader told The Register: "Not being able to share terminal output and snippets of code in a monospaced font is quite the limitation. The workaround, sad that it is, is to compose messages in Word and then paste them into Outlook."
Font selection isn't a cosmetic feature sitting at the edge of Outlook's toolset. It's the most basic formatting control in the compose window. When it stops working, certain messages simply can't be composed the way they need to be, and the app offers no indication that anything is wrong.
Outlook for Mac font workaround: your options right now
How you respond depends on how much control you have over the machine. Depending on your environment, one of the following three paths applies.
-
Roll back and pause updates. If you manage your own Mac and aren't in a locked-down enterprise environment, reverting to an earlier version of Outlook and pausing automatic updates eliminates the bug. The tradeoff is staying on an older build until a stable-channel fix ships, at which point you update manually. For individuals, this is the cleanest available option, per The Register.
-
Compose in Word, paste into Outlook. If rollback isn't available managed devices, IT-controlled environments write any message requiring non-default fonts in Microsoft Word first, then paste into Outlook before sending. It's an extra step and a tedious one, but it preserves formatting and keeps the machine on a supported build. At least one affected user has already settled into this routine for code-heavy communications, according to The Register.
-
Wait for a stable-channel update. Forum reports suggest the bug is absent in Outlook for Mac beta and preview builds, which may indicate a fix is moving through the pipeline, The Register noted. Microsoft has not confirmed a timeline. When the next stable-channel update arrives, apply it promptly that's the most likely delivery vehicle for a resolution.
The beta and preview signal is the most encouraging piece of information available. A broken feature that's clean in pre-release builds suggests the fix exists and is staged somewhere in the pipeline. That doesn't explain how the regression shipped in the first place, but it does suggest the wait shouldn't be indefinite.
What Microsoft has said and what the roadmap shows
As of The Register's July 9 report, Microsoft had not issued a public statement beyond the forum moderator's acknowledgment the previous day. No patch timeline has been confirmed.
Microsoft positions new Outlook as the Copilot-enabled successor to classic Outlook and publishes a feature comparison matrix tracking what's available now versus what's coming soon. The documentation states: "We are actively listening to your feedback and will make updates and changes to our feature roadmap based on what you tell us." The matrix is framed around Windows parity and does not define equivalent timelines for the Mac desktop app.
The font regression isn't a missing feature waiting on a roadmap entry. It's a capability that existed and broke. That distinction matters when evaluating how quickly the Mac desktop channel gets attention.
Why this keeps happening on the Mac desktop
The font bug doesn't exist in isolation. Two separate user reports from earlier this year describe the same pattern: functional on the web, absent or broken on the Mac desktop.
In January, users on version 16.105 reported that Tasks and To Do had disappeared from the desktop app entirely no sidebar icon, no task pane while both remained accessible through Outlook on the web. One user described the situation plainly: "Accessing OWA is now the only way for users to see tasks/flagged emails, but very much not the preferred solution since there IS a desktop client which should do that," according to the Microsoft Community Hub.
Around the same time, a licensed Microsoft 365 Copilot subscriber running version 16.106 reported that the Copilot Chat icon was absent from the desktop app's navigation bar and couldn't be added through sidebar settings, while working normally in Outlook on the web for the same account. The Copilot app didn't even appear as an option to add, per a separate Community Hub post.
These are individual user reports, not confirmed scope data from Microsoft, and they don't establish broader prevalence. But the pattern has appeared more than once: something works in the browser, doesn't work in the desktop app, and the user is left filing a forum post.
Outlook Mobile, by comparison, ships on a roughly biweekly cadence, according to Microsoft's release notes. That's not a direct comparison mobile and desktop release cycles involve different constraints but it does establish that Microsoft can move quickly when it chooses to. A regression as fundamental as broken font selection surviving roughly four weeks in the stable desktop channel raises a reasonable question about whether the Mac desktop app is receiving the same level of release scrutiny.
Roll back if the environment allows it. Use the Word paste workaround if it doesn't. Either way, the next stable-channel update is worth applying as soon as it arrives.
Comments
Be the first, drop a comment!