Microsoft handed IT administrators a powerful new tool on June 12, 2026. Tucked inside Windows 11 Release Preview Build 28000.2333 is a Group Policy setting that standardizes how the operating system handles multiple applications accessing a camera at the same time. No more pleading with users to close one app before opening another, or guessing why a camera feed dropped mid-meeting. The Configure Camera Options policy puts camera behavior squarely under administrative control.

For the first time, organizations can enforce either AutoShare (allow concurrent camera access) or SafeMode (strip out OEM camera plugins and hardware acceleration) across fleets of managed devices. The policy is not just a toggle buried in the Settings app. It lives in Group Policy and Microsoft Intune, exactly where enterprise configuration belongs.

The Policy at a Glance

The new setting appears under Computer Configuration > Administrative Templates > Windows Components > Camera > Configure Camera Options. It is a device-scoped integer policy, meaning it applies to the PC, not the signed-in user. Three values define its behavior:

  • 0 – Disabled (default): The policy does nothing. Windows leaves camera mode decisions to the system and applications.
  • 1 – AutoShare: Multiple applications can access the camera stream simultaneously. This is the productivity setting—useful when, say, a video conferencing app needs to share the feed with an accessibility tool or a compliance recording application.
  • 2 – SafeMode: The camera runs in a basic mode, bypassing OEM and independent hardware vendor (IHV) plugins and disabling hardware acceleration. Microsoft positions this as a troubleshooting and stability option, not a recommended everyday configuration.

Critically, Microsoft documents this policy as available on Windows 11 version 24H2 (build 26100) and later, including Pro, Enterprise, Education, and IoT Enterprise editions. The promotional spotlight on Build 28000.2333 might suggest the feature is exclusive to the upcoming 26H1 release, but the policy engine has been ready for months. That means organizations still running 24H2 or the 25H2 release can start testing immediately—no major upgrade required.

Who This Affects

If you manage a handful of Windows 11 PCs with Intune or Group Policy, this news lands differently than if you’re a home user. Here’s the breakdown.

For IT administrators: You now have a declarative way to align camera behavior with business policy. Before today, simultaneous camera use was left to chance: an app might request exclusive access, or a system prompt might confuse an employee mid-call. With AutoShare pushed through policy, you can ensure that two sanctioned applications work together without user intervention. Conversely, if a camera model keeps glitching in a particular workflow, SafeMode helps you isolate whether the problem is a vendor plugin or the core camera stack. The policy also streamlines compliance documentation—every device in scope has a known camera mode, not a guess.

For end users: If your IT department chooses not to enforce a policy, nothing changes. You still control camera access per application through the usual privacy settings. If the policy is set to AutoShare, you might notice fewer interruptions when opening a second app that uses the camera—but you may also lose the heads-up that another program is watching. That’s a privacy trade-off that responsible rollout should address with clear user communication. SafeMode may degrade camera quality or disable vendor-specific effects, so employees should understand why it’s active and how to report issues.

For developers: Camera-aware applications should test their behavior under both AutoShare and SafeMode scenarios. An app that assumes exclusive camera control could fail silently when forced to share the stream. Conversely, an app that relies on OEM processing pipelines (such as background blur or auto-framing) might lose those capabilities in SafeMode. The policy introduces a new configuration matrix that warrants a spot in your compatibility test plans.

Why Centralized Control Matters Now

Windows has supported multi-app camera access in limited forms for several releases, but the capability was never centralized. The first inklings appeared in 2023 when Microsoft introduced the concept of “camera sharing” for certain insider builds. At the time, you could enable the feature per device via a hidden registry key or a PowerShell script—fine for a developer but hopeless for a fleet. Predictably, adoption stalled in enterprises that rely on standard management tooling.

Simultaneously, the number of applications that demand camera access exploded. Video meetings became the default collaboration mode. AI-powered tools—from gesture recognition to continuous wellness monitoring—proliferated. Background blur, eye contact correction, and automatic lighting adjustments each tapped into the camera pipe in their own way. The result was a growing stack of demands that often conflicted. An employee switching from Teams to a corporate training app might find the camera “in use” and fail to start a session. Help desk tickets piled up with no consistent fix.

The Configure Camera Options policy solves this by making camera concurrency an administrative choice. It sits alongside other device governance controls, so IT can apply it to a small pilot group, monitor for anomalies, and scale up with confidence. Organizations that already use Group Policy to manage power settings, Windows Update rings, or Microsoft Edge configurations will find the same deployment rhythm.

Microsoft’s timing is also telling. The policy lands in a Release Preview build for 26H1, a Windows version the company describes as “a targeted release for specific silicon,” notably Qualcomm Snapdragon X2 Series devices. Broadly upgrading a 24H2 fleet to 26H1 just for this feature would be wasteful—and Microsoft itself advises against it. The policy works on current mainstream builds, so the smart play is to deploy it on the hardware already in hand.

How to Deploy the Policy

A policy sitting in documentation doesn’t fix anything. Here are the concrete steps to get Configure Camera Options into a pilot ring.

Via Group Policy

This is the simplest path for domain-joined devices or local tests.

  1. Open the Group Policy Management Console (or Local Group Policy Editor for a single device).
  2. Navigate to Computer Configuration > Administrative Templates > Windows Components > Camera.
  3. Double-click Configure Camera Options.
  4. Set the policy to Enabled and choose a mode: AutoShare (1) or SafeMode (2).
  5. Link the policy to an organizational unit containing your pilot devices. A computer reboot or a gpupdate /force is not strictly required for the initial test, but a restart ensures no lingering camera state.

Via Microsoft Intune

The setting is not yet a one-click toggle in the Settings Catalog, so you’ll need a Custom Device Configuration profile.

  1. In the Intune admin center, go to Devices > Configuration > Create > New policy.
  2. Choose Windows 10 and later as the platform, then Custom as the profile type.
  3. Add a setting with these exact values:
    - Name: ConfigureCameraOptions - AutoShare
    - OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Camera/ConfigureCameraOptions
    - Data type: Integer
    - Value: 1 (for AutoShare; use 2 for SafeMode)
  4. Assign the profile to a pilot device group. Never assign both AutoShare and SafeMode profiles to the same device—they are mutually exclusive values for one policy.
  5. Monitor deployment status under the profile’s Device status report. Once successful, move on to validation.

Rollback

Reverting is equally straightforward. In Group Policy, set the Configure Camera Options policy back to Not Configured or Disabled (value 0). In Intune, change the custom OMA-URI value to 0 or remove the profile. Always verify that no other policy is simultaneously delivering the setting—a common mishap in hybrid environments with overlapping GPOs and Intune profiles.

Validate the Camera Workflow

Deploying a policy is not the same as proving the camera works. After the policy hits a test device, run through this checklist:

  1. Confirm the device is on Windows 11 build 26100 or later and has received the intended policy (check rsop.msc or MDM diagnostics).
  2. Close every application that might be holding the camera.
  3. Open your first approved camera app (e.g., Microsoft Teams) and start a video session.
  4. Open the second approved app (e.g., a company-mandated attendance tracker) and select the same camera.
  5. Verify both apps deliver usable video without crashing or blank screens.
  6. Repeat the test under normal user conditions, not just an admin session.
  7. If testing SafeMode, compare the feed quality against the AutoShare baseline. Document any loss of features like background blur that your business relies on.

Record the device model, camera hardware, OS build, and assigned value for every test. Patterns will emerge: certain webcams may behave flawlessly in AutoShare while others stutter. That data fuels your rollout decisions.

The Privacy Layer AutoShare Doesn’t Provide

AutoShare is a technical plumbing change, not an access-control list. It does not decide which applications may use the camera—only whether multiple can do so at once. Without careful handling, an employee could accidentally consent to a rogue app that grabs the feed while a legitimate meeting is running. The camera privacy light may be the only indicator, and that’s easy to miss when a dozen windows compete for attention.

Responsible deployment means coupling the policy with governance:

  • Define a shortlist of business-justified applications that are allowed to share the camera concurrently.
  • Inform users what simultaneous camera use looks like and how to report unexpected access.
  • Consider auditing camera access events through Microsoft Defender for Endpoint or a third-party SIEM if your compliance framework demands it.
  • Use SafeMode only for diagnostics, not as a blanket “security” mode; it still enables sharing and may degrade the user experience.

For organizations that need to disable cameras entirely, this policy is not the answer. Look instead at the separate Allow camera policy (under Camera device restrictions), which blocks all camera hardware.

What’s Next

The Configure Camera Options policy is a foundation, not a finish line. Microsoft has been steadily layering device management controls into the Camera stack over the past 18 months. Expect per-app camera allowlists, more granular plugin management, and reporting endpoints in future Windows releases. The company’s investment in the NPU and AI-driven camera features will only intensify the need for centralized oversight. A feature that uses the camera for real-time sentiment analysis or hands-free control in a factory setting can’t be left to local user preference.

For now, the immediate to-do is clear: carve out a pilot ring of a dozen devices, apply AutoShare on a handful and SafeMode on a few more, and run your critical workflows. The policy is live, it’s free on existing supported builds, and it solves a real pain point that has festered since the pandemic cemented video-first work. The next time a camera-sharing ticket lands in the queue, you’ll have a button to press—and that’s a welcome change.