Microsoft Purview: Retirement of Data Security Posture Management (DSPM) classic and DSPM for AI classic experiences
Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.
Action date
Microsoft tags this a retirement but gives no action date in the notice metadata. Any date is in the text below.
- Microsoft's start date
- 28 Sep 2026
- Last changed by Microsoft
- 28 Sep 2026
- First seen here
- 19 Oct 2026
- Versions seen
- 1
What the notice says
Microsoft's text, with its sections, lists and tables; source markup removedWhat and why
Beginning November 30, 2026, Microsoft will start retiring the Microsoft Purview Data Security Posture Management (DSPM) classic and DSPM for AI classic experiences. Retirement will be completed by December 31, 2026.
As part of our continued investment in Microsoft Purview Data Security Posture Management, we have unified DSPM capabilities into a single experience that helps organizations discover, protect, and investigate data risks across traditional data sources and AI applications and agents.
Rollout schedule
- Retirement (Worldwide, GCC, GCC High, and DoD): Beginning in late November 2026 and expected to complete in late December 2026
Impact on your organization
Who is affected
- Organizations currently using DSPM classic or DSPM for AI classic in the Microsoft Purview portal
- Microsoft Purview administrators
- Security administrators and compliance administrators responsible for monitoring and managing data security posture
Platforms and services
- Microsoft Purview portal
- Microsoft Purview Data Security Posture Management (DSPM)
- Microsoft Purview DSPM for AI (classic)
- Microsoft Purview DSPM (classic)
What will happen
- DSPM classic and DSPM for AI classic experiences will no longer be available after retirement.
- Organizations must use the current Microsoft Purview DSPM experience for posture management and investigation workflows.
- The current DSPM experience provides centralized access to posture metrics, recommendations, reports, investigations, and data security objectives.
- Most new DSPM capabilities and innovations are delivered through the current DSPM experience.
- Organizations that have already transitioned to the current DSPM experience and no longer rely on DSPM classic or DSPM for AI classic do not need to take action.
Action required and recommendations
Action is required only if your organization currently uses DSPM classic or DSPM for AI classic.
Recommended actions:
- Review your current DSPM workflows and identify any processes that depend on DSPM classic or DSPM for AI classic.
- Confirm access to the current DSPM experience by navigating to Microsoft Purview portal > Solutions > DSPM.
- Transition any remaining workflows that rely on DSPM classic or DSPM for AI classic to the current DSPM experience before retirement.
- Notify Microsoft Purview administrators, security teams, and compliance teams about this retirement.
- Update internal documentation, training materials, operational procedures, and help desk guidance.
Learn more
- Learn about Microsoft Purview Data Security Posture Management (DSPM) | Microsoft Learn
- Map tasks that you used to do in Microsoft Purview Data Security Posture Management (DSPM) for AI | Microsoft Learn
Compliance considerations
| Question | Answer |
|---|---|
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? | Administrators will no longer use DSPM classic or DSPM for AI classic experiences and will instead use the current unified DSPM experience for posture monitoring, reporting, recommendations, investigations, and objectives. The capability remains available but through a different experience. |
What changed
Between the versions this installation saw, newest firstThis installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.