MC1450128: Microsoft Purview Adds Lifecycle Status Controls to Adaptive Scopes and Supports ISO 8601 Durations

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

Microsoft 365 AdminsSecurity TeamsCompliance TeamsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This is a new feature for Microsoft Purview adaptive scopes, adding lifecycle status evaluation and ISO 8601 duration support. Admin impact is moderate as scope creation and management processes may need to be updated and reviewed for governance implications. User impact is minimal because changes occur in administrative controls rather than end-user experiences. Urgency is low to moderate as no immediate action is required before rollout, but future configuration choices should be planned. Implementation effort involves updating documentation, processes and possibly revising existing scopes.
55
🛡️ Admin Impact
15
👥 User Impact
35
Urgency
45
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Adaptive scopes in Microsoft Purview will now let you control membership by lifecycle status. New scopes default to active recipients only.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Review adaptive scope settings and decide if inactive or soft-deleted recipients should be included. Update any internal guidance as needed.
📅

ROLLOUT TIMELINE

Upcoming:
Mid-Sep to Nov 2026

📢 Official Microsoft Message Center Announcement


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

[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 mid-September 2026 and expected to complete in early October 2026
  • General Availability (Worldwide): Beginning in mid-October 2026 and expected to complete in 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

Share This Update