> ## Documentation Index > Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Explore Oversharing and Data Access Governance in SharePoint > How Microsoft Purview detects and prioritizes overshared SharePoint content and guides remediation using sensitivity labels, DLP, permissions tightening, and access governance In this lesson we examine a common, high‑impact challenge for organizations using SharePoint and Microsoft 365: oversharing. As collaboration increases, files, folders, and sites can unintentionally become available to broader audiences — increasing the risk that sensitive information is exposed. Microsoft Purview helps detect and prioritize potentially overshared content in SharePoint by evaluating multiple signals and presenting prioritized findings so administrators can remediate the highest‑impact issues first. A presentation slide titled "Oversharing and Data Access Governance in SharePoint" showing how to identify potentially overshared sites and files with icons for sensitive data, broadly shared data, and frequently accessed data. On the right it shows "Prioritize highest impact risks" with a risk assessment scale: red High Risk, yellow Medium Risk, and green Low Risk. ## Why oversharing matters Broad sharing can boost productivity, but it also increases the chance that sensitive content is accessible to people who should not see it. Even content stored in secure locations becomes risky when permissions are incorrect or overly permissive. Key reasons to address oversharing: * Prevent unauthorised exposure of regulated or confidential information. * Reduce the likelihood that in‑product assistants (like Microsoft 365 Copilot) or search features surface sensitive content to unintended users. * Focus remediation efforts on the highest business impact findings instead of manual review of thousands of sites and files. ## How Microsoft Purview evaluates oversharing Purview continuously analyzes a combination of signals to identify potentially overshared content and triage risk: | Signal | What Purview looks for | Typical action | | - | - | - | | Presence of sensitive data | Detection of sensitive data types (e.g., financial records, personal data) | Apply sensitivity labels, DLP rules | | Breadth of sharing | How widely a file, folder, or site is shared (e.g., "Everyone", external users) | Tighten permissions or revoke broad access | | Access patterns | Frequency and volume of access across users | Prioritize items with high access of sensitive content | Based on these signals Purview assigns a risk priority (High, Medium, Low) so administrators can focus on the most critical exposures. ## Example scenario — how a simple permission change creates exposure 1. Initial state: A SharePoint site contains sensitive financial information (for example, an unreleased earnings report). Access is restricted to the finance team and other authorized staff. 2. Accidental permission change: A permission edit (for example, granting access to "Everyone" or "All company") unintentionally broadens access to a much wider audience. This commonly happens as teams change and permissions are edited. 3. Rapid exposure: With the content accessible to many more users, it can be viewed frequently and appear in search or productivity tools. For example, [Microsoft 365 Copilot](https://learn.microsoft.com/microsoft-365/copilot/?view=o365-worldwide) and other in‑product experiences may summarize or surface results based on content the requesting user is allowed to view. 4. Remediation: Use governance and protection controls — tighten access back to the finance group, apply [sensitivity labels](https://learn.microsoft.com/microsoft-365/compliance/sensitivity-labels?view=o365-worldwide) or [DLP](https://learn.microsoft.com/microsoft-365/compliance/data-loss-prevention?view=o365-worldwide) policies, and use Purview findings to prioritize follow‑up actions. [Microsoft 365 Copilot](https://learn.microsoft.com/microsoft-365/copilot/?view=o365-worldwide) and related experiences only surface content a user already has permission to view. Implementing `sensitivity labels`, `DLP` rules, and Purview policies helps ensure protected content isn’t inadvertently exposed or summarized outside approved boundaries. This scenario highlights why access governance is essential: even securely stored data can become exposed when permissions are misconfigured. Microsoft Purview provides detection, impact assessment, and guidance to restore correct access and apply protective controls. ## Recommended remediation and preventive controls * Tighten permissions on overshared sites and files; remove broad or external access where unnecessary. * Apply sensitivity labels to classify and enforce handling rules for confidential content. * Configure DLP policies to block, restrict, or monitor sharing of sensitive data. * Use Purview risk priorities to sequence remediation (start with High risk findings). * Educate site owners about sharing best practices and implement automation to prevent future oversharing. To summarize: Purview identifies potentially overshared content by analyzing sensitivity, sharing breadth, and access patterns; it prioritizes findings by likely business impact; and it enables administrators to restore appropriate access and apply protective controls such as sensitivity labels and DLP. This infographic titled "Oversharing and Data Access Governance in SharePoint" shows a four-step scenario about accidental data exposure. The panels read: "A secret is kept," "A door is left open," "Word spreads fast," and "Calm is restored," each with a corresponding icon and short explanation. We will continue exploring how data protection and governance controls can be applied across Microsoft 365 to reduce exposure and automate remediation. ## Links and references * Microsoft Purview overview: [https://learn.microsoft.com/microsoft-365/compliance/microsoft-purview?view=o365-worldwide](https://learn.microsoft.com/microsoft-365/compliance/microsoft-purview?view=o365-worldwide) * Microsoft 365 Copilot: [https://learn.microsoft.com/microsoft-365/copilot/?view=o365-worldwide](https://learn.microsoft.com/microsoft-365/copilot/?view=o365-worldwide) * Sensitivity labels: [https://learn.microsoft.com/microsoft-365/compliance/sensitivity-labels?view=o365-worldwide](https://learn.microsoft.com/microsoft-365/compliance/sensitivity-labels?view=o365-worldwide) * Data Loss Prevention (DLP): [https://learn.microsoft.com/microsoft-365/compliance/data-loss-prevention?view=o365-worldwide](https://learn.microsoft.com/microsoft-365/compliance/data-loss-prevention?view=o365-worldwide) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.