We are updating the Settings menu for “Help & Feedback” and the in-app “Give Feedback/Suggest a Feature” experience for Teams Desktop & Web clients. Teams Desktop and Web clients will no longer use Microsoft Teams feedback policies for the in-app “Give Feedback/Suggest a Feature” experience, and instead use the Cloud Policy service for Microsoft 365.
We’re introducing a setting that allows Teams Phone Mobile users to opt-out of your presence automatically transitioning to Do Not Disturb when presenting or screen sharing. When this setting is enabled, users will be able to continue to receive call notifications when presenting, without having to manually adjust their presence status.
New features coming to the Text web part include enhancements to styling/formatting, bullets/numbered lists, and tables.
Microsoft Viva Engage will soon introduce a new community to support the adoption of Microsoft Copilot for Microsoft 365, offering features like one-click community creation and a setup checklist. Rollout begins late May 2024, with completion expected by early June 2024. No action is required from admins before the rollout.
Classic Teams will end support on July 1, 2024, and availability on July 1, 2025. Users will see informational banners starting April 2024 and experience non-dismissible dialogs post-availability end. Users should update their OS and address installation issues to prepare for the transition.
With this update, Insider risk management will help admins identify risky AI usage. We are adding new detections of intentional and unintentional insider risk activity on generative AI apps that can pose a risk to an organization. Activities will include risky prompts containing sensitive info or risky intent and sensitive responses containing sensitive info or is generated from sensitive files or sites. Coverage will span across Microsoft Copilots and 3P generative AI apps. These detections will also contribute to Adaptive Protection insider risk levels.
Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy.
,As of today, whenever the user wants to enable email notifications the policy tips also need to be enabled and vice versa, but with this decoupling the admin can configure the following: 1) None of policy tips or email notification 2) Only policy tips 3) Only Email Notifications 4) Both Email Notifications and Policy tips
If a modern M365 group is deleted, the associated SharePoint has a retention policy, a file with a retention label, or a legal hold, it remains active but orphaned. These sites cannot be excluded from the retention policy after the deletion of the group because of designed modern group scope. The site-level holds are applied when a group is added to a retention policy and the Tenant-level holds are applied when the complete modern group workload is added to a retention policy. Currently, to remove such a hold, the customer has to raise an escalation. With the rollout of this feature, users will be able to exclude the orphaned SPO site from both site-level holds and tenant-level holds as a self-service.
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
