DSPM for AI and Copilot Exposure

Quick Answer: DSPM for AI in Microsoft Purview discovers AI activity and highlights sensitive data touched by Copilot and other AI apps so admins can apply protective policies. Copilot only retrieves data the user already has permission to access via Microsoft Graph — fixing oversharing is the critical pre-deployment step.

DSPM for AI Defined

Data Security Posture Management (DSPM) for AI is a Microsoft Purview capability purpose-built for the AI era. It helps organizations:

1. Discover AI application usage — Microsoft 365 Copilot, Copilot Studio agents, and third-party AI tools connected to organizational data.
2. Identify sensitive data involved in AI interactions — which SITs appear in prompts, responses, or retrieved documents.
3. Recommend and apply policies — suggest DLP, labeling, or access remediation to reduce AI-related data risk.
4. Maintain posture over time — continuous visibility as AI adoption scales.

Think of DSPM for AI as the risk dashboard for AI data exposure — not an identity tool and not a replacement for Conditional Access.

What DSPM for AI Is NOT

AB-900 distractors often overstate the tool:

On the Exam: DSPM for AI = visibility + policy guidance for AI data risk. Pair it with DLP, labels, and permission remediation.

How Copilot Accesses Organizational Data

Microsoft 365 Copilot is not a privileged crawler with unlimited tenant access. Its data path:

1. Signed-in user context — every query runs as the user, not as a service account.
2. Microsoft Graph — Copilot requests content through Graph APIs honoring existing permissions.
3. Semantic index — a pre-built, meaning-based map of organizational content that improves relevance beyond keyword search.
4. Sensitivity labels & DLP — additional gates applied to matched content.

The semantic index enables Copilot to find conceptually related documents ("Q3 revenue forecast") even when exact keywords differ. Indexing respects permissions — admins cannot use the index to expose data users were not already authorized to see.

Customer Data Boundaries

Microsoft states that customer data remains within the Microsoft 365 service boundary and is not used to train foundation models for other tenants. Copilot processing occurs within the tenant's compliance and residency commitments. AB-900 may test this against false claims that customer prompts train public models or are published externally.

SharePoint Oversharing and Copilot Risk

The highest-impact governance gap for Copilot is SharePoint oversharing:

• "Anyone" sharing links on confidential libraries.
• Inherited permissions granting entire company access to HR or M&A sites.
• Stale guest accounts retaining access to sensitive teams.

Because Copilot honors permissions, a user with accidental access to a confidential file can ask Copilot to summarize it — natural language makes discovery easier than manual browsing. Oversharing remediation is the primary SharePoint action before broad Copilot rollout.

Data Access Governance Reports

SharePoint Data Access Governance reports (and related advanced management tooling) show:

• Who can access each site and library.
• Overshared content and inactive sharing links.
• Sites with excessive external sharing.

Administrators remediate permissions, apply default sensitivity labels to sites, and remove stale links — then validate with a Copilot pilot.

Restricted SharePoint Search (Short-Term Control)

Restricted SharePoint Search lets administrators define an allow list of sites eligible for organization-wide search and temporary Copilot grounding. It is a short-term bridge while permissions are audited — not a permanent governance strategy. AB-900 treats long-term reliance on restricted search as a trap answer.

DSPM for AI Workflow

A typical DSPM for AI assessment sequence:

DSPM insights feed the same remediation tools covered elsewhere in this chapter — labels, DLP, permission fixes — rather than introducing a separate protection technology.

Worked Scenario: Oversharing Before Rollout

A financial services firm plans tenant-wide Copilot. DSPM for AI reports heavy Copilot pilot usage retrieving files from a SharePoint site with "Everyone except external users" access containing client portfolio data. The exam-correct response order:

1. Remediate oversharing — tighten site permissions and remove broad links.
2. Apply sensitivity labels with encryption to portfolio documents.
3. Enable DLP on Copilot location for financial SITs.
4. Use Communication Compliance for regulatory language in prompts.
5. Expand rollout after Data Access Governance reports show reduced exposure.

Answers suggesting "make all sites public" or "disable audit logging" are anti-patterns.

Responsible AI Connection

DSPM for AI operationalizes Microsoft's Responsible AI principles — especially privacy and security and transparency — by giving administrators evidence of how AI touches sensitive data. It supports accountability when leadership asks, "What is Copilot doing with our regulated data?"

Study Checklist

• Define DSPM for AI and its three discovery goals.
• Explain Copilot's Graph + semantic index data path.
• State the customer data boundary training claim (what Microsoft does not do).
• Describe SharePoint oversharing risk and remediation tools.
• Explain when Restricted SharePoint Search is appropriate (short-term only).