Admin, security & compliance Retiring #169

Microsoft Purview: Retirement of DSPM classic and DSPM for AI classic

Classic DSPM workflows must move to the current experience

Microsoft plans to retire DSPM classic and DSPM for AI classic from mid-March through late March 2027. Organizations using these experiences in the Microsoft Purview portal must move their workflows to the current Microsoft Purview DSPM experience.

Key points

  • Retirement covers Worldwide, GCC, GCC High, and DoD.
  • The current DSPM experience centralizes posture metrics, recommendations, reports, investigations, and data security objectives.
  • Most new DSPM capabilities are delivered through the current DSPM experience.
  • Organizations already using the current experience with no remaining classic dependencies do not need to take action.

What to do

Review workflows for dependencies on DSPM classic or DSPM for AI classic. Confirm access through Microsoft Purview portal > Solutions > DSPM. Transition remaining classic workflows before retirement begins. Notify Microsoft Purview administrators, security teams, and compliance teams. Update documentation, training materials, operational procedures, and help desk guidance. If already fully transitioned, no action is needed; communicate the retirement to relevant teams.

Timeline

  1. 28 September 2026 Published
  2. 30 October 2026 Timeline change (confirmed) Microsoft updated the retirement timeline.
  3. March 2027 Retirement end (planned) Retirement is expected to complete in late March.
  4. March 2027 Retirement start (planned) Retirement begins in mid-March across all listed clouds.
Speaker notes

This retirement changes where administrators manage data security posture, rather than removing the underlying capability. Microsoft has unified DSPM capabilities for traditional data sources and AI applications and agents into the current experience. The classic experiences will no longer be available after retirement. The updated schedule starts in mid-March 2027 and is expected to finish in late March 2027; these are planned dates, not confirmation of removal. Teams should check for operational dependencies on either classic experience and move them before retirement. Organizations that have already fully transitioned do not need to take action.

Sources and links

Related cards

Area, status, change type, licence and flags are indicative. Always open the source before you act on a card.