Cannot deploy Custom backgrounds for Teams in VDI environment
We have detected (or so we think) a malfunction in Teams on VDI when attempting to deploy Teams backgrounds that should be available to users for their video calls. The only article that documents how to do this is the following: https://learn.microsoft.com/en-us/microsoftteams/custom-meeting-backgrounds It clearly states that the path where custom Teams backgrounds are stored is in the user profile, specifically in the folder: %LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Backgrounds\Uploads Expected Process The process is not direct, but it is straightforward. Using a script, a UUID is generated, which is used to create two image files (JPG, BMP, or PNG format, depending on the original image). For example, if the original is a JPG: UUID.JPG UUID_thumb.JPG These two files are copied to the path above, and on the next Teams session startup they should be available to the user. ✅ This works correctly in physical (non-VDI) environments. Tested many times without issues. What We Have Observed in VDI Even when the file pair is copied to the correct path within the user's FSLogix profile, the image does not become available in the Teams client — even after restarting Teams multiple times or even the VDI session itself. After each restart, the files are confirmed to be persistent and located at the correct profile path.[ %LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Backgrounds\Uploads folder contents] When a background image is added manually through the Teams UI, a folder is created in OneDrive called "Microsoft Teams User Custom Video Backgrounds". If additional images are manually added to that OneDrive folder, they do not appear as available in Teams. This leads us to believe that the upload process performs additional operations in the registry or other configuration locations beyond simply copying the file. A ProcMon capture was performed, but after an initial superficial inspection, it was not possible to determine exactly what is happening under the hood.NEW Teams Feature: Test Your Mic & Speaker BEFORE Joining a Meeting!
🎙️ No more "Can you hear me?" moments in Microsoft Teams! Microsoft just rolled out a small but genuinely useful feature: you can now test your microphone and speaker directly from the Teams pre-join screen — before you even enter the meeting. ✅ Test your speaker with a quick tone ✅ Record and play back your mic ✅ Get a green checkmark confirming you're ready to join No more digging through Settings > Devices > Make a test call every time. Have you tried it yet? Let me know in the comments if this feature has saved you from an awkward audio moment in a meeting 👇 #MicrosoftTeams #Microsoft365 #TeamsUpdate #Productivity #RemoteWork #M365Insider
SharePoint document set as Teams Tab
I been testing adding folders as a team tab and these work fine. Also, adding a library that contains document set's also works fine and the document sets seem to browse and operate as expected. When adding a document set URL it produces the error below. The same exact process with a folder works. It's a bit surprising this does not work as the document sets do work when adding the entire library however a specific document set like adding a folder does not work. Any feedback is appreciated.
Cross-Tenant Shared Meeting Room Spaces
We have two M365 tenancies under our group. We need to allow users from both tenants to use Meeting room resources (book rooms, use calendars etc..). Is this just about configuring Exchange OR Sharing in EXO or do we need anything beyond that to facilitate Teams meeting room resource sharing? Would we also need to sync these meeting room objects across tenancies to allow users to see them in GAL etc.. ? Thank you!
Still Cannot Bulk Add People or Groups in Team/Channel in 2026
It's 2026, still same issue. As a regular user/leader of a large team (hundreds of people), we still cannot bulk add people in Team/Channel. It's frustrating to add one people at a time. This has been brought up in 2020, 6 years after, same issue. teams and bulk adding of members | Microsoft Community Hub No real resolution.Assign a phone number for user using Direct Routing
Hello, I have setup a trunk for direct routing. I think I have all the proper licensing in place for my user, ie: phone system and calling plan. I am now trying to assign a phone number however the phone number type drop down ( in the general information section of my user in teams admin ) does not have the direct routing option. The only option given is Calling Plan. I want to use number that is on the Direct Routing trunk, not a Calling Plan number. How can I make it so Direct Routing is an option under Assign Phone number -> Phone number Type?
