MC1450128: Microsoft Purview Adds Lifecycle Status Evaluation Controls to Adaptive Scopes for Recipients and Site Owners

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
40
0 25 50 75 100
MODERATE IMPACT • ASSESS BUSINESS IMPACT
Recommended Action:
Take a look and decide whether this affects your tenant, users or support teams.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Tenant AdminsMicrosoft 365 AdminsCompliance TeamsSecurity TeamsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
The announcement confirms a new capability for adaptive scopes in Microsoft Purview, giving admins lifecycle status controls and ISO 8601 duration support. The timeline has been pushed back by several months, reducing immediate urgency. Admin impact is moderate as it affects policy targeting and scope definitions, but existing scopes are unchanged. User impact is low since the change is admin-side and does not affect end-user behaviour.
55
🛡️ Admin Impact
15
👥 User Impact
35
⚡ Urgency
45
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Microsoft Purview adaptive scopes are gaining lifecycle status controls, letting admins choose whether active, inactive or soft‑deleted recipients and site owners are included.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Review adaptive scope settings and documentation to plan for the new lifecycle status options and default behaviour.
📅

ROLLOUT TIMELINE

Upcoming:
December 2026

📢 Official Microsoft Message Center Announcement


(Updated) Microsoft Purview: Adaptive scopes add lifecycle status evaluation controls for recipients and site owners
Message ID: MC1450128 (Updated)

Updated November 13, 2026: We have updated the timeline. Thank you for your patience. 

[What and why]

Microsoft Purview is introducing lifecycle status evaluation controls for adaptive scopes. This update gives administrators explicit control over whether active, inactive, and soft-deleted recipients and site owners are included in adaptive scope membership.

With this change, newly created adaptive scopes will evaluate only active recipients and site owners by default. Administrators can configure adaptive scopes to include inactive and/or soft-deleted recipients and site owners when needed.

This update also adds support for ISO 8601 duration values for selected date attributes in the adaptive scope advanced query builder.

This message is associated with Microsoft 365 Roadmap ID 568785.

[Rollout schedule]

  • Public Preview: Beginning in December 2026 (previously mid-September) and expected to complete in December 2026 (previously early October)
  • General Availability (Worldwide): Beginning in April 2027 (previously mid-October 2026) and expected to complete in April 2027 (previously mid-November 2026)

[Impact on your organization]

Who is affected

  • Microsoft Purview administrators who create or manage adaptive scopes.
  • Organizations that use adaptive scopes for Microsoft Purview policy targeting.

Platforms and services

  • Microsoft Purview
  • Adaptive Scopes

What will happen

Existing adaptive scopes will continue to function as they do today and will not be automatically modified as part of this rollout.

For newly created adaptive scopes:

  • Active recipients and site owners will be evaluated by default.
  • Inactive and soft-deleted recipients or site owners will not be included unless explicitly configured by an administrator.

21547

Administrators will also have the option to update existing adaptive scopes to use explicit lifecycle status evaluation criteria for recipients and site owners.

Additionally, adaptive scopes will support ISO 8601 duration values for certain date-based attributes in the advanced query builder.

[Action required and recommendations]

No action is required before rollout.

We recommend that administrators:

  • Review current adaptive scope configurations and governance requirements.
  • Determine whether inactive or soft-deleted recipients and site owners should be included in future adaptive scope definitions.
  • Update adaptive scope creation processes and documentation, if applicable, to account for the new lifecycle status settings.

Learn more

[Compliance considerations]

No compliance considerations have been identified.

Source: Microsoft Message Center • Analysed by MWPro

<<< [MC1450128] Archive
Tooltip: View earlier revisions of this post