Microsoft released a Group Policy setting in Windows 11 26H1 Release Preview build 28000.2333 on June 12, 2026, giving administrators centralized control over whether multiple applications can share a camera simultaneously. This change closes a critical management gap for kiosks, telehealth stations, and shared PCs, but comes with a major caveat: 26H1 is only for new hardware, not existing Windows 11 fleets. That means this enterprise-ready feature is an upgrade tied to your next hardware refresh, not a software update you can push to current devices.
What Actually Changed
The new policy – Configure Camera Options – lives under Computer Configuration > Administrative Templates > Windows Components > Camera in both local and domain Group Policy Objects. It offers two modes:
- Multi-App Camera: Allows multiple permitted applications to access one webcam stream simultaneously. This is the feature Microsoft first previewed in December 2024.
- Basic Camera: Simplified functionality for troubleshooting or when a camera misbehaves. It can also serve as the default for devices that don’t need concurrent access.
Before this policy, Multi-App Camera was a user-facing toggle buried in Windows 11’s advanced camera settings. Anyone with physical access could change it, and the setting would not necessarily survive a reboot or a different user’s sign-in. For a reception terminal, a remote medical exam station, or a training-room PC, that was a non-starter. The new Group Policy moves the decision from the endpoint to the administrator, and it sticks.
The policy arrived in a Release Preview build, not the initial Windows 11 26H1 release that went GA on February 10, 2026. As of now, it is documented in build 28000.2333 and rolling out to Beta and Release Preview channels alongside Camera app version 2026.2605.7.0 (June 24 update). However, it is not yet confirmed in the final production image that OEMs will ship. IT teams should verify the policy’s presence on any potential new 26H1 device before standardizing on it.
What It Means for You
For IT Administrators
This is a long-overdue management control. Shared and kiosk-style PCs have relied on third-party camera utilities or simply locked down user settings to avoid camera conflicts. Now you can:
- Ensure a telehealth PC always lets the doctor’s video app and a separate imaging tool use the camera at the same time.
- Set a reception kiosk to Basic Camera mode to prevent a rogue app from grabbing exclusive camera access and confusing visitors.
- Define a consistent camera behavior across an entire OU or device group, without touching each machine.
But two points are critical. First, Multi-App Camera is not the same as Multi-App Kiosk mode. Assigned Access (the kiosk feature) restricts which apps a user can run; the camera policy determines how the camera stream is shared among those allowed apps. Both must be configured for a complete solution.
Second, Microsoft explicitly states that Windows 11 26H1 is intended for new devices and is not offered as an in-place upgrade from Windows 11 24H2 or 25H2. If your fleet is already on those releases, you cannot simply deploy 26H1 via your usual servicing ring. This is a hard stop: you can only get this policy if you’re buying new 26H1 hardware or perhaps reimaging a device from scratch (and losing existing support guarantees).
For Home Users and Power Users
The new Group Policy won’t appear on Windows 11 Home. For those on Pro or higher with local group policy access, it’s possible to set it on a standalone device, but the real scenario is enterprise management. Unless you’re running a shared family PC with unusual camera-sharing needs, this change won’t affect you.
For Developers
If you develop apps that rely on camera access, this policy means you can now test your application’s behavior in a managed Multi-App Camera environment. IT may start enforcing modes that differ from the user-facing toggle, so ensure your app gracefully handles both shared and exclusive camera access.
How We Got Here
Microsoft first demonstrated Multi-App Camera in a Windows 11 Dev Channel build (26120.2702) in December 2024, presenting an accessibility scenario where a sign-language interpreter and a live audience feed could use one camera. The capability worked, but the user-controlled setting left it impractical for enterprise.
The company then spent eighteen months sewing together the infrastructure to manage it centrally. Along the way, Windows 11 26H1 materialized as a distinct servicing branch, separate from the 24H2 and 25H2 tracks. When 26H1 reached general availability in February 2026, it did so without this policy. Only now, in a late-cycle Release Preview build, has the management layer caught up.
This timeline matters. It shows that the camera feature wasn’t baked into the base 26H1 code; it’s an add-on that arrived six months after the GA deadline. That explains why the policy is not retrofitted to earlier Windows 11 versions—and why organizations must wait for hardware that ships with the update.
What to Do Now
If you’re not planning new hardware in the next 12 months, skip this feature. Continue using your 24H2 or 25H2 devices with existing camera configurations. Monitor Microsoft’s announcements, but do not budget for a fleet upgrade solely for shared camera access.
If you are evaluating new 26H1 devices for kiosks, telehealth, training rooms, or collaboration spaces, include these steps in your acceptance testing:
- Confirm the device runs a build that includes the Configure Camera Options policy (at least 28000.2333).
- Pilot with the exact camera model and the applications that will run under Assigned Access or other lockdown methods.
- Test both launch orders: open App A first, then App B; reverse it. Confirm both get usable video.
- Test failure scenarios: close one app, restart the device, sign out and back in as the restricted kiosk user.
- Validate the fallback: switch the policy to Basic Camera and ensure it resolves any conflict—without user intervention.
- Deploy the policy to a small pilot group for at least one week before broader rollout.
Remember: Assigned Access must explicitly allow the apps your kiosk will use. The camera policy does not override app restrictions; it only controls how the camera is shared among allowed apps.
Finally, check Microsoft’s camera release notes page regularly. As this policy moves from Release Preview to production, the page will be updated. The absence of a supported-camera list or compatibility matrix means you carry the testing burden. Do not assume all webcams work with Multi-App Camera—test with your actual hardware.
Outlook
The next milestone isn’t another Insider build. It’s Microsoft confirming that Configure Camera Options has reached a stable production image, alongside at least a basic set of validated cameras. Enterprises should also watch for signs that equivalent management controls might trickle into Windows 11 24H2 or 25H2 via a future quality update. For now, the policy exists in a narrow island: new 26H1 hardware only. Plan accordingly, and don’t let a camera convenience drive an unsupported migration.