Category: Retention and Scheduling

Adaptive Scope

Also known as: Adaptive Policy Scope, Adaptive Scopes

Simply put

An adaptive scope is a feature in Microsoft Purview (Microsoft 365) that uses a query to automatically decide which users, groups, or locations a retention or compliance policy applies to. Because membership is determined by the query rather than a fixed list, the set of targets updates as the underlying data changes. This differs from static scopes, where the targets are selected manually and remain fixed until edited.

Formal definition

An adaptive scope is a dynamic, query-based targeting mechanism within Microsoft Purview's information governance and records management capabilities. Rather than specifying a fixed list of locations, an administrator defines a query (for example, based on user or group attributes, or SharePoint site properties such as site templates), and the scope's membership is evaluated dynamically against that query to determine where a policy, such as a retention policy, is applied. Adaptive scopes are used by Purview solutions to identify target locations for processing, and according to the evidence are associated with an E5 licensing tier. This term is vendor-specific and describes a policy-targeting construct; it should not be treated as a generic records management concept, and its behavior, scope, and prerequisites are defined by the Microsoft platform rather than by any records management standard.

Why it matters

Retention and compliance policies are only effective if they are applied to the right locations, and in large or changing organizations the set of relevant users, groups, and sites rarely stays fixed. Adaptive scopes address this by determining policy targets through a query rather than a manually curated list, so that as people join or leave groups, or as new sites are created that match the defined criteria, the policy's coverage adjusts without an administrator having to revise the target list each time. This reduces the risk of gaps in coverage that can arise when static lists fall out of step with organizational reality.

For records and information governance professionals, this matters because coverage gaps can undermine the defensibility of a retention program. A policy that fails to reach newly created locations may leave records unmanaged, while an out-of-date static list may continue applying rules to locations that no longer warrant them. Query-based targeting is intended to keep the applied scope aligned with current conditions, which supports more consistent treatment of content across a changing estate.

At the same time, adaptive scope is a vendor-specific construct within Microsoft Purview and should not be mistaken for a generic records management principle. Its behavior, prerequisites, and licensing depend on the platform, the evidence associates adaptive scopes with an E5 licensing tier, so organizations should confirm current requirements against Microsoft's own documentation before relying on the feature as part of a governance strategy.

Who it's relevant to

Records managers

Those responsible for retention programs within Microsoft 365 environments may use adaptive scopes to keep policy coverage aligned with a changing set of users, groups, and sites, reducing the manual effort of maintaining target lists. They should treat it as a platform feature that supports, but does not replace, a defensible retention framework.

Information governance officers

Because adaptive scopes span retention and compliance policy targeting across Microsoft Purview, governance officers overseeing how policies are applied across the organization's estate have an interest in understanding how query-based targeting affects coverage and consistency.

Microsoft 365 and Purview administrators

Administrators who configure and publish policies are the ones who define the queries that determine adaptive scope membership. They also need to confirm licensing prerequisites, the evidence associates the feature with an E5 tier, and verify current requirements and behavior against Microsoft's documentation.

Compliance leads

Those accountable for demonstrating that policies reach the intended content may find query-based targeting useful for keeping coverage current, but should understand its vendor-specific nature and validate that its behavior meets their jurisdictional and sector-specific obligations.

Inside Adaptive Scope

Dynamic classification criteria

Rules that adjust how records are categorized as organizational activities, systems, or regulatory conditions change, rather than relying on a single fixed taxonomy applied uniformly over time.

Contextual retention triggers

Retention parameters that respond to events, business function, or jurisdictional factors, so that the applicable retention period can shift depending on the context in which a record was created or is held.

Boundary review mechanisms

Periodic reassessment of what falls inside or outside the defined scope of a recordkeeping control, enabling coverage to expand or contract as needs evolve. What is in scope at one point may fall outside it later, depending on organizational policy.

Change governance controls

Documented approval, versioning, and accountability arrangements that ensure adjustments to scope remain defensible and traceable, preserving the authenticity and integrity of affected records.

Jurisdiction and sector sensitivity

The capacity to reflect differing legal, regulatory, and sectoral requirements, recognizing that obligations vary across jurisdictions and that no single regime applies universally.

Common questions

Answers to the questions practitioners most commonly ask about Adaptive Scope.

Is adaptive scope the same as simply having no fixed retention rules?

No. Adaptive scope should not be confused with the absence of rules. It refers to a controlled approach in which the boundaries of what a scheme, classification, or retention arrangement covers can be adjusted in response to changing circumstances, but those adjustments are typically governed by defined criteria, authority, and documentation. Removing fixed rules altogether would tend to undermine the consistency and defensibility that recordkeeping relies on, whereas adaptive scope aims to preserve control while allowing measured change.

Does adopting adaptive scope mean my organization can change retention periods whenever it wants?

Not in an unqualified sense. The capacity to adjust scope does not imply that retention periods can be altered at will. In many organizations, retention periods are shaped by statutory, regulatory, and business requirements that vary by jurisdiction and sector, and these often constrain what can be changed and by whom. Adaptive scope typically concerns how the reach of an arrangement is defined and revised under governance, rather than granting discretion to override obligations that sit outside organizational control.

How should responsibility for changing scope be assigned within an organization?

Responsibility is usually allocated according to organizational policy and governance structures. Many organizations designate specific roles, such as records managers or information governance officers, with the authority to propose or approve changes, often with input from legal, privacy, and business stakeholders. The aim is generally to ensure that adjustments are made by accountable parties rather than informally, so that changes remain traceable and defensible.

What should be documented when the scope of a recordkeeping arrangement is adjusted?

Documentation practices depend on organizational policy, but it is common to record what changed, the reason for the change, who authorized it, and when it took effect. Capturing this information supports the authenticity and reliability of the recordkeeping system and helps demonstrate that adjustments were deliberate and controlled. Where changes affect retention or disposition, organizations often retain evidence of the prior arrangement as well.

How can changes to scope be managed without disrupting existing legal holds?

Legal holds and their interaction with scope changes depend on jurisdiction and organizational policy. As a general matter, records subject to a hold are typically protected from disposition regardless of broader adjustments, so many organizations design their processes to check for active holds before any change takes effect. This helps ensure that adaptive adjustments do not inadvertently override obligations to preserve relevant records.

How often should the scope of a scheme be reviewed?

Review frequency is a matter of organizational policy and risk appetite rather than a fixed rule. Some organizations schedule periodic reviews, while others trigger reviews in response to specific events such as regulatory change, reorganization, or the introduction of new systems. The intent is generally to keep the arrangement aligned with current requirements without making changes so frequently that consistency and traceability are compromised.

Common misconceptions

Adaptive scope means retention rules can be changed freely and informally whenever convenient.

Adaptability typically operates within governed change controls. Adjustments generally require documentation, approval, and traceability so that the integrity and defensibility of recordkeeping decisions are preserved.

Adaptive scope is simply another term for information governance.

Adaptive scope concerns how the boundaries of a particular recordkeeping control adjust over time. Information governance is the broader accountability framework spanning policy, risk, privacy, security, and value; the two overlap but are not synonymous.

Expanding scope automatically means more records are destroyed or archived sooner.

Changes in scope affect which records a control applies to, not a single predetermined outcome. Disposition may include transfer or permanent preservation as well as destruction, and the applicable action depends on organizational policy and jurisdiction.

Best practices

Document the rationale, approver, and effective date for every change to scope so adjustments remain traceable and defensible.

Establish a regular boundary review cycle to confirm what remains in or out of scope as business activities and systems change.

Align scope changes with jurisdictional and sector-specific requirements, using qualified criteria rather than assuming a single regime applies everywhere.

Version and retain prior scope definitions so the state of controls at any past point can be reconstructed if questioned.

Coordinate scope adjustments with legal hold and retention processes to avoid inadvertently narrowing coverage of records subject to ongoing obligations.

Verify that scope changes preserve the authenticity, reliability, integrity, and usability of affected records rather than disrupting their evidential value.