This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Every time I try to use the "Read Aloud" function, I get this exact error:
"To choose what voice you hear while using Read Aloud, sign in with your Microsoft account."
It worked fine until two weeks ago (the last time I used it) and I have tried every single thing in every thread: I reinstalled the apps, logged out and in, "repair online", reinstalled the english langague packs on my computer, used safe mode, turned on the optional experience, rebooted my pc, and it still doesn't work. I am out of options.
Last time, it was apparently due to a windows update, and yesterday I did update my windows, but I don't see anyone talking about it, so I don't know, please help.
A family of Microsoft word processing software products for creating web, email, and print documents.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Mine is up and running!!!! 8:30 PM EDT
Evidently today's update set it back in order.
After nearly 5 days of frustration, thank you MS for the fix.
I just started having the same issues a few hours ago. It was working until about 3PM EST.
I was on a chat with Microsoft support for about an hour regarding this issue. I informed the individual up front that I tried all the usual fixes in all the threads, just like you mentioned, yet they insisted I try them all again. When none of them worked, they simply dropped off of the chat without a word. Super unprofessional and frustrating. Especially since this is a feature that I use daily. I hate when this bug crops up. Hopefully they fix it soon. But I am glad to confirm that it is indeed the bug, and not simply me.
Hi doveOO and All,
Currently, there have many different users are experiencing the issue that when they try to use the Read Aloud Function in Word desktop application, it will pop the message saying, "To choose what voice you hear while using Read Aloud, sign in with your Microsoft account.", which prevented users from using the Read Aloud function as usual.
Also, from my search across the community, the sameissue is currently happening for both Microsoft 365 Business/Education and also Home/Personal subscription with a work/account or a Microsoft personal account, which proves the popping message doesn't really make the sense. In this situation, as it can highly possibly be a potential bug from Word product side, my suggestion for all affected users is to report this inconvenience and unsatisfied user experience directly to the Word development team and so the product engineers can get informed of how this temporary Read Aloud issue has caused the low work-efficiency for many end users **** and recover back the available function AS SOON AS POSSIBLE.
From admin users, the most efficient way is to raise a free M365 support ticket where product engineers there will offer escalated support resources for this and report this directly to the internal channel ASAP: Get support - Microsoft 365 admin | Microsoft Learn****
And for end users, submit direct feedbackvia the in-app channel: How do I give feedback on Microsoft 365? - Microsoft Support
Please understand that as a community moderator here, I have limited troubleshooting suggestions offer here to resolve such potential bug from product backend. But I will keep monitor from the Microsoft Service Incident Center and if I receive any bugfix notifications on our side, I'll share with you here as soon as I can! I appreciate your time and patience on checking this reply. Hope you stay well and safe!
Sincerely,
Mia | Microsoft Community Moderator
Same issue since this afternoon. Reported the problem through MS Word. Let's hope they get a fix soon.