Microsoft released a new Office preview build 14217.20002 for Office Suites (version 2107). The build is now rolling out to the Office Insiders who are in the Windows Beta Channel (Fast Ring). The latest Microsoft Office Insiders Preview Build adds a new feature to the Microsoft Outlook client.
This build also comes with several bug fixes for Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and Microsoft Project. To know more about the new feature for Microsoft Outlook and the other fixes, continue reading further.
What's new and improved in Microsoft Office build 14217
With the latest Microsoft Office Insiders Build 14217.20002 released to the insiders in the Windows Beta Channel, Microsoft adds a new improvement to the Microsoft Outlook client. It now improves the functionality for default and mandatory labeling in Outlook.
Outlook clients that use built-in labeling will now also enforce the existing PowerShell label policy advanced settings DisableMandatoryInOutlook and OutlookDefaultLabel, previously supported only by the Azure Information Protection unified labeling client. If you have already configured these settings for your organization, they will now be enforced in Outlook clients.
Apart from this new improvement, Microsoft fixed an issue in Outlook client where hyperlinks, including digits, would be broken when composing a message in a right-to-left language.
Other fixes in Microsoft Office build 14217
- Microsoft fixed an issue in Microsoft Word where enabling auto-save could cause recent edits to temporarily disappear
- Microsoft fixed an issue in Microsoft Word with scrolling in the comments pane
- Microsoft fixed an issue in Microsoft Word where header/footer text was not clearly visible in print preview when the Office theme was set to black
- Microsoft fixed an issue in Microsoft Excel where chart axis values could not be changed if both the thousand and decimal separators use the same symbol
- Microsoft fixed an issue in Microsoft PowerPoint related to SmartArt nodes having Change Shape disabled
- Microsoft fixed an issue in Microsoft Project where engagements created in the Project Web App might not load properly in the Project desktop client if the resource name had special characters, such as a semicolon
- Microsoft fixed an issue in Microsoft Project where, when the project option “Project should calculate costs” is disabled, the time-phased cost values might not have been correctly baselined for cost-type resources
- Microsoft fixed an issue in Microsoft Project where project-level enterprise custom fields with lookup tables were not showing a value in the Project desktop client
- Microsoft fixed an issue in Microsoft Project where saving a local project to Project Web App could change a previously saved baseline
