Microsoft Purview: Export adaptive scope members using PowerShell
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
What the notice says
Microsoft’s text, safely structuredIntroduction
We’re adding a new way for Microsoft Purview administrators to export adaptive scope members using PowerShell. Today, admins can review current and historical membership in adaptive scopes through the Purview portal. Based on customer feedback, we are introducing a PowerShell cmdlet that offers more flexibility—enabling automated exports, offline analysis, and the ability to resume exports if an operation is interrupted.
When this will happen
General Availability (Worldwide, GCC, GCCH, and DoD): Rollout began and will be completed within January 2026.
How this affects your organization
Who is affected:
- Administrators who manage Microsoft Purview Data Lifecycle Management, Microsoft Purview Communication Compliance
- Organizations that export adaptive scope membership lists for compliance, reporting, or operational review
What will happen:
- A new PowerShell cmdlet will be available to export adaptive scope members.
- Admins can continue using the Microsoft Purview portal; no existing workflows or UI experiences will change.
- The PowerShell cmdlet offers:
- Granular control over export parameters
- Ability to automate export scenarios using scripts or scheduled tasks
- Ability to resume an interrupted export operation
- The feature will be available by default for all tenants.
- There will be no user impact.
What you can do to prepare
No action is required to prepare for this change.
If you plan to use the PowerShell option after it becomes available, you may want to:
- Review or update internal scripts that manage adaptive scopes.
- Inform your compliance or security operations teams about the new export method.
Learn more: Get-AdaptiveScopeMembers | policy-and-compliance-retention | Exchange PowerShell | Microsoft Learn
Compliance considerations
No compliance considerations identified. Review as appropriate for your organization.
What changed
Between archive captures, newest firstThe archive supplies one version of this notice.
Learn more
Links from the notice and their documentation checksRelated public evidence
- Public source · August 2026New: Remove a retention hold from an unlicensed OneDrive site by using Security & Compliance PowerShell.
- Public source · August 2026Updated: App-only authentication for eDiscovery cmdlets in Security & Compliance PowerShell is unsupported.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- 1 linked page has not been read yet.