We’re updating the subject and heading of service health emails to make it easier to grasp key information quickly. Instead of the generic subject line “M365 Service Health Notification” we’ll include the incident ID and affected product in the subject line. The heading of email will be changed from “[Product name] Service Health Notification” to the title of the issue.
Office for the web will begin respecting the Microsoft Purview Information Protection encryption setting that limits users’ ability to copy content to the clipboard.
Office for the web will begin respecting the Microsoft Purview Information Protection encryption setting that limits users’ ability to copy content to the clipboard.
The user page in Microsoft 365 Defender will be subject to a number of enhancements that will provide SecOps with a richer experience when viewing identity information in Microsoft 365 Defender. These include structure alignment to follow other entity pages in Microsoft 365 Defender, new side pane options like Location, Devices, Groups and Alerts, and clearer descriptions of user data on the main view, ensuring quicker identification of any given identity at a glance.
,When you choose a sensitivity label configured for user-defined permissions, they can now use domain names to restrict file access to specific individuals, or to all individuals from that domain. For example, you can specify “someone@example.com” or “@example.com” and permissions will be restricted based on those parameters.
For a better hybrid meeting experience, Teams users on their Android phone can use a single tap to join a meeting on both their device and Microsoft Teams Room. Audio on their device will be automatically turned off to ensure echo doesn’t happen. Furthermore, the landing experience on Android will be optimized for engagement activities to make it easier to raise hand or react, chat, see all participants, and more.
In government clouds, we honor the data residency commitments aligned with these environments. As a result, submissions are not sent to Microsoft. Admins can still create allow or block rules in the tenant allow/block list for emails via admin email submission. With this change, customers in our government cloud environments will be able to create allow and block entries for URLs and attachments in the Tenant allow block list via admin URL and email attachment submission. The data submitted via the submissions experience will not leave the customer tenant just as is standard for admin email submissions.
Security teams can now block sender email addresses, domains, URLs and email attachments while making admin submission for email, URL and file attachment respectively.
More info: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-defender-for-office%2Fintroducing-tenant-blocks-via-admin-submissions%2Fba-p%2F3604792&data=05%7C01%7Cv-begzaiem%40microsoft.com%7C3308930689f74
Allows in the tenant allow block list typically expire after 30 days, meaning legitimate email can continue to be blocked. With this change, Microsoft will automatically extend or remove allow rules based on an assessment of the particular entity.
Using the activity timeline from the Microsoft Defender for Identity portal as inspiration, this release will provide a dedicated tab on the user page in Microsoft 365 Defender that contains a full user activity timeline, detailing all activities and alerts from relevant workloads, associate dot that identity.
I've been working with Microsoft Technologies over the last ten years, mainly focused on creating collaboration and productivity solutions that drive the adoption of Microsoft Modern Workplace.
Found my content useful?
Buy Me a Beer
HANDS ON SharePoint
HANDS ON Teams
HANDS ON Lists
HANDS ON tek
M365 Admin
