I just did a write up on this:
If a user is running Windows 11 with “Teams for Work or School” installed and within the past few weeks, their Teams application has started looking a bit odd and not behaving the same way, it is because of an update to the “Teams for Home or Small Business” that comes pre-installed with Windows 11. The behavior is best identified when a user accesses a meeting in Teams. The expected behavior is the meeting to be opened in a separate window from Teams, however, Teams looks like this when opening a meeting:

As you can see, there are no “reactions” any longer. The only reaction that is available is the ability to raise hand. Additionally, the video gallery can no longer be relocated. If you attempt to access the chat or teams icons on the left navigation menu, the meeting is minimized to a very small window within the Teams application like this:

To resolve this issues, follow these steps:
Quit Teams for work or school by right-mouse clicking on the Teams icon in the lower right-hand corner next to clock and selecting Quit from the sub-menu.
Click the up carrot (^) to show any hidden application icons. You will see another Teams icon there. Right-mouse that icon and select Quite from the sub-menu.
In File Explorer, navigate to %appdata%\Microsoft\ and delete the Teams folder.
In Windows 11, go to the Settings app and from the menu on the left select Apps.
Click on Installed apps.
In the “Search apps” text box type “Teams” and uninstall all Microsoft Teams related applications (there should be three: Teams for work or school, Teams, systems wide installer for Teams).
Reboot the Windows 11 system after all the Teams apps have been uninstalled.
Log into the system and in either Edge or Chrome go to: https://aka.ms/GetTeams
Click the “Download for desktop” tile.
Click the “Download Teams” tile under the “Teams for work or school” and run the installer.
!!!DO NOT DOWNLOAD AND INSTALL THE TEAMS FOR HOME OR SMALL BUSINESS!!!
Once the installer has been run, Teams will start normally and run as expected. This issue may return on the next Windows 11 update.