MC1481315 - Microsoft Purview: Retirement of Data Security Posture Management (DSPM) classic and DSPM for AI classic experiences

Message Center

Summary

Microsoft will retire Microsoft Purview DSPM classic and DSPM for AI classic experiences by late March 2027, unifying capabilities into a single current DSPM experience. Organizations using the classic versions must transition workflows and update documentation accordingly; no action is needed if already using the current DSPM.

Discussionpowered by zap.ms

Last Updated

Oct 30, 2026

Published Sep 28, 2026

View version history

Service

Microsoft Purview

Tag

Major change
Updated message
User impact
Admin impact
Retirement

Platforms

Web

More information

Updated October 30, 2026: We have updated the timeline. Thank you for your patience. 

What and why

Beginning mid-March 2027, Microsoft will start retiring the Microsoft Purview Data Security Posture Management (DSPM) classic and DSPM for AI classic experiences. Retirement will be completed by end of March 2027.

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 mid-March 2027 (previously late January) and expected to complete in late March 2027 (previously late January)

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

Compliance considerations

QuestionAnswer
Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Yes. 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.

Version history

3 versions tracked

Updated 2 times since Sep 28, 2026. Microsoft only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Oct 30, 2026 · 06:20 PMLatest · v3

    Changed: Body, End date

  2. Oct 27, 2026 · 05:46 PMv2

    Changed: Body, Tags, End date

  3. Sep 28, 2026 · 11:51 PMOriginal · v1

    Changed: Initial version