Microsoft releases a new Office version to the Office Insiders in the Windows Beta Channel (Fast Ring). The latest Microsoft Office Version 2110 Build 14503.20002 adds a new feature to the Microsoft Outlook client. You can now use your voice to send an email and @mention people.
This build also adds Data Loss Prevention policy tips to Microsoft Word, Excel, and PowerPoint. Apart from these new features, Microsoft adds a bunch of fixes too. Here's the complete changelog.
What's new in Microsoft Office Version 2110 Build 14503
Use your voice to send an email and @mention people in Outlook
In our increasingly busy world, dictating your emails in Outlook has become a very popular way to improve your efficiency. We’ve now made this feature even more powerful by adding specific voice commands, enabling you to add people to an email, mention (@name) someone in a message, and send the mail—all using only your voice. To use this feature, click the Dictate button on the Message tab for an email. Then dictate your message and try out a voice command, such as “add [name] to email” or “at mention [name],” and observe the results.
Data Loss Prevention policy tips in Word, Excel, PowerPoint
Additional sensitive information types configured as part of OneDrive and SharePoint data loss prevention (DLP) policies can now be detected by the app to show a policy tip. This update also brings accuracy improvements and globalization support.
Other improvements and fixes in Microsoft Office Build 14503
Microsoft Outlook
- We fixed an issue where double-clicking to save an untrusted attachment would fail to save to network locations.
- We fixed an issue where messages created via Send To do not get default sensitivity labels.
Microsoft Excel
- We fixed an issue where automatic sensitivity labeling was not working for a few GCC-H tenants.
Microsoft PowerPoint
- We fixed an issue where using auto-save saved the file in an unexpected location; requests to save to a shared location were saved locally without notification.
Microsoft Project
- We fixed an issue where, if the decimal separator isn’t a period, enterprise resources can’t be saved when an enterprise number custom field is updated.
Microsoft Office Suite
- We fixed an issue where the ampersand character was incorrectly shown as an underline in the data types card.
Have a question? Or, a comment? Let's Discuss it below...
Thank you for visiting our website!
We value your engagement and would love to hear your thoughts. Don't forget to leave a comment below to share your feedback, opinions, or questions.
We believe in fostering an interactive and inclusive community, and your comments play a crucial role in creating that environment.