Join Teams work meetings from Microsoft Teams (free) and vice versa

Microsoft Teams (Free) users can currently join Teams for work (or school) meetings only as guests, which requires them to use a browser and results in a sub-optimal experience. The new feature rolling out will allow these users to join Teams for work (or school) meetings in one click, without being redirected to the browser or asked to fill in their name/surname. They will also be able to continue collaborating with the meeting organizer and other participants via meeting chat after the meeting.  The feature will work in the opposite way as well, so Teams for work (or school) will just as easily be able to join meetings hosted by a Teams Free user with one click. This is associated with Roadmap ID: 167326

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

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.