In September 2026, Microsoft will start rolling out native pan-tilt-zoom (PTZ) camera controls to Teams Rooms on Windows – and the feature will be switched on by default. That single decision means any room with a compatible camera could suddenly hand users the ability to physically redirect the meeting’s view, potentially upending the automated participant framing that many organisations have come to rely on.
What’s Changing in Teams Rooms
Microsoft is adding local PTZ controls directly into the Teams Rooms interface for Windows. The controls will let in-room participants pan, tilt, and optically zoom a connected PTZ-capable camera without leaving the meeting experience. Initially, the feature focuses on mechanical and optical movement; finer digital PTZ or crop-based controls may come later.
Crucially, PTZ controls appear only when Enhanced Framing is turned off. Enhanced Framing – the AI-driven system that automatically keeps all in-room participants visible and well-composed – and manual PTZ are presented as an either/or choice. As soon as a user disables Enhanced Framing, the camera settings screen will offer manual movement. Turn Enhanced Framing back on, and the PTZ controls vanish.
The feature is scheduled to begin rollout in September 2026, according to the Microsoft 365 Roadmap. The toggle will be located under Admin Settings > Peripherals on each Teams Rooms device, and Microsoft has confirmed the setting will be enabled by default when the update arrives. Administrators who do nothing will effectively vote for manual PTZ in every room that has a supported camera.
A critical detail tucked into Microsoft’s certification documentation: a “Certified for Microsoft Teams” badge does not mean PTZ will work perfectly, or even at all, in your environment. The program evaluates hardware design and performance, not feature-level or cloud-environment support. Your own testing on the actual room stack – including USB extenders, switching gear, and the installed firmware – becomes the final arbiter.
The Real-World Impact for Organisations
For IT administrators and AV teams, the September deadline is a policy landmine disguised as a convenience. The default-on setting will unleash manual camera control across the entire fleet unless you deliberately turn it off, room by room or via bulk configuration. That means inventorying every Teams Rooms device, its camera model and firmware, and then applying a global policy that reflects how each space is actually used.
The risk isn’t just technical incompatibility. In rooms designed around automated framing – typical huddle spaces and mid-sized conference rooms where people walk in, join a call, and expect the tech to handle the picture – manual PTZ invites trouble. A well-meaning employee could zoom in on the whiteboard, then leave the camera pointing at an empty chair for the next meeting. A remote attendee might find themselves staring at a wall because someone tried to adjust the angle and gave up. These are not edge cases; they are predictable outcomes when a controllable camera lands in front of users who never asked for the feature.
For everyday meeting participants, the change may feel like a surprise new button. In rooms that keep the default, the first person who pokes around in Camera settings could unintentionally disable Enhanced Framing and start moving the lens. Without clear in-room instructions – and perhaps even a designated camera operator – the result will often be worse video for everyone dialling in remotely. In rooms where administrators have wisely disabled PTZ, nothing changes; users simply continue enjoying automated framing.
For remote attendees, the impact is entirely downstream. When a room’s camera is manually mishandled, they see the poor framing, not the cause. Over time, inconsistent video quality across different rooms within the same company can erode trust in hybrid meetings and turn every call into a troubleshooting session. Organisations that leave PTZ on everywhere without a plan will likely see an uptick in helpdesk tickets about “bad camera views” that are really configuration problems, not hardware failures.
There is also a brighter side. In spaces where someone is actively directing the camera – training rooms with a lectern, auditoriums with a stage, demonstration labs, executive briefing centres – manual PTZ can deliver a better, more intentional video experience than any AI can. The presenter or room operator can frame exactly what matters, avoid reframing distractions when someone walks through the background, and use optical zoom to show fine detail. These rooms are the reason the feature exists, and for them, the new default is a genuine upgrade.
How We Got Here: From AI Framing to Manual Override
Teams Rooms on Windows has long leaned on automated intelligence to manage cameras. Enhanced Framing, introduced several years ago, uses on-board AI to detect and frame participants. More recently, Microsoft has been building Enhanced IntelliFrame for certified AI-capable cameras, turning the camera system into a core Teams Rooms Pro feature rather than a peripheral afterthought. The promise has been consistent: walk into a room, and the system handles the video.
But the demand for manual PTZ never disappeared. In many education, healthcare, and government settings, the ability to steer a camera toward a specific person, object, or area is non‑negotiable. Third‑party integrations and workarounds filled the gap, but they added complexity and broke the seamless Teams Rooms experience. Native PTZ controls are Microsoft’s answer to that sustained feedback.
The decision to enable the controls by default, however, seems aimed at discoverability rather than operational wisdom. By making PTZ immediately visible, Microsoft ensures that admins and power users in operator‑led rooms don’t have to hunt for a hidden toggle. But it simultaneously imposes manual control on every general‑purpose collaboration space – a blunt‑instrument approach that flips the burden from “opt in” to “opt out.”
Microsoft’s own certification disclaimer highlights the gap between lab validation and real‑world use. The Teams Devices Certification Program confirms that a camera meets audio, video, and UI quality bars. It does not confirm that the camera’s PTZ functions correctly with the specific firmware, USB path, and room control processor in your deployment. That validation is left entirely to the customer.
What Admins Must Do Between Now and September 2026
The window to act is open but finite. A deliberate, tested policy beats a rushed post‑rollout scramble every time. Here is a practical checklist:
- Inventory every Teams Rooms device – model, active camera, connection type, and installed camera firmware.
- Identify each room’s operational profile. Is it a general collaboration space that depends on Enhanced Framing, a presenter‑led room where manual PTZ adds value, or a complex multi‑camera space that needs individual design review? Assign a provisional category.
- Check the Microsoft certified‑peripherals catalogue for the camera model and its listed certified firmware baseline. Compare with the actual firmware running in the room.
- Test with Enhanced Framing on and off. In a controlled test meeting, turn off Enhanced Framing and verify whether PTZ controls appear under Camera settings. Exercise pan, tilt, and optical zoom. Watch for lag, jerky movement, or failure to respond.
- Test recovery scenarios. After moving the camera, re‑enable Enhanced Framing: does the system reframe automatically, or does the camera stay stuck in the last manual position? Reboot the room system and camera separately, then together, to catch USB enumeration or startup‑order glitches.
- Involve real users. Don’t rely on an empty‑room preview. Have someone join a live Teams meeting from the room and adjust the camera, then ask a remote participant to assess the experience.
- Document the room’s policy. Based on the test results and the room’s purpose, decide whether PTZ stays enabled or is disabled. Record the decision in your room inventory or configuration management database.
- Prepare in‑room guidance. For rooms where PTZ remains enabled, print clear instructions on how to access the controls, when to use them, and – critically – how to restore Enhanced Framing before ending the meeting.
- Configure the setting before the rollout hits. Microsoft gives you the toggle under Admin Settings > Peripherals. Set it per device according to your policy, so that on Day One of the feature’s availability, each room is already in its intended state.
- Brief your helpdesk. Train support staff on the distinction: “PTZ controls are missing” is often because Enhanced Framing is on. “Automated framing stopped working” can be because someone turned it off. Having standard triage steps avoids unnecessary escalations.
For multi‑camera rooms – those using the multiple‑camera view feature with Teams Rooms Pro – the policy decision needs extra care. Microsoft’s documentation states that multi‑stream intelligent cameras are unsupported in a multi‑camera configuration. If your large space uses several single‑stream cameras, enabling PTZ on one of them could undermine the entire multi‑camera layout. Treat these rooms as a separate design review, not as a checkbox on a spreadsheet.
Looking Ahead: The Future of Camera Control
Microsoft has framed this rollout as a starting point. Support for additional PTZ capabilities – digital zoom, presets, tracking – could arrive in subsequent waves. As AI‑driven camera intelligence continues to deepen, the line between automated and manual control will likely blur further, with systems that can hand off smoothly between operator and AI based on context.
The September 2026 change is an operational decision more than a technological one. The tools will work; what makes the difference is whether organisations take the time to map those tools to actual human workflows. Rooms that are never meant to be touched should have PTZ disabled before users discover it. Rooms that need intentional framing should be prepared with clear roles and runbooks. The default is just a default – but it becomes policy the moment nobody changes it.