Additional meeting and call-related features and issues within Microsoft Teams for business
Dear @Fordham Tucker,
Thank you for reaching out to the Microsoft 365 Q&A forum. Being able to adjust your camera zoom is a key feature for professional meetings, and Microsoft Teams supports this through several integration layers with Logitech hardware.
To help me narrow down the cause, could you please provide the following details?
- What specific model of Logitech camera are you using?
- Are other functionalities (like pan and tilt) working as expected?
- Have you tested zoom in other applications (like Zoom or Skype) to see if the problem is specific to Teams?
In the meantime, please try the following official troubleshooting options which usually resolve issues with basic issues:
Step 1: Native Teams device settings
You can often access basic zoom controls directly within the app:
- Before a meeting: Click the Settings > Devices.
- Select Open camera settings.
- In the properties window, look for the Camera Control tab to adjust the Zoom slider.
Step 2: Far end camera control (FECC)
(Please note that if you are a user you will need to ask your global administrator to perform these steps)
For professional-grade Logitech devices (such as the Rally Bar or MeetUp), Teams supports Far End Camera Control. This allows users to control Pan-Tilt-Zoom (PTZ) functions directly through the Teams interface.
Before starting, ensure you have the Microsoft Teams PowerShell module installed. If you haven't installed it yet, run this command in PowerShell as an Administrator:
Install-Module -Name MicrosoftTeams -Force –AllowClobber
Open PowerShell as an Administrator and run the following command to sign in to your tenant:
Connect-MicrosoftTeams
First, see what the current setting is for your organization’s default policy:
Get-CsTeamsMeetingPolicy -Identity Global | Select-Object TeamsCameraFarEndPTZMode
- Disabled: Means no one can control the zoom remotely.
- AutoAcceptAll: Means users can control the camera zoom.
You can either modify the Global (default) policy, so it applies to everyone or create a specific policy for certain users.
To update the Global policy for everyone:
Set-CsTeamsMeetingPolicy -Identity Global -TeamsCameraFarEndPTZMode AutoAcceptAll
To create and assign a "Pro User" policy (Optional): If you only want specific people to have zoom control:
Create the policy:
New-CsTeamsMeetingPolicy -Identity "ProCameraPolicy" -TeamsCameraFarEndPTZMode AutoAcceptAll
Assign it to a user:
Grant-CsTeamsMeetingPolicy -Identity "******@yourcompany.com" -PolicyName "ProCameraPolicy"
Run this command to ensure the setting has been updated:
Get-CsTeamsMeetingPolicy -Identity Global | Select-Object TeamsCameraFarEndPTZMode
Note:
- Propagation Time: Please note that changes made via PowerShell can take up to 24 hours to reflect across all users in the Microsoft 365 tenant.
- Hardware Requirement: This command only works if the Logitech camera (e.g., Rally, MeetUp, Group) is Teams Certified and supports PTZ hardware commands.
- User Interface: Once active, users will see the Pan-Tilt-Zoom controls in their Device Settings sidebar during a live meeting.
Example:
Step 3: Use dedicated Logitech software
For the most reliable control, we recommend using Logi Tune or Logitech G HUB. These applications run alongside Teams and allow you to:
- Set a default zoom level that remains consistent across all calls.
- Enable Auto-framing (RightSight), which automatically zooms to keep you centered.
Step 4: Hardware and system check
- Certification: Ensure your camera is Teams Certified. Certified devices have built-in drivers that communicate perfectly with Teams' zoom features.
- Connection: Ensure the camera is plugged into a high-speed USB port (USB 3.0 or higher is recommended for PTZ cameras).
- Updates: Check that your camera firmware and your Teams app are updated to the latest versions to ensure all hardware features are unlocked.
The zoom functionality is a result of the "Handshake" between Logitech’s hardware and Microsoft's software. If the zoom is not working, it is usually because this handshake is being blocked by a policy setting or an outdated driver.
Please note that as a forum moderator, I don’t have access to backend tools or internal systems to investigate further, and certain settings or configurations are managed exclusively by your organization’s administrators, so I’m unable to check or make changes on that side. That said, I truly hope these suggestions help you move forward.
Please let me know if you have any further questions or if the problem persists after trying these solutions. Thank you for your patience and cooperation.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.