A school district IT office is auditing how Copilot and agents may expose district data. Which Microsoft Purview family should it identify for AI data-security posture?

DSPM for AI in Microsoft Purview supports understanding AI interactions with organizational data and the related data-security risks those interactions create. School district IT auditing how Copilot and agents may expose district data should identify DSPM for AI as the Purview family for AI data-security posture. Insider Risk Management reviews user activity patterns to surface potential insider risks; it is not the family built to show how Copilot and agents interact with organizational data across the tenant. Data Loss Prevention monitors content sharing and enforces protective actions on data; it does not provide the posture view of AI-data interactions that DSPM for AI provides. Information Protection applies sensitivity labels to classify organizational data assets, but labeling and classification alone do not audit or surface how Copilot and agents are interacting with that content across the district's data estate. Exam caveat: at fundamentals depth, map DSPM for AI to Copilot/agent data-exposure visibility—do not confuse it with Insider Risk Management for user activity patterns, Data Loss Prevention for sharing controls, or Information Protection for labeling and classification. Operational check: use DSPM for AI outputs to list which district repositories AI experiences touch, confirm sensitive information types involved, and close gaps with least-privilege access and Purview protection before broader agent rollout.