Windows App Permissions: Review Access by Capability

Use Windows app-permission pages to decide which apps may use a capability. Do not assume those lists cover every desktop program or every route by which data can be accessed.

On this page
  1. Make a capability inventory
  2. Review permissions rather than enabling a blanket preset
  3. Understand the coverage limit
  4. Questions and answers

Make a capability inventory

CapabilityKeep access forCheck after restricting it
MicrophoneYour intended calling or recording appA local recording or test call.
CameraYour chosen video or capture appPreview in the relevant application.
LocationFeatures that actually need precise locationThe specific location-dependent feature.
Contacts or calendarApps you intentionally use with that dataWhether the expected item can still be opened.

Review permissions rather than enabling a blanket preset

  1. Open Privacy & security on Windows 11 or Privacy on Windows 10. Select the capability, not just the application name.
  2. Distinguish a device-wide access switch from per-app choices and any desktop-app control.
  3. Restrict an app you do not want to use the capability, then check a permitted app still works.
  4. For browser-based services, also review the website permission in the browser.

Understand the coverage limit

Microsoft notes that some desktop applications have broad system access and are not controlled by every item in these lists. Installation source, application permissions, account access, and the vendor’s privacy practices still matter. A short list of enabled apps is not evidence that all other software is sandboxed.

Questions and answers

Why is my desktop application absent from the list?

Some desktop applications are not represented as individually controllable Store-style app entries.

Can Windows allow a browser while the website stays blocked?

Yes. Windows capability access and a website’s browser permission are separate layers.

Sources and further reading