There is no supported zero-cost method to deploy and enforce one corporate Teams meeting background across both managed and unmanaged users with the listed licenses; the practical no-cost option is a one-time self-service upload, while centralized publishing and enforcement require Teams Premium.
Supported no-cost approach
Distribute the approved image from a location already available to every user, such as SharePoint, and ask users to upload it once:
- Download the corporate image to the device.
- In Teams, open Calendar, select a meeting, and select Join.
- On the pre-join screen, select Effects and avatars.
- Select More video effects → Add new.
- Select the corporate
.JPG, .PNG, or .BMP file.
- Apply the background.
Teams retains the selected effect for future meetings and calls until the user changes it, so this is normally a one-time action rather than something users must repeat for every meeting.^1^
To reduce administrative effort, publish a short internal guide containing the image and these steps, then include it in onboarding. This works for Intune-enrolled and unmanaged devices because it uses the Teams client’s supported upload workflow.
Ensure the applicable meeting policy permits uploads:
- Teams admin center → Meetings → Meeting policies
- Open the policy assigned to the users.
- Under Audio & video, set Participants can use video effects to All video effects.
That setting permits custom image uploads. It does not distribute the image or force users to select it.^2^
Why Intune or Graph cannot cover the gap
Microsoft Graph does not currently provide an API for uploading or managing users’ custom Teams meeting backgrounds; the supported non-Premium workflow is upload through the Teams client.^3^
No supported Teams or Intune configuration in the available documentation distributes this image to all enrolled endpoints as a user background. Endpoint file-copy scripts would also leave the 60% of unmanaged devices uncovered. For optimized VDI specifically, Microsoft states that placing files into the user’s AppData background folder by script is unsupported—the user must upload the image through the Teams UI.^4^
Avoid treating the Teams background cache path as a supported organization-wide deployment interface. Client storage locations and behavior can vary by platform, and unmanaged devices provide no administrative delivery channel.
If centralized enforcement becomes mandatory
License affected users with Teams Premium and configure a customization policy:
- Open Teams admin center → Meetings → Customization policies.
- Create or select a policy.
- Under Meeting backgrounds, enable Use background images from my organization.
- Select + Add, upload the corporate image, and save.
- Select the uploaded image, choose Set as required, and save.
- Assign the policy to the required users.
The image must be PNG or JPEG, between 360 × 360 and 3840 × 2160 pixels. Users assigned a required preset cannot change that background. Microsoft explicitly requires Teams Premium for users who receive and use organization-managed custom backgrounds.^5^
Therefore, the available choices are:
- Zero additional licensing: one-time user upload; scalable through self-service communication but not enforceable.
- Unattended, centrally published and required background: Teams Premium for the users governed by that policy.
- Intune-only file distribution: would not satisfy organization-wide coverage and is not documented as a supported Teams background-management mechanism.
References
- Change your background in Microsoft Teams meetings | Microsoft Support
- Meeting policy settings for audio & video
- Use API to upload Teams background images - Microsoft Q&A
- New VDI solution for Teams
- IT Admins- Manage and create custom meeting backgrounds for Teams meetings