I'm trying to distribute a company-branded background image to users without purchasing the premium feature. I deployed a Win32 app that runs a PowerShell script, and Intune reports that the app completed successfully, but the image doesn't appear in Teams. Is there a reliable way to install the image for the new Teams client, and can it be selected or enforced automatically?
3 Answers
For the new Teams client, place the image in the user-context folder `%localappdata%PackagesMSTeams_8wekyb3d8bbweLocalCacheMicrosoftMSTeamsBackgroundsUploads`. The image usually needs a GUID-style filename, plus a thumbnail using the same name with `_thumb` appended. A deployment running as system may copy the files successfully but still fail because Teams looks in the signed-in user’s profile. Active Setup or another user-context method can help, although Microsoft could change this path in a future update.
A successful Win32 deployment only confirms that the script ran and copied files; it doesn’t mean Teams registered the background. Also verify whether the device has new Teams or the classic client, since their package locations differ. Even when the files appear correctly, users may still need to open the background picker and select the image manually.
Without Teams Premium, you generally can’t centrally enforce a background or set it as the default. The practical workaround is to copy the image into each user’s Teams upload folder and have users select it themselves.
That was my original approach, but Teams isn’t detecting the image after the script runs.