Important Points
- Enforcing Audience Detection behavior through MDM policies
- Prevent user can’t change settings (UI switcher disabled)
- Helps protect sensitive skin information from unauthorized viewers
- Ensure consistent security configuration on all managed devices
- Ideal for organizations with tight data personal and compliance requirements
In this post, we discuss Securing Sensitive Screens Through Watchdog Detection Controls using Intune Policies. With Microsoft Intune Settings Catalogadministrators now have more granular control over advanced features such as Human Presence Detection. One of these settings, Force the Audience Detection Action, ensuring sensitive screen content is protected from unwanted viewers. This policy determines whether Viewer Detection measures are enforced by the organization.
List of contents
Force Audience Detection Settings with Intune to Increase Privacy and Prevent User Change
By implementing these settings, IT teams can reduce the risk of data exposure in alarming environments due to shoulder browsing or unauthorized viewing. This is especially useful in workplaces that handle confidential data, helping to maintain privacy without user intervention.
Create a Profile in Intune
Entered into Microsoft Intune Admin Center using your admin account. From the left menu, go to Devices and select it Configuration profile. Click Create profile to get started a new policy. Choose Windows 10 and later as the platform. Choose Settings catalogue as profile type. Finally, click Make option to continue.
Basic Tab
The Basics tab is fastest step. Here, you need to enter basic details like NameDescription, and Platform information. Since the platform is already set to Windows, you just need to provide a specific name and description for the policy, then click Next.


Configuration Tab
The next step is Configuration settings; there, you can search for it + Add Settings. When you click + Add settings, You will get a settings selector window. There, you can search for Human Presence, then in the category select the policy name Forced Audience Detection Measures.

Failed Policy State
The policy’s default state is User Select Default. This means that if a policy is not explicitly set by the admin, Windows will defer to the user’s privacy or screen protection preferences rather than implementing a specific action such as Force Notify or Force Dim and Notify

Force Notify
When Forced Audience Detection Measures policy is set to Force NotifyWindows will do it just remind the user when a viewer is detected, and it is detected No dim or blur the screen. If set to Force Notification, the screen itself remains normal (does not dim or blur). Select a mode and click Next.

That Coverage tag page helps control who can view or manage this policy aligned. If your organization uses scoped tags, choose the appropriate tag based on your admin role or department. Coverage tags are useful in large environments with many IT teams. If you organization If you don’t use scope tags, you can leave this part out.
- It’s me Pass this part

Tasks Tab
In Task page, decide which devices or users should accept this policy. Under Including group, select the required device or user group group. Setting a policy will ensure that the policy only applies to the system. Avoid assigning it to testing or excluded device unless required. Once the task is complete, click Next to continue.

Review + Create
To complete policy creation, you can review all policy details at Review + create tab. This helps to avoid mistakes and successfully configured that policy. After verifying all the details, click Make Knob. After creating the policy, you will get a success message.

Monitoring Status
To quickly configure policies and take advantage of them, sync the assigned devices in the Enterprise Portal. Open the Intune Portal. Go to Devices > Configuration > Search Policies. Here the policy is shown as succeed.

Client Side Verification
Always Remember, receive a success message during the policy spread does not necessarily confirm that the policy is being actively implemented or works as intended on the client device. To ensure that the policy has been implemented succeed configured, it is important to verify via Event Viewer. You can do this by filtering on Event ID 813 or 814, which will help you quickly find logs.
| Policy Info |
|---|
| MDM PolicyManaqer: Set policies into, Policy: (ForceOnlookerDetectionAction), Area: (Human Presence), Registration ID brand request: (EB427D85-802F-46D9-A3E2-D5B414587F63), Current User: (Device), Int: (0x2), Registration Type: (0x6), Coverage: (0x0). |

Remove Assigned Groups from Intune
To delete group of a policy, first open it Microsoft Intune Admin Center and enter. From the left menu, open it Device and then open it Configuration profile. Find the policy you want to change and click it. Open Task section and select Edit. Delete the groups that should no longer accept this policy and save the changes. After this, the policy no longer applies to the device.
- Delete a group simply stops policy for it groupbut the policy remains There is.
To get more detailed information, you can refer to our previous post – Learn How to Delete or Unassign Apps from Intune using Step by Step Guide.

Delete Policy Permanently
If the policy is no longer needed, you can delete it’s completely from aligned. Sign in to the Microsoft Intune Admin Center and open it Device > Configuration profile. Find the policy you want to delete and open it. Click three dot menu in the top corner and select Delete. The policy is now permanently removed and will not affect any devices.
For more information, you can refer to our previous post – How to Remove Allow Clipboard History Policy in Intune Step by Step Guide.

Need More Help or Have a Technical Question?
Join LinkedIn Page AndTelegram Group to get step by step guides and latest news updates. Join usMeeting Pageto participate in User group meetings. Also, join inWhatsApp Communityand itWhatsApp channelto get the latest news about Microsoft Technologies. We were thereredditas well.
Author
Anoop C Nairis a Workplace Technology solutions architect with over 25 years of experience. Microsoft Certified Trainer. Microsoft MVP from 2015 onwards for 11+ years in a row! He is a blogger, Speaker, and Founder of the HTMD Community and HTMD Conference. The main focus is on Device Management technologies such as Intune, Windows, and Cloud PC. He writes about technologies such as Intune, SCCM, Windows, Cloud PC, Entra, and Microsoft Security.
PakarPBN
A Private Blog Network (PBN) is a collection of websites that are controlled by a single individual or organization and used primarily to build backlinks to a “money site” in order to influence its ranking in search engines such as Google. The core idea behind a PBN is based on the importance of backlinks in Google’s ranking algorithm. Since Google views backlinks as signals of authority and trust, some website owners attempt to artificially create these signals through a controlled network of sites.
In a typical PBN setup, the owner acquires expired or aged domains that already have existing authority, backlinks, and history. These domains are rebuilt with new content and hosted separately, often using different IP addresses, hosting providers, themes, and ownership details to make them appear unrelated. Within the content published on these sites, links are strategically placed that point to the main website the owner wants to rank higher. By doing this, the owner attempts to pass link equity (also known as “link juice”) from the PBN sites to the target website.
The purpose of a PBN is to give the impression that the target website is naturally earning links from multiple independent sources. If done effectively, this can temporarily improve keyword rankings, increase organic visibility, and drive more traffic from search results.