The sensitivity toolbar is also available while saving new documents or renaming existing ones. New sensitivity labels powered by Microsoft Purview Information Protection are now displayed alongside the filename in the app's title bar, allowing you to easily recognize and adhere to your organization's policies. In addition, there is a new Sensitivity toolbar in Excel, PowerPoint, and Word that makes it easier to prevent data leaks. The apps will now automatically disable the legacy Azure Information Protection add-in and use the built-in sensitivity labels to view and apply labels powered by Microsoft Purview Information Protection. The build also disables the Azure Information Protection Add-in by default in Excel, Outlook, PowerPoint, and Word.
When using built-in sensitivity labels, admins can specify a sublabel to get applied automatically when a parent label is selected. This build offers a variety of new features, including the ability to assign a sublabel as the default when a parent label is selected in Excel, Outlook, PowerPoint, and Word. This build fixes two bugs in Outlook, one that caused the new labels to fail to appear for some users of the Label Inheritance feature, and another that caused the Suggested Replies feature to not be disabled when connected experiences are disabled. This build fixes two bugs, one that causes Access to close unexpectedly when exporting from an SAS application to a Microsoft Office format, and another in Outlook that hat caused some users to see the wrong Data Loss Prevention policy annotations in a multi-account profile. The build fixes a variety of bugs, including one in which an Excel file could not be previewed in File Explorer if the file’s extension included a capital letter such as XLSX or Xlsx, and one in which PowerPoint sometimes crashed when opening a file. (Access still supports Internet Explorer browser control.) This build offers several new features, including adding closed captions to audio objects in PowerPoint and web browser control for Edge in Access. For details, see Release notes for Microsoft Office security updates. It also fixes a number of security holes.
This build fixes several bugs, including one in Outlook that caused users of the Event-Based feature to be unable to utilize some of the new APIs included in Mailbox Requirement Set 1.13, and one in Project in which users were unable to connect Project Client from the desktop to a Project Web Access site in Project Server 2016. It also fixes a variety of bugs, including one in Excel in which Conditional Formatting rules were not being preserved after closing and reopening a workbook, one in Outlook in which people were shown the error “We cannot render Actionable Messages right now” when reading some email messages, and one in Access in which refreshing an ODBC connection to an Access database caused the operation to stop working after refreshing the link several times. This build offers faster filtering when cells contain unique or duplicate rules in Excel, as well as a new accessibility ribbon tab in Outlook and PowerPoint for making emails and presentations more accessible. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update. What IT needs to know: Because this is a security update, it should be applied relatively soon. This build fixes a number of security holes. This build includes several new features, including adding autocomplete capabilities to Excel’s Data Validation dropdown list, and giving Outlook pop-up messages that warn, justify, or block emails being sent based on sensitivity labels.Ī number of bugs have also been fixed, including one in Outlook’s Me control that showed the wrong display name in Office apps, and one in Word in which doing a mail merge displayed the error “Microsoft Word is required to run the Mail Merge Wizard.”
0 kommentar(er)
