A family of Microsoft word processing software products for creating web, email, and print documents.
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.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Same issue since yesterday. On PC, mac or event iPhone Microsoft 365 app.
Same issue, but somewhat good to know it's not isolated. Still frustrating, tho. Hope the fix released soon.
Same issue occurs for me on the desktop app and on IOS. This has happened before many times on my iphone and was annoying but would typically fix itself after closing and reopening the app, but as of an hour ago, it immediately gives the sign in error message on the desktop and phone. This is literally the only reason I pay for Microsoft so I can proofread my work, so I hope it gets addressed asap.
Same here, it started this morning after an update to Edge