Data Lifecycle Management: Separate Copilot retention policies from Teams chats

on
In a previous post I mentioned how Microsoft is adding the capability to use Purview Data Loss Prevention on Copilot to block certain information from surfacing for the user. Now, Microsoft is adding Copilot to it's retention policy controls, and starting mid-February, public preview tenants can start exploringthis new feature. Admins will be able to create separate retention policies for Microsoft Teams chats and Microsoft 365 Copilot interactions, and allows for a more tailored data management. The feature will of course require that the targeted users have Microsoft 365 Copilot license.  According to the message center, the public preview will be during February, and we can hope for a general release sometime in March. The feature will be available by default, but policies will have to be set up.

Viva pulse coming out of preview, SharePoint moving to use only B2B invitations and helping users select the most secure MFA option

on

Viva Pulse is a new feature coming to organizations who have invested in the Viva platform. Viva pulse is a new application, organizations can use to measure the "satisfaction temperature" of their employees. It's easy to use for both "Feedback authors" and "Feedback providers", and is of course fully integrated into Teams to make things easily accessible for all. As an organization admin, reading up on the following material is a great way to get started. 

Viva Pulse preview was announced to end on July 14th, and according to the message center, it should be rolling out around the 20th of July to users who have been assigned with the Viva Suite license. The official roadmap item is: 117393

Microsoft is making changes to the guest invitation flow in SharePoint. The flow is moving away from the original SharePoint engine, and into the new Azure B2B invitation manager. Sharing of files remains the same, but when users are being invited to sites the new invitation experience is used. There are several settings to consider, and it is recommended for admins to go through these policies to make collaboration easier. This update should be rolling out by the end of July.

MFA is getting a new tweak. By adding a "System-preferred" policy and setting it as default, the goal is to always prompt the user for the most secure MFA option available to them. This to avoid the use of weaker options such as SMS just because the user has registered for it previously. 

Admins should go through these settings to make sure any necessary exceptions are made for those who for some reason need to use a less secure MFA option than the more secure MFA they might have registered for. The rollout has begun, and should be completed by August.