New adaptive scopes will skip inactive mailboxes unless you say otherwise

Microsoft is changing how new adaptive scopes in Purview decide who's in. According to Message Center post MC1450128 (Microsoft 365 roadmap ID 568785), newly created adaptive scopes will evaluate only active recipients and site owners by default. Administrators can choose to include inactive and soft-deleted ones. Existing scopes keep working as they do today and won't be changed by the rollout. The timeline moved on 13 November: public preview in December 2026, general availability in April 2027.

Nothing breaks on the day. The risk is quieter. Someone builds a new retention scope next spring, accepts the default, and leavers fall out of a policy they were meant to stay in.

Why this lands on records, not just admin

Adaptive scopes target Purview policies by attribute rather than by a fixed list, which is why records teams like them. Learn's adaptive scopes page already lets you target or exclude inactive mailboxes in the advanced query builder with the IsInactiveMailbox property. Our post on Copilot chats after someone leaves suggested an adaptive scope as one way to set a different period for leavers. Under the new default, that only works if the scope says so.

What changes, precisely

  • New scopes: active recipients and site owners only, unless you include inactive or soft-deleted ones.
  • Existing scopes: unchanged. Administrators can move them to the explicit lifecycle settings.
  • Queries: ISO 8601 duration values for selected date attributes in the advanced query builder.

The duration support is useful on its own. A relative value such as P90D, ISO 8601 for 90 days, stays correct as time passes, where a hard-coded date has to be edited by someone who remembers. The Message Center post says the Learn page will be updated closer to general availability, so check then which attributes accept it.

Three decisions before April 2027

  1. Records owner. For each policy that uses an adaptive scope, say whether inactive mailboxes belong in it. Leavers' mail and Copilot interactions are the usual cases where the answer is yes.
  2. Compliance administrator. List every existing scope and the policies that use it. Decide whether to move existing scopes to the explicit setting now, so old and new scopes don't behave differently by accident.
  3. Whoever owns the build runbook. Add one line to the scope template: lifecycle status, with the reason. Active only, active plus inactive, or including soft-deleted.

Soft-deleted objects are a separate choice from inactive mailboxes. Decide each one on purpose rather than ticking both because they sit next to each other.

Allow for the lag

Learn notes that adaptive scope queries can take up to five days to fully populate, and suggests waiting a few days before adding a new scope to a policy. Retention policy distribution adds its own delay. A scope built the week someone leaves may arrive late for that person.

Default changes are easy to miss because nothing fails. Write the lifecycle choice into every new scope, and inactive mailboxes stay where you meant them to be.

McCloy Data

Thought leadership on OpenText, SAP, and practical content and finance automation - from the McCloy Data team.

https://www.mccloydata.com
Next
Next

UK e-invoicing from April 2029: what OpenText VIM for SAP needs from Peppol and EDI